Migration of all media assets, such as images, videos, and PDFs, along with associated metadata.
Configuration of Media Library and Acquia DAM integration features.
Pre-migration requirements
Before you start the migration process, ensure:
Complete a full backup of your Drupal site's database and file system.
Verify your administrative permissions to access the migration dashboard.
Confirm your permissions to update modules in Drupal.
Steps to migrate
If you are already running the latest version of the media_acquiadam module (2.1.x) and acquia_dam version 1.1.2 (or newer), and have previously performed the database update, you can skip the version upgrade and database update, steps 1 and 2.
1. Upgrade to the latest version (2.1.x):
Upgrade the module using Composer or through the Drupal UI.
composer require drupal/media_acquiadam:^2.1
2. Run database update:
This step is essential to apply any necessary database schema changes and configuration updates, enabling the new version of the Media Acquia DAM module to function properly. Execute the drush updb -y command or navigate to the /update.php page in your Drupal installation. This process also enables the media_acquiadam module.
3. Use the migration dashboard to perform migration:
After the upgrade and database update steps are completed, navigate to the migration path (/admin/config/acquia-dam/migration) within the Drupal user interface. This leads to the Migration Dashboard, which provides a clear overview of the migration status. The migration process is guided through a three-step wizard designed to ensure a smooth and structured migration experience. Each step focuses on a specific phase of the migration:
Media Source Selection
Media Type Selection
Pre-Migration Review
You can progress through the following steps sequentially, with options to review, confirm, and proceed at their own pace.
A. Media source selection
This dashboard facilitates the migration of legacy media types to Acquia DAM by providing a map between media_acquiadam media types and their corresponding media source in Acquia DAM. The table displays the media types, the total number of media items, the display handler for media assets, and the target media source that requires migration. This dashboard enables you to track the progress and completion of the migration.
The details of each column are:
Media type label and name: You may change the label during migration to the Acquia DAM system.
Number of media items: Count of DAM assets in each media type that require migration.
Method to handle media files: Two methods are provided:
Sync: This method renders assets locally.
Embed: This method renders assets from the Widen CDN.
Target source type: You receive a list of Acquia DAM media sources. You must select the target source for asset migration.
B. Media type selection
This page shows a list of new media types from the Acquia DAM module. Select the checkbox next to any media type you do not want to keep. You must decide whether to keep the suggested media types or select them for deletion if they are not required.
Note: If you deselect any suggested media type, a warning appears to alert you about potential duplication within the system.
C. Pre-migration review
After you review and confirm the media types selected for deletion, click Save & Next to move to the final step. This action takes you to the pre-migration report, which provides a summary of the current status before the migration begins.
After the configuration is saved, migration can be performed through either of the following:
Admin user interface
Command-line interface
Through admin user interface
Verify the data and click Migrate to begin the migration process. The assets migrate in batches. A progress bar displays the status of the migration in real time.
At the end of the process, the system displays a migration summary. This summary provides a detailed overview of the media items successfully migrated, categorized by each media type.
Through Command-line interface
After you click Save on the last page of the migration dashboard, you can also perform asset migration using the Drush command:
drush acquiadam:migrate
4. Validate migration
After the migration, ensure that:
All assets are transferred and visible in the Acquia DAM Library at /admin/content/media.
Metadata, files, and references remain intact in the content.
Duplicate media types are deleted from the system.
5. Post migration
To finalize the migration process:
Clear Drupal site’s cache to ensure all changes are properly reflected across the site.
Verify the Acquia DAM integration by testing media uploads, retrievals, and rendering within the site’s content.
Ensure permissions for content editors and administrators operate as expected.
How to migrate from Media Acquia module to Acquia DAM module?
The Media: Acquia DAM to Acquia DAM migration tool facilitates asset transfers within the Drupal application.
Features
The tool offers several key capabilities:
Transfers assets efficiently between different modules, which enhances the experience for site administrators and editors.
Ensures migration of digital assets and associated metadata while it preserves site and user authentication.
Integrates key features such as embed and download options without disruption to ongoing workflows.
Enhances platform capabilities and functionalities, so users can migrate media assets to Acquia DAM media types without affecting the media system.
Provides the flexibility to uninstall the media_acquiadam module.
Migration of all media assets, such as images, videos, and PDFs, along with associated metadata.
Configuration of Media Library and Acquia DAM integration features.
Pre-migration requirements
Before you start the migration process, ensure:
Complete a full backup of your Drupal site's database and file system.
Verify your administrative permissions to access the migration dashboard.
Confirm your permissions to update modules in Drupal.
Steps to migrate
If you are already running the latest version of the media_acquiadam module (2.1.x) and acquia_dam version 1.1.2 (or newer), and have previously performed the database update, you can skip the version upgrade and database update, steps 1 and 2.
1. Upgrade to the latest version (2.1.x):
Upgrade the module using Composer or through the Drupal UI.
composer require drupal/media_acquiadam:^2.1
2. Run database update:
This step is essential to apply any necessary database schema changes and configuration updates, enabling the new version of the Media Acquia DAM module to function properly. Execute the drush updb -y command or navigate to the /update.php page in your Drupal installation. This process also enables the media_acquiadam module.
3. Use the migration dashboard to perform migration:
After the upgrade and database update steps are completed, navigate to the migration path (/admin/config/acquia-dam/migration) within the Drupal user interface. This leads to the Migration Dashboard, which provides a clear overview of the migration status. The migration process is guided through a three-step wizard designed to ensure a smooth and structured migration experience. Each step focuses on a specific phase of the migration:
Media Source Selection
Media Type Selection
Pre-Migration Review
You can progress through the following steps sequentially, with options to review, confirm, and proceed at their own pace.
A. Media source selection
This dashboard facilitates the migration of legacy media types to Acquia DAM by providing a map between media_acquiadam media types and their corresponding media source in Acquia DAM. The table displays the media types, the total number of media items, the display handler for media assets, and the target media source that requires migration. This dashboard enables you to track the progress and completion of the migration.
The details of each column are:
Media type label and name: You may change the label during migration to the Acquia DAM system.
Number of media items: Count of DAM assets in each media type that require migration.
Method to handle media files: Two methods are provided:
Sync: This method renders assets locally.
Embed: This method renders assets from the Widen CDN.
Target source type: You receive a list of Acquia DAM media sources. You must select the target source for asset migration.
B. Media type selection
This page shows a list of new media types from the Acquia DAM module. Select the checkbox next to any media type you do not want to keep. You must decide whether to keep the suggested media types or select them for deletion if they are not required.
Note: If you deselect any suggested media type, a warning appears to alert you about potential duplication within the system.
C. Pre-migration review
After you review and confirm the media types selected for deletion, click Save & Next to move to the final step. This action takes you to the pre-migration report, which provides a summary of the current status before the migration begins.
After the configuration is saved, migration can be performed through either of the following:
Admin user interface
Command-line interface
Through admin user interface
Verify the data and click Migrate to begin the migration process. The assets migrate in batches. A progress bar displays the status of the migration in real time.
At the end of the process, the system displays a migration summary. This summary provides a detailed overview of the media items successfully migrated, categorized by each media type.
Through Command-line interface
After you click Save on the last page of the migration dashboard, you can also perform asset migration using the Drush command:
drush acquiadam:migrate
4. Validate migration
After the migration, ensure that:
All assets are transferred and visible in the Acquia DAM Library at /admin/content/media.
Metadata, files, and references remain intact in the content.
Duplicate media types are deleted from the system.
5. Post migration
To finalize the migration process:
Clear Drupal site’s cache to ensure all changes are properly reflected across the site.
Verify the Acquia DAM integration by testing media uploads, retrievals, and rendering within the site’s content.
Ensure permissions for content editors and administrators operate as expected.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia DAM