GP to Business Central Migration: Automated vs. Manual - Which Path Is Right for You?
- Abhisar Sharma
- Feb 23
- 5 min read
This is Part 4 of our 5-part series on migrating from Dynamics GP to Business Central.
Read the full series:
Part 4: GP to BC Migration - Automated vs. Manual (you are here)
Part 5: The Most Common GP to BC Migration Mistakes (And How to Avoid Them)
One of the most consequential decisions in a GP to Business Central migration is one that many organizations don't know they need to make: which technical migration path to use. There are two options - Microsoft's automated Cloud Migration Tool, and a manual migration using native import/export tools. The right choice depends on your GP version and the complexity of your environment.
Getting this decision wrong does not necessarily derail a project, but it adds cost, time, and risk that could have been avoided. Here is how to think through it.
Path 1: The Automated Cloud Migration Tool
This is the recommended path for most businesses, and for good reason. Microsoft built this tool specifically to move GP data into Business Central, and it automates the majority of the data transfer process.
Technical Requirements
Before you can use the automated tool, your environment needs to meet these prerequisites:
Dynamics GP 2015 or later (older versions must first be upgraded)
SQL Server 2016 or later
SQL Database compatibility level 130 or higher
SUPER permissions in your Business Central online tenant
All batches posted, default posting accounts in place, no duplicate or unbalanced entries
If your environment does not meet these requirements - particularly around GP version - you will need to either upgrade GP first or use the manual path.
How It Works
The process runs through five main steps:
Step 1 - Set up the migration connection. In your Business Central online tenant, run the "Cloud Migration Setup" wizard and select Dynamics GP as your source system. You will enter a SQL connection string to your GP database. If you do not already have a self-hosted Integration Runtime installed, the wizard will prompt you to download and install it on a machine that can reach your GP SQL Server.
Step 2 - Configure the migration. Once connected, the GP Company Migration Configuration page opens. You select which companies to migrate, and the tool auto-maps your GP account segments to Business Central account numbers. At this stage you also define your Global Dimensions (up to two) and Shortcut Dimensions (up to eight) - decisions that affect how you will analyze data in BC going forward, so they deserve careful thought.
Step 3 - Run data replication. From the Cloud Migration Management page, you initiate the data replication process. The tool copies your on-premises GP data, table by table, to your Business Central online environment. For large datasets, this may need to run more than once.
Step 4 - Run data upgrade. After replication completes, the status will show "Upgrade Pending." Running the data upgrade converts the replicated data into Business Central's data model.
Step 5 - Post-migration validation. Thorough testing to confirm GL balances match, open transactions are accurate, and everything that should have come across did so correctly.
Important: Always run at least one trial migration in a sandbox environment before touching your production data.
What the Automated Tool Does Not Handle
The automated tool is powerful, but it has limitations worth knowing upfront. It does not migrate data from third-party ISV solutions - those need separate planning. It also has limited support for highly customized environments. And while it preserves more historical data than a manual migration, its ability to handle extremely complex or non-standard GP setups varies.
Path 2: Manual Migration
The manual path is necessary when the automated tool cannot be used - typically because your GP version predates 2015, or because your environment is heavily customized in ways the automated tool cannot accommodate. It is more labor-intensive, but it gives you more control over exactly what moves and how.
Tools Used
SQL Server Tools - to export data from the GP database
Configuration Packages (RapidStart) - a native Business Central feature for importing data from Excel or CSV files
How It Works
Step 1 - Data export from GP. Identify the relevant master data tables in your GP SQL database - customers, vendors, items, chart of accounts - and export them to flat files using SQL Server tools.
Step 2 - Data transformation. This is the most critical and time-consuming step. The exported data must be cleaned and restructured to match Business Central's data model. This covers master data, chart of accounts (flattening GP segments into BC dimensions), open balances (AR, AP, GL), open transactions, and historical data decisions.
Step 3 - Data import into Business Central. Using Configuration Packages in BC, you create a package for each data set, export a pre-formatted Excel template with the correct column headers, paste your transformed GP data in, and import it back. BC runs validation checks before loading the data.
Limitations of the Manual Path
The manual path has real constraints that are worth being clear about:
Detailed historical transaction data typically does not migrate - you will usually bring over summary balances rather than line-level history
There is no automatic field mapping, which increases the risk of errors if the transformation step is not done carefully
ISV and customization data must each be handled individually with separate plans
The process requires significant technical expertise and time
Choosing Between the Two: A Summary
Factor | Automated Tool | Manual Migration |
|---|---|---|
GP Version Required | GP 2015 or later | Any version |
Implementation Effort | Low to Medium | High |
Historical Data | More is preserved | Typically summary only |
Customization Support | Limited | Flexible |
ISV Data | Not supported | Must handle separately |
Risk of Error | Lower | Higher without careful execution |
For most organizations on GP 2015 or later with a reasonably standard environment, the automated tool is the right choice. If you are on an older version or have a heavily customized setup, the manual path is viable - but it needs experienced hands and more time budgeted.
If you are unsure which path applies to your environment, the discovery phase of your implementation is the right time to make that determination. A proper assessment of your GP version, database state, customizations, and ISV solutions will tell you clearly which direction to go.
Next in This Series
In Part 5, we cover the mistakes we most commonly see in GP to BC migrations - and specifically how to avoid them.
Evolve Strategy & Capital Inc. is a senior Microsoft Dynamics 365 Business Central consulting firm based in Calgary. We have direct experience with both automated and manual GP to BC migrations. If you want an honest assessment of which path makes sense for your environment, book a discovery conversation with our team.
Comments