Adobe Experience Manager is the successor to Adobe CQ5. Most of the information shared on these pages is valid for both AEM as well as CQ5.
This page introduces the Adobe Experience Manager and the CRXDE lite tool that is used for content migrations into the Adobe Experience Manager. Content is being saved using the the Java Content Repository. Via Sling the content is posted to Adobe Experience Manager. For more information, visit 'The Basics' on the documentation of Adobe. A few of the powerful advantages of AEM uses, are the Digital Asset Management, blueprinting and Sling.
By using Sling, this connector provides a way to import content quickly via REST. This can be done locally, before it is transported via packages and uploaded to a different server. The content is uploaded using the JCR. In practice, this means the connector creates json files, which will be uploaded via Sling (using REST). You can use the CRXDE lite tool to see the pages and assets get imported into AEM.
Adobe Experience Manager provides a set of predefined templates for a lot of different content. E.g. there are templates for content types, pages, page blocks, components, etc. These templates can be extended or adjusted to the customers liking, which makes the AEM extremely flexible.