The GP to Business Central Cloud Migration Tool: What It Does and Where It Stops

The GP to Business Central Cloud Migration Tool: What It Does and Where It Stops

https://www.nevastech.com/blog/wp-content/uploads/2026/01/Gemini_Generated_Image_85xsyk85xsyk85xs.png By John Solomon
15 November 2026
The GP to Business Central Cloud Migration Tool: What It Does and Where It Stops

When companies start planning their move from Microsoft Dynamics GP to Dynamics 365 Business Central, one question comes up very early: does Microsoft have a tool that moves our data for us?

The answer is yes. Microsoft provides a cloud migration tool built specifically for GP customers moving to Business Central. It is free, it is maintained by Microsoft, and it handles a large share of the data movement.

But it is important to recognize what the tool is, and what it is not. It moves data. It does not redesign your processes, rebuild your reports or replace your add-ons. In this article, we explain in plain terms what the tool does, how it works, and where your project team needs to take over.

What Is the Cloud Migration Tool?

The cloud migration tool is a set of features inside Business Central online that connects to your on-premises GP SQL Server database and copies selected data into a Business Central environment in Microsoft’s cloud.

A few basics are worth knowing from the start:

  • It only targets Business Central online. It is not designed for moving GP data into Business Central on-premises.
  • It needs GP 2015 or later. Older GP versions must be upgraded first.
  • It is run from Business Central. You use an assisted setup guide, and it uses Azure Data Factory and a small integration runtime installed on your network to move the data securely.
  • Your GP system keeps running. GP remains your live system until you complete the migration and go live.

How the Migration Process Works

Microsoft describes the process in a series of clear stages. Summarizing them simply:

  1. Assessment: Microsoft offers a migration assessment tool that reviews your GP structure and highlights potential issues before you begin.
  2. Preparation: You plan the timeline, confirm prerequisites and clean your data in GP.
  3. Setup: You run the Set up Cloud Migration guide in Business Central, connect to your GP database and choose which companies to migrate.
  4. Configuration: You decide exactly what to bring across using the GP Company Migration Configuration page, such as modules, inactive records, classes and history.
  5. Data replication: The tool copies data from GP into Business Central. You can run this several times, which is very useful for testing.
  6. Data upgrade: The copied data is converted into Business Central records.
  7. Validation: Business Central compares the migrated data with GP and highlights differences.
  8. Completion: You finish the setup, configure users and go live.

We want to emphasize one important rule from Microsoft: never run the tool against a Business Central production environment that is already in use, because migrated data can overwrite existing records. The usual approach is to test in a sandbox first, then run the final migration into a fresh production environment.

What the Tool Migrates

The tool covers more than many people expect. Based on Microsoft’s documentation, it can bring across the following.

General Ledger

  • Fiscal periods become accounting periods in Business Central.
  • Chart of accounts. The main account segment becomes the Business Central account number, and the other segments become dimensions. You choose which two segments become global dimensions, and the rest are set up as shortcut dimensions.
  • Summary balances for open and historical years, based on your GP fiscal periods. You choose the oldest year to bring across.
  • Unit accounts become statistical accounts.

Receivables

  • Customers, with the option to leave out inactive ones, and all their addresses as ship-to addresses.
  • Customer classes as customer posting groups, if you choose.
  • All outstanding receivables transactions, brought across at the remaining amount.

Payables

  • Vendors, with the option to leave out inactive ones, and all their addresses.
  • Vendor classes as vendor posting groups, and vendor EFT details as vendor bank accounts.
  • All outstanding payables transactions, at the remaining amount.
  • 1099 information, from 2024 onwards.
  • Open purchase orders, for quantities not yet received and invoiced.

Inventory

  • Items, with their valuation method, locations and quantities on hand.
  • Serial and lot numbers where tracked.
  • Item classes as inventory posting groups, with options to leave out inactive or discontinued items.

Bank

  • Checkbooks, with the option to migrate only active ones.
  • Unreconciled bank transactions, so you can complete reconciliations in Business Central.

Historical Detail

