Prepare and plan for cloud migration from Dynamics GP

This article provides recommendations to help you define your cloud migration strategy and get environments and users ready for cloud migration.

Run migration assessment tool

The migration assessment tool delivers valuable insight into your overall readiness to migrate. It provides migration options based on your needs and detects potential migration issues based on your Dynamics GP system structure. To get started, go to the cloud migration assessment tool.

Learn more about the tool in the video Are You Ready for Business Central.

Determine what data to migrate

The data that's migrated is determined on a per-company basis. The GP migration apps transform supported GP data into Business Central data according to the company options you select. Learn more in Configure Dynamics GP company migration.

You can choose to migrate data for all companies or only specific companies. We recommend that you determine which companies to migrate upfront to save time and resources. Keep in mind that the more companies you replicate in a single operation, the longer the migration takes.

You can migrate all the data that you want to take with you to the cloud, but be aware of the storage capacity of your online tenant. If you need more storage than the default 80 GB, you can buy another environment or extra storage capacity. Storage capacity includes 80 GB, allowances per Essentials, Premium, Device, or Partner Sandbox license, and extra capacity from purchased environments and storage capacity licenses. Learn more in Managing capacity.

Determine your migration approach

It's important to have a solid migration strategy in place to ensure a smooth transition. Most migrations can run from the on-premises production database with minimal downtime for end users. However, for especially large migrations, it might be better to run migration from a backup of the on-premises database. Doing migrations this way improves migration speeds and minimizes performance loss and downtime on the on-premises production database. The following steps outline a typical migration approach.

  1. Create a full backup of the GP system and company databases that you plan to migrate. Restore the backups to a SQL Server instance that meets the migration prerequisites and is licensed for the workload.
  2. Complete the usual preparation steps on the backup on-premises database and address any issues that arise.
  3. Complete cloud migration setup, including choosing the companies and configuring the GP data to migrate. On GP Migration Settings, turn off Run migration after replication so that data transformation doesn't start after a test replication.
  4. Run the replication and address any issues that arise.
  5. Stop users from entering data in the on-premises environment before taking the final backups.
  6. Restore the final backups to the migration source SQL Server instance, run the final replication, and resolve any errors. Keep the on-premises environment closed to data entry.
  7. Run data upgrade and validate the migrated data in the online environment.
  8. Optionally, copy Dynamics GP data to Azure Data Lake for future reference and wait for the copy to complete. This copy requires cloud migration to remain enabled and is separate from the SQL Server backup. Learn more in Copy Dynamics GP data to Azure Data Lake.
  9. Complete the migration and go live in the online environment.

Important

Keep the Dynamics GP source version and Business Central online version unchanged while cloud migration is set up. Schedule updates to the online environment for a date after cloud migration is complete.

Avoid changing extensions while cloud migration is enabled. If you need to install or uninstall extensions, disable cloud migration, make the changes, and then set up cloud migration again.

Keep in mind that the migration process can be complex, and issues might arise that require more troubleshooting. It's important to stay flexible and be prepared to adjust your migration strategy as needed to address any problems that arise.

Schedule the final migration

  • Plan the switch to use Business Central online for production carefully so that production use doesn't start until migration is complete.

    Don't set up cloud migration for a production environment that's already in use for business. You risk that the migration process overwrites data that's needed to run the business. Even if your migration targets a different company in that environment, you risk that the upgrade overwrites data that's shared across companies in the target environment.

  • Schedule the migration so that it doesn't conflict with an update of Business Central online.

    Once you set up cloud migration for an environment, the environment can't be updated. If you want to update the environment, you must disable cloud migration. If an update is available, and you haven't started migration, then update the target environment first, then migrate. If you've already started the cloud migration process, we recommend that you continue migrating all companies, complete cloud migration, and then update to the next major or minor version. Separating updates from cloud migration helps avoid data corruption if the update touches tables with records in both migrated and nonmigrated companies.

Next steps