If you’re evaluating a Dynamics GP to Business Central migration, one of the first decisions is how much of your existing GP environment you want to carry forward. There are two common approaches:
Reimplementation
Build a new Business Central environment, redesign where appropriate, and selectively migrate data from GP.
Cloud Migration Tool
Connect Dynamics GP to Business Central online and use Microsoft’s migration tooling to move supported setup, master, transactional, and historical data.
The Cloud Migration Tool can reduce the amount of manual migration work, but that does not automatically make it the right approach for every organization. Your data structure, customizations, historical-data requirements, integrations, and desired future-state design all matter.
What data can migrate from Dynamics GP to Business Central?
Microsoft’s cloud migration tools can migrate a range of GP data, including:
- Fiscal periods and accounting setup
- Chart of accounts and account-related data
- Customers and outstanding receivables
- Vendors and outstanding payables
- Inventory items and units of measure
- Checkbook data
- Payment terms, shipping methods, and other company setup
- Historical transaction data
The exact data migrated is configurable during the cloud migration setup, including which companies and historical information you want to bring into Business Central. Microsoft Learn
What about historical Dynamics GP data?
Historical GP information can be migrated into dedicated extension tables in Business Central. Microsoft refers to this as the GP Historical Snapshot. Depending on your configuration, historical snapshots can include:
- General ledger detail
- Receivables transactions
- Payables transactions
- Sales Order Processing transactions
- Purchase Order receipt transactions
- Inventory transactions
You can also specify how far back you want the historical snapshot to go rather than automatically bringing over every available year. Microsoft Learn That data remains separate from native Business Central transaction data, but users can access it through corresponding Business Central list pages using the GP Detail Snapshot views. Microsoft Learn
How does the migration process work?
Microsoft’s migration process moves GP data table by table and tracks successes and failures during the migration. If an individual table fails because it cannot be found or its schema does not match what the migration expects, the migration can continue with the remaining tables. Microsoft Learn A typical approach is to:
- Configure the Business Central cloud migration environment.
- Select the GP companies and data you want to migrate.
- Run an initial migration into a Business Central sandbox.
- Validate the migrated data, configuration, reporting, and integrations.
- Resolve migration errors or design issues.
- Run the migration again as you prepare for production cutover.
After the initial migration, subsequent runs can use change tracking to migrate changes that occurred in GP since the previous migration. Microsoft Learn
When does the Cloud Migration Tool make sense?
The Cloud Migration Tool tends to be a stronger fit when much of your existing GP structure and data should carry forward into Business Central. A reimplementation may deserve more consideration when you want to:
- Redesign your chart of accounts or dimensions
- Clean up significant master-data issues
- Replace old customizations
- Simplify business processes
- Reconsider integrations
- Change how reporting or operational workflows are structured
Neither approach is inherently better. The question is how much of the existing GP environment still represents how you want the business to operate going forward.
Best practices for migrating GP to Business Central
Before migrating, we typically recommend:
- Design the future-state Business Central environment first. Don’t assume the goal is simply to reproduce GP in a new platform.
- Clean up GP before you migrate. Resolve data issues, run appropriate reconciliations, and address master-record changes before moving the data.
- Plan your dimensions deliberately. GP account segments do not map one-for-one to the way you may want to use Business Central dimensions.
- Test in a sandbox before production. Microsoft specifically recommends testing the migration before running the production move. Microsoft Learn
- Validate integrations and reporting separately from the data migration. Successfully moving records does not mean every surrounding business process is ready for go-live.
- Keep GP accessible after cutover. Maintain access to the legacy environment for an appropriate period when users may still need original source documents or historical context.
A GP to Business Central migration can range from a relatively direct data move to a broader ERP redesign. If you’re trying to determine which approach fits your GP environment, BCS can help you assess the data, integrations, customizations, and migration path before you commit to an approach.