The optional GP Historical Snapshot can bring detailed history for General Ledger, Receivables, Payables, Sales Order Processing, Purchase Order receipts and Inventory into separate tables in Business Central. Users can view this information through GP Detail Snapshot pages, and it can also be used in Power BI. It does not post to your live ledger, so your new books stay clean.

Where the Tool Stops

This is where planning really matters. The tool is a data mover, and there are several areas it does not cover.

1. Your Customizations

Any GP modifications, Dexterity customizations, VBA code or Modifier changes do not come across. If a process depends on them, it needs to be redesigned in Business Central, often through extensions or standard features.

2. Third-Party Add-on Data

Many GP customers rely on add-ons from independent vendors. The tool focuses on standard GP tables, so add-on data usually needs a separate plan, either through the vendor’s own migration path or a custom approach.

3. Modules Outside the Standard Scope

Microsoft’s list focuses on core financials, receivables, payables, inventory, bank and purchase orders. Areas such as payroll, fixed assets, project accounting, manufacturing and open sales orders are not part of the standard list, so they need to be reviewed and handled separately.

4. Reports and SmartLists

Your GP reports, SmartList favorites, Management Reporter statements and Excel reports do not migrate. They need to be rebuilt using Business Central reports, financial reporting, Excel integration or Power BI.

5. Users, Security and Workflows

User accounts, security roles and approval workflows must be set up again in Business Central, which uses a different permission model.

6. Some Data Needs Preparation First

For example, undeposited cash receipts are not migrated, so they should be deposited in GP before the final run. Historical years also come across as open and must be closed in Business Central afterwards.

7. Different Concepts

Some GP features have no direct match. Unit of measure schedules, for example, do not exist in Business Central, which manages units of measure per item instead. The tool cannot decide how your business should work in the new system. That is a design decision for your team.

How to Get the Most from the Tool

From our experience on GP migration projects, these steps make a real difference:

  • Clean your data in GP first: Remove duplicate customers and vendors, mark inactive records and tidy up items before the first run.
  • Review your account segments early: Deciding which segments become global dimensions shapes your reporting for years.
  • Decide on history carefully: More history means longer runs and more to check. Many organizations bring summary balances plus a few years of Historical Snapshot detail, and archive the rest.
  • Run several test migrations: Each run reveals something new. By the final run, the process should be predictable.
  • Reconcile thoroughly: Use the built-in validation, then compare trial balances, aged receivables, aged payables and inventory values yourself.
  • Plan the gaps alongside the tool: Customizations, add-ons, reports and security should be designed in parallel, not after the data has moved.

Frequently Asked Questions

Is the GP cloud migration tool free?

Yes. It is included with Business Central online. You still need to plan the project, prepare your data and configure Business Central, which is where most of the effort lies.

Which Dynamics GP versions does the tool support?

Microsoft lists GP 2015 or later as a prerequisite. If you are on an older version, you need to upgrade GP before using the tool.

Can the tool migrate to Business Central on-premises?

No. The tool is designed for Business Central online. Moves to on-premises usually rely on configuration packages and other import methods.

Can I keep using GP while the migration is running?

Yes. GP remains your live system until you complete the migration. Business Central is effectively read-only for migrated data during this period.

How Nevas Technologies Can Help

The cloud migration tool is a strong starting point, but a successful move needs more than a data transfer. At Nevas Technologies, we have more than two decades of experience with Microsoft Dynamics, and our Dynamics GP to Business Central migration service combines Microsoft’s tool with careful planning for everything it does not cover.

We help you assess your GP system, configure the migration, redesign customizations, rebuild key reports and train your team. Our Business Central implementation plans, training and Business Central consultants make sure your team is ready from day one, and our Dynamics GP support team keeps GP stable until you go live.

Planning your move to Business Central? Schedule a demo, or contact our team for a free migration assessment.

https://www.nevastech.com/blog/wp-content/uploads/2026/01/Gemini_Generated_Image_85xsyk85xsyk85xs.png
About the author:

John Solomon

Director, Business Central

John Solomon is a technology professional with extensive experience helping businesses improve their systems, processes, and digital transformation.