How to migrate and clone production content to a stage environment in Adobe Experience Manager
This article explains how to migrate content from a production environment to a stage environment in Adobe Experience Manager (AEM). Organizations often migrate production content to support testing, development, or user acceptance activities. The process includes identifying the required content paths and transferring both the primary content and any related assets or content fragments. The migration approach depends on whether the environment uses Adobe Experience Manager (AEM) as a Cloud Service or Adobe Experience Manager (AEM) 6.x. To resolve the issue, migrate content and related assets to the stage.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service
- Adobe Experience Manager (AEM) 6.x
- Adobe Managed Services (AMS)
- On-premises deployments
Issue/Symptoms
The content team cannot proceed with testing or development until production content is available in the stage environment.
Root cause
There is a business need to replicate production content for development, testing, or validation in a non-production environment.
Resolution resolution
Follow the steps below to resolve the issue:
- Identify the content paths and related assets or content fragments that require migration from the production environment to the stage environment.
- For Adobe Experience Manager as a Cloud Service (AEMaaCS), use the Content Copy Tool to define a content set that includes the required JCR paths, such as
/content/example,/content/dam/example, and/conf/example. Initiate the content copy from the production environment to the target stage environment by following the documented Content Copy process. - For Adobe Experience Manager (AEM) 6.x on-premises or AMS deployments, use AEM Package Manager to create content packages for the identified content paths and related assets. Download the packages from the production environment, then upload and install them in the stage environment through Package Manager.
- After the migration completes, verify that the content appears under the intended paths in the stage environment.
- Confirm with the content or QA team that the migrated content meets the testing, development, or validation requirements.