Note
Acquia will remove all features of Acquia Migrate Accelerate from Cloud Platform on April 10, 2024. For all Drupal site owners, an open source version of the Acquia Migrate Accelerate module is available in the community. For more information, see Acquia Migrate: Accelerate - now open source!.
I can’t access the Create Migrate Environment link to start the process
Make sure your Account Manager has verified the entitlement is added to your account, and your Cloud user has the appropriate Acquia Migrate: Accelerate permissions assigned. See Step 0 in Using Acquia Migrate Accelerate.
When you have the correct entitlement and permissions, you see Create Migration Environment as one of the options in the Cloud Actions menu.
Creating a migration environment seems to take a long time
Cloud Platform generally creates a migration environment within 10-15 minutes. However, this process might take up to an hour or more, depending on the size of the Drupal 7 site’s database and files, and network traffic at that time.
While Cloud Platform is generating my migration environment, I cannot access my other environments in the Cloud Platform user interface
This is an expected behavior. The migration environment needs to generate a new database on all of your environments, which stores the copy of the Drupal 7 database that will be used as the migration source. No other changes are being made to any of your environments. However, the UI does not return control until the migration environment is generated.
File copy operation takes longer in Cloud Next compared to Cloud Classic
The file copy operation in Cloud Next takes longer as compared to Cloud Classic. This occurs because the files are first copied from the production environment to an intermediate ODE environment, and then to a migration environment. After the copy operation is complete, the system deletes the ODE environment, thereby keeping only the migration environment. This additional step in the migration process consumes more time.
I encountered the “Another Acquia Migrate Accelerate operation is already running” issue during migration
This issue occurs when you have multiple concurrent requests in the database layer. In addition, you might have a complex infrastructure that results in high network latency.
Workaround:
To migrate your data, you can use the drush ama:import command. Acquia
recommends you to not use the Acquia Migrate Accelerate web user interface, and
run Acquia Migrate Accelerate locally as it is now open source. For more
information, see AMA is now open source.