แก้ไข

Prepare and plan for cloud migration from Dynamics SL

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 provides insight into your readiness to migrate. It offers migration options based on your needs and detects potential issues with your Dynamics SL system.

Download the Dynamics SL Analysis and Repair tools from Microsoft's BCTech repository.

Details on compiling and using the files are included on GitHub.

Warning

Before installing or running the tools, make sure that you have restorable backups of both the SL application and system databases. The Repair Tool updates data in the SL application database. Learn more in Repair Tool installation instructions.

  • The Analysis Tool connects to a Microsoft Dynamics SL database and generates an analysis report text file.
    • The report outlines and provides an overview of the modules in use and examines the data that can be migrated to Business Central.

    • Analysis Report information example:

      • Microsoft Dynamics SL version
      • Microsoft SQL version
      • Overview of Microsoft Dynamics SL modules being used
      • Module details including the number of:
        • Records in master tables
        • Records in transaction tables
    • The Repair Tool connects to a Microsoft Dynamics SL database.

      • The Repair tool is used to validate Microsoft Dynamics SL data to identify any issues that require repair before using the online Business Central tool to migrate Microsoft Dynamics SL data to Microsoft Dynamics Business Central.
      • Repair Tool:
        • Includes automated fixes to the Microsoft Dynamics SL data.
        • Includes repair items that need to be addressed.

Determine what data to migrate

The data migrated is determined on a per-company basis. The SL migration apps transform supported SL data into Business Central data according to the company options you select. Learn more in Configure Dynamics SL 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

Ensure you have a solid migration strategy for a smooth transition. Most migrations can run from the on-premises production database with minimal downtime for end users. For large migrations, consider running the 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 SL system and application 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. Prepare the SL databases on the migration source instance and address any issues that arise.
  3. Complete the cloud migration setup, including choosing the companies to migrate.
  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, review posting results, and test the migrated data in the online environment.
  8. Complete the migration and go live in the online environment.

Important

Keep the Dynamics SL 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 only after the 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 to avoid conflicts with updates to 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