You can use Microsoft's built-in migration tools to migrate from Dynamics GP to Business Central. However, your GP version must be 2015 or later, and your SQL Server database should be 2016 or later with a compatibility level of 130 or higher. Also, the migration process involves transferring data sensitive data like customer and vendor information, inventory items, and financial transactions. Hence, it is beneficial to reach out to a certified partner to plan your migration process for a seamless transition. Here, we have drafted the entire migration process, including stages and essential dos and don'ts during the migration.
Migration assessment
We assess your existing system before migrating to Business Central. We identify potential issues, choose the right migration path, and analyze critical information such as the modules, features, add-ons, product version, data consumption, and other industry-specific requirements to be addressed during migration. Upon assessment completion, you get valuable insights into the overall readiness, customized solutions based on your needs, and how to address potential obstacles before migration.
Preparation
We create a detailed migration plan outlining timelines, resource needs, and our chosen approach to minimize downtime and disruption. We carefully determine which data to migrate, balancing the need for comprehensive data with cloud storage limitations (additional storage is available if needed).
Our migration approach involves moving the Dynamics GP database to Azure Data Lake for reference (optional). Then, we create a full backup of the on-premises production database (partial backups are not supported). Then, we prepare a backup, resolve issues, and set up the cloud migration for the selected companies. Following this, we run data replication, address issues, and stop on-premises usage before backing up the production database. Finally, we perform the data upgrade in the cloud, complete the final migration, and go live on the new cloud environment.
We prioritize scheduling the migration to avoid conflicts with Business Central online updates, ensuring the target environment is either updated beforehand or the migration is fully completed before any updates are applied to prevent potential data corruption.
Cloud Migration setup
In this phase, we do not migrate data but prepare the environment by establishing the connection and pipeline between the on-premises and online tenant databases, allowing you to specify which companies to migrate. First, we start the Set up Cloud Migration guide, provide SQL database connection details for on-premises migrations, and select an integration runtime. Then, we prepare the environment by checking compatibility between the source and destination databases, creating stored procedures on both sides. Then, we identify companies and extensions to migrate and set up a data replication pipeline. Finally, we start the data replication process to copy data to the cloud and perform a data upgrade.
Configure Dynamics GP company migration
Business Central configuration packages help you simplify importing GP data from Excel spreadsheets. We can help you map GP tables to BC tables, configure your GP company migration, decide what data to migrate, and review default settings. We configure global settings or customize settings for each company, paying attention to dimensions, segments, and historical data. To configure the migration globally, we set the dimensions, select the modules to migrate, and decide whether to migrate only master data for the modules. We also determine if auto-posting for migrated transactions should be disabled. We specify inactive records or discontinued items to migrate, map classes to posting groups, and choose the historical transactions to migrate.
Data Replication
To begin the data migration, we navigate to the cloud migration management and start "Run data migration" process. It runs the data replication pipeline, transferring data from your on-premises system to Business Central online. The process prioritizes larger tables for faster migration, and once completed, you can review the results in the Migration log.
Data Upgrade
Before upgrading, we ensure all users are signed out of Business Central to avoid interruptions, and for on-premises setups, we consider skipping the API upgrade temporarily for quick processing. To run the data upgrade, navigate to the Cloud Migration Management page and select Run data upgrade. During the process, the system updates the environment status, disconnects users, and allows us to track progress in the Business Central admin center. Upon successful completion, the environment becomes active, and users can reconnect. In case of failure, the system restores the environment to its previous state, and we review the error details, fix the issue, and retry the upgrade, potentially rerunning migration setup or data replication if necessary.
Completion and follow-up
To ensure a seamless transition, we optimize the new Business Central online environment to suit your needs, set up user access for all relevant team members, and switch to the new system while decommissioning the old on-premises deployment.