Reprocessing Dynamic Media assets after migrating to AEM as a Cloud Service
Reprocessing Dynamic Media (Scene7) assets after migrating from Adobe Experience Manager (AEM) on-premise to AEM as a Cloud Service is only necessary in certain cases. Validate your migrated assets, and reprocess them if required.
Description description
Environment
Adobe Experience Manager (AEM) on-premise migrating to AEM as a Cloud Service, using Dynamic Media (Scene7).
Symptoms
After migrating assets using the Content Transfer Tool (CTT), there is uncertainty about whether Dynamic Media assets need to be reprocessed to re-establish metadata linkage or ensure correct asset functionality. There are also questions about how to identify assets that require reprocessing and how to validate the migration.
Cause
A full reprocessing of Dynamic Media assets is only required if assets are missing Dynamic Media metadata, new image or video profiles are introduced, or metadata is incorrect. When the same Scene7/Dynamic Media company is reused and metadata is preserved during migration, existing assets typically do not require reprocessing.
Resolution resolution
Follow the steps below to determine whether your Dynamic Media assets need reprocessing, and reprocess them if required.
-
Confirm your migration approach. If you are reusing the same Scene7/Dynamic Media company and have migrated assets using the Content Transfer Tool (CTT), Dynamic Media metadata (such as
dam:scene7Id,dam:scene7Domain, anddam:scene7FileStatus) should be preserved. -
Validate migrated assets:
-
Configure Dynamic Media in AEM as a Cloud Service using the same company ID as your previous environment.
-
Select a representative sample of migrated assets.
-
For each sample asset:
- Check that Dynamic Media metadata fields are present and accurate.
- Verify that Dynamic Media renditions and viewer URLs are functional.
-
-
Identify assets requiring reprocessing by checking the asset properties for missing or incorrect
dam:scene7*metadata fields. Assets might need reprocessing if:- They were migrated using methods that bypassed Dynamic Media processing (such as direct package deployment or bulk import without DM workflows), resulting in missing
dam:scene7*metadata. - New image or video profiles, presets, or encoding profiles have been introduced post-migration and you want existing assets to use these new settings.
- Dynamic Media metadata is incomplete or incorrect for certain assets.
- They were migrated using methods that bypassed Dynamic Media processing (such as direct package deployment or bulk import without DM workflows), resulting in missing
-
Reprocess assets as needed:
- Use the Reprocess assets dialog in AEM as a Cloud Service at the folder level, selecting Dynamic Media only.
- Run reprocessing jobs in manageable batches (for example, 500–1,000 assets per job) to avoid overloading the system.
- Dynamic Media processing throughput is typically around 9,000 assets per hour under optimal conditions. Processing time will scale with the volume of assets being reprocessed.
- Monitor Dynamic Media queues and AEM performance during reprocessing.
- Schedule jobs during off-peak hours, and consider using lower environments for initial validation.