DocumentationCommerceAEM Assets integration Guide

Migrate media files to the AEM Assets DAM

Last update: Wed Jul 09 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User

Both Adobe Commerce and Adobe Experience Manager (AEM) provide built-in features to streamline media file migration from Commerce to the AEM Assets digital asset management system (DAM). You can also migrate media files from other sources.

Prerequisites

Category
Requirement
System requirements
  • AEM as a Cloud Service environment provisioned with AEM Assets
  • Sufficient storage capacity
  • Network bandwidth for large file transfers
Required access and permissions
  • Administrator access to AEM Assets as a Cloud Service
  • Access to source system where media files are stored (Adobe Commerce or external system)
  • Appropriate permissions to access cloud storage services
Cloud Storage Account
  • AWS S3 or Azure Blob Storage account
  • Private container/bucket configuration
  • Authentication credentials
Source Content
Metadata Preparation

Migration best practices

  1. Curate assets before migration by removing unused and duplicate content.

  2. Organize assets logically by size, format, or use case.

  3. Consider breaking large migrations into smaller batches.

  4. Schedule resource-intensive imports during off-peak hours.

  5. Validate metadata mapping before full import.

Migration workflow

Follow the migration workflow to export media files from Adobe Commerce or another external system and import them into the AEM Assets DAM.

Step 1: Export content from the existing data source

[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects only (Adobe-managed PaaS infrastructure)."}

For Adobe Commerce merchants, the Remote Storage module can facilitate media file imports and exports. This module allows businesses to store and manage media files using remote storage services like AWS S3. To set up remote storage for your Commerce instance, see Configure Remote Storage in the Commerce Configuration Guide.

If you have media files stored outside of Adobe Commerce, upload them directly to one of the data sources supported by AEM as a Cloud Service.

Step 2: Build a CSV file for metadata mapping

After exporiting the media files, create a CSV file to map these assets with the necessary metadata for automation. The CSV should include fields for product, position, and role mapping, ensuring alignment with the AEM Assets metadata profile.

For each media file you plan to migrate, provide values for the metadata fields included in the AEM Assets metadata profile for Commerce assets as described in the following table.

Metadata
Description
Value
assetPath
The full path where the asset will be stored in the AEM Assets repository.

Use the path to create sub-folders to organize Commerce assets, for example content/dam/commerce/<brand>/<type>.
/content/dam/commerce/<sub-folder>/..<filename>
commerce:positions
The position/order of the asset in product galleries
Multiple numeric values separated by pipe (see csv file)
commerce:isCommerce
Flag indicating if the asset is used in commerce
Yes
commerce:skus
Product SKUs associated with this asset
Multiple string values separated by pipe (see csv file)
commerce:roles
The roles or types of images for the asset (for example, thumbnail, main image, swatch)
Multiple values separated by semicolons (for example, “thumbnail; image; swatch_image; small_image”)
CSV code

Use this sample CSV code to create the file in a code editor or spreadsheet application like Microsoft Excel.

code language-csv 
assetPath,commerce:positions{{Number: multi}},commerce:isCommerce{{String}},commerce:skus{{String: multi}},commerce:roles{{String: multi}}
/content/dam/commerce/sample1.jpg,1,Yes,sku1,thumbnail; image; swatch_image; small_image
/content/dam/commerce/sample2.jpg,1|1|1,Yes,sku1|sku2|sku3,thumbnail; image; swatch_image; small_image|image|image; small_change

Step 3: Bulk Import Assets into AEM Assets

After creating the metadata mapping file, use the AEM Assets Bulk Import Tool to import your assets.

The following is a high-level overview for using the tool.

  1. Log in to your AEM Assets as a Cloud Service author environment.

  2. From the Experience Manager Tools view, select Assets > Bulk Import.

    AEM Assets authoring {width="600" modal="regular"}

  3. From the Bulk Import Configurations, select Create to open the configuration form.

    AEM Assets authoring {width="600" modal="regular"}

  4. Set up and save the configuration.

    You’ll need:

    • Authentication credentials for your data source
    • The target folder in AEM Assets where imported files will be stored
    • Optional. Information about the MIME types, file size, and other parameters to customize the import configuration
    • The path to the metadata mapping CSV file you uploaded to the Cloud storage instance.

    For detailed steps, see Configure the Bulk Import tool in the AEM Assets as a Cloud Service User Guide.

  5. After saving the configuration, use the bulk import tools to test and run the import operation.

Related Articles
Bulk Import tool video demo
Tips, best practices, and limitations
Upload or ingest assets using APIs
recommendation-more-help
62e3c486-e09f-42bb-be80-2058df1fc0e9