Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Accounting

ERP

Dynamics GP to Business Central Migration: Tools, Data Scope and Timeline

Sherman Hsieh
Share This Post!
Published
Dynamics GP to Business Central Migration: Tools, Data Scope and Timeline

Last updated: November 4, 2026 · Independent guide · We do not sell rankings or coverage.

A Dynamics GP to Business Central migration moves your GP master data, open transactions and summary general ledger history into Dynamics 365 Business Central online, usually with Microsoft’s Cloud Migration tool. The tool does not bring over paid transaction detail, payroll, users, customizations or most third-party add-on data, so you need a plan for history, ISV replacements and reporting before you start. Microsoft ends GP technical support and tax updates on December 31, 2029 and security updates on April 30, 2031, and partners publish project timelines from about eight weeks for a single, simple company to a year or more for complex estates.

The migration in eight stages

Microsoft splits the technical work into assessment, preparation, setup, company configuration, replication, data upgrade, validation and completion (Microsoft Learn, December 13, 2024). The business stages below wrap around those steps.

  1. Confirm your deadline, licensing and target (Business Central online or on-premises).
  2. Assess your GP system: companies, modules, add-ons, customizations, integrations and data volumes.
  3. Decide the data scope and how you will keep GP history.
  4. Replace or rebuild ISV add-ons, reports and customizations.
  5. Prepare the environment and meet the tool’s prerequisites.
  6. Run at least two dry runs in a sandbox: replicate, upgrade, validate.
  7. Cut over: freeze GP, run the final replication and data upgrade, validate and go live.
  8. Stabilize: set up users and permissions, close historical years, archive GP.
Stage Accountable Main output
1. Deadline and target CFO or controller Target go-live date and budget
2. Assessment Project sponsor Inventory of companies, add-ons, integrations, gaps
3. Data scope and history Controller Signed-off data scope and archive plan
4. ISVs and customizations IT lead Replacement list and extension backlog
5. Environment IT lead Sandbox, integration runtime, prerequisites met
6. Dry runs Partner project manager Timed runbook and reconciled test data
7. Cutover Controller Signed trial balance and subledger tie-out
8. Stabilize Controller First clean month-end close in Business Central

The owners are our recommended split, not a Microsoft requirement. Your partner does most of the hands-on work in stages 2 through 7.

Stage 1: Confirm the GP support timeline and your target

Microsoft announced the end of GP support in September 2024 and later moved the date. Product support and updates now end on December 31, 2029, a change Microsoft made so customers could complete a full payroll and tax year, and security patches end on April 30, 2031 (Microsoft Dynamics 365 Blog, September 25, 2024, updated January 15, 2025).

Microsoft’s June 2025 post adds the licensing milestones. April 1, 2026 was the last day for new customers to license GP subscriptions. On April 30, 2031, Service Plan coverage ends, SPA and DPL subscription licenses can no longer be renewed, you can no longer add perpetual users, and SPLA subscription use is expected to end (Microsoft Dynamics 365 Blog, June 5, 2025). Neither post announces a GP transition discount.

Your practical deadline is earlier. To file 2029 year-end forms from a supported system, go live in Business Central at the start of a fiscal year before then. Also decide whether you are moving to Business Central online, because Microsoft’s GP Cloud Migration tool targets online only (Microsoft Learn, December 13, 2024), so an on-premises Business Central target needs a different, partner-built data load.

GP vs Business Central: what changes for your team

Area Dynamics GP Business Central online What it means for you
Deployment On-premises SQL Server or partner hosted Microsoft-hosted SaaS No server upgrades, but no direct SQL access
Updates You schedule version upgrades Two major releases a year, in April and October, plus minor updates in each other month Extensions must keep up with each release
Chart of accounts Segmented account string Main account plus dimensions The tool maps the main segment to the account and other segments to dimensions
Financial reporting Management Reporter, SmartList Built-in financial reporting with row and column definitions, Power BI Reports are rebuilt, not converted
US payroll Native module No native payroll module Choose a payroll app or outside provider
Customization Dexterity, VBA, modified forms and reports AL extensions only Custom code is rewritten or replaced
Licensing Perpetual or subscription, plus annual plan Essentials $80, Premium $110, Team Members $8 per user per month, paid yearly Premium is needed for manufacturing and service management

Sources: update cadence from Microsoft Learn (October 8, 2026), account mapping from Microsoft Learn (January 15, 2026), payroll from Sylogist (June 15, 2026; Sylogist sells a Business Central payroll product), and prices from Microsoft’s pricing page (no date shown, checked November 4, 2026). If you run manufacturing in GP, read our Business Central manufacturing guide before you pick a tier.

Stage 2: Assess your GP system

Your project sponsor owns this stage and the partner does most of the work. Inputs are your companies, modules, add-ons, integrations and database sizes; the output is a gap list and a scope estimate.

Microsoft offers a migration assessment tool at bcmigrationassessments.com that reports readiness and flags likely issues based on your GP system structure (Microsoft Learn, March 1, 2024). The usual failure here is an incomplete add-on list, so ask each department which GP windows, SmartLists and Excel exports it uses every month.

Stage 3: Decide data scope and history

The controller owns this stage because it affects audit, tax and reporting. The output is a signed data scope and archive plan.

What the Cloud Migration tool brings over

Area What migrates What does not, or needs a decision
General ledger Accounts, fiscal periods, summary transactions for open and historical years; unit accounts as statistical accounts Years before the “Oldest GL Year” you set; historical years arrive open and must be closed
Receivables Customers (all or active only), addresses, open transactions at remaining balance, optional classes as posting groups Paid portions of documents; undeposited receipts
Payables Vendors, remit-to and order addresses, EFT bank details, open transactions at remaining balance, open PO quantities, 1099 data 1099 data before 2024; fully received and invoiced PO lines
Inventory Items at the GP valuation method, locations, quantity on hand, serial and lot tracking, units of measure Unit of measure schedules (no equivalent); inactive or discontinued items unless included
Bank Checkbooks and unreconciled bank transactions Reconciled bank history
Not listed by Microsoft None Payroll, fixed assets, project accounting, manufacturing, users, permissions, ISV tables

The table summarizes Microsoft’s data list (Microsoft Learn, January 15, 2026). Microsoft does not list payroll, fixed assets, project accounting or manufacturing, so plan to load those with configuration packages or a partner tool. Users and permissions never migrate (Microsoft Learn, May 8, 2026).

The remaining-balance rule matters for your aged reports. As an illustration, a $1,000 customer invoice on which $400 has been paid arrives in Business Central as a $600 open invoice, so the aging ties out but the original amount is not on the document. Deposit all posted receipts in GP before the final run.

Your history options

Most companies combine two or more of these options.

  • Summary GL history. Set the Oldest GL Year on the GP Company Migration Configuration page to bring in period totals for that year and later (Microsoft Learn, May 8, 2026).
  • GP Historical Snapshot. The tool can copy GL detail, receivables, payables, sales order processing, purchase receipts and inventory transactions into separate history tables for lookup and Power BI reporting. An Oldest Snapshot Year field limits the volume, and the snapshot runs in the background after migration (Microsoft Learn, January 15, 2026).
  • Archive to Azure Data Lake. Microsoft notes you can copy the GP database to Azure Data Lake for reference after migration (Microsoft Learn, March 1, 2024). Tools such as Popdock can access GP history stored in the data lake (Encore, July 3, 2024; Encore is a Microsoft partner selling services).
  • Keep GP read-only. This works for lookups until security updates end on April 30, 2031.

Snapshot volume counts against your storage. Business Central online includes 80 GB plus allowances per licensed Essentials or Premium user, and Microsoft recommends keeping each migration run under 30 GB (Microsoft Learn, June 19, 2026). Agree retention periods with your auditors before you pick the oldest years.

Stage 4: Replace ISV add-ons and customizations

The IT lead owns this stage. The output is a replacement decision per add-on and a backlog of AL extensions.

Microsoft’s migration FAQ says only tables available in both the source and the Business Central online tenant migrate, and customizations must be converted to extensions. Microsoft lets you define table mappings to move data from custom fields into standard or extension fields (Microsoft Learn, June 19, 2026). Before rewriting a Dexterity customization, check whether standard Business Central already covers it.

  • Payroll. Business Central has no native payroll module (Sylogist, June 15, 2026). Choose an embedded AppSource payroll app or an outside provider that posts a journal, and switch on January 1 if you can.
  • Management Reporter. Business Central has built-in financial reporting with row and column definitions, and you can export and import row definitions as RapidStart configuration packages (Microsoft Learn, May 12, 2026). Management Reporter is not available for Business Central (Solver, April 8, 2023, updated July 23, 2026; Solver sells reporting software), so budget time to rebuild reports.
  • Check printing and multi-entity add-ons. Encore reports that Mekorma and Binary Stream both offer Business Central versions on AppSource (Encore, July 3, 2024). Confirm feature parity, because these are separate products.
  • SmartList and inquiry tools. Microsoft’s Dynamics GP History SmartLists app is one of the required migration apps (Microsoft Learn, May 8, 2026). Ad hoc lists move to Business Central list pages, Edit in Excel and Power BI.

Stage 5: Prepare the environment

The IT lead and SQL administrator own this stage. Microsoft’s prerequisites are specific (Microsoft Learn, May 8, 2026):

  • Dynamics GP 2015 or later. Older versions must be upgraded first.
  • SQL Server 2016 SP1 or later, compatibility level 130 or higher, TCP/IP enabled, and SQL authentication with sysadmin and db_owner rights.
  • A self-hosted integration runtime on the network that holds the GP database.
  • The Intelligent Cloud Base, Dynamics GP Intelligent Cloud and Dynamics GP History SmartLists apps installed in Business Central, plus Dynamics GP Intelligent Cloud US for US companies.
  • A user with SUPER permissions who is also a Microsoft 365 administrator.
  • Assisted setup is supported only for the United States, Canada, the United Kingdom and Australia.

Microsoft says to use full backups (differential and partial backups are not supported), to avoid updating either environment while migration is enabled, and never to point migration at a Business Central production environment already in use, because replication can overwrite data (Microsoft Learn, March 1, 2024). Clean up GP data now: purge inactive records, deposit receipts and reconcile checkbooks.

Stage 6: Run dry runs in a sandbox

The partner project manager owns the runbook, and key users own testing. In Business Central you open Cloud Migration Setup, connect to SQL Server, select companies and complete the GP Company Migration Configuration page (Microsoft Learn, May 8, 2026). You then replicate, run the data upgrade and validate.

Microsoft’s general cloud migration guidance is to plan at least two dry runs: one to find technical issues and time the run, and a second to confirm fixes and complete business validation (Microsoft Learn, June 19, 2026). The tool migrates table by table, and a table whose schema does not match fails while the run continues (Microsoft Learn, December 13, 2024), so read the error log each time. Controls are a trial balance tie-out by period, AR and AP agings, inventory value by location and unreconciled bank items by checkbook.

Stages 7 and 8: Cut over, go live and stabilize

The controller owns the go or no-go decision. Stop GP posting, take the final full backup, run the final replication and then the data upgrade. Once the data upgrade starts, all client connections are terminated, and after it succeeds you cannot replicate again from the earlier data (Microsoft Learn, May 8, 2026).

Run validation from Cloud Migration Management with Actions > Validation Status > Run All Validation, resolve errors, then select Complete Cloud and Disable Cloud Migration (Microsoft Learn, May 8, 2026). Disable migration before anyone posts, because each run overwrites changes in the online company.

For Stage 8, set up users with Microsoft 365 accounts, licenses and permission sets, since none of these migrate. Close the historical years that arrived open. Reconcile the migrated unreconciled bank transactions in your first bank reconciliation; our guide to Business Central bank reconciliation covers that workflow.

A realistic timeline

Integrato lists an eight-week fixed-fee GP to Business Central offer that assumes up to two entities, moderate data volumes and Microsoft’s standard migration tool, and says multiple GP companies, extensive add-ons or large history sets need a timeline and cost discussion (Microsoft Marketplace listing, no date shown; Integrato sells this service). Zenzero, a UK partner, gives 3 to 4 months for simple migrations, 5 to 8 months for mid-level and 9 to 12 months or more for complex ones (Zenzero, April 13, 2026; Zenzero sells implementation services).

Phase One company, few add-ons Several companies, payroll and ISVs
Assessment and scope 2 weeks 4 to 6 weeks
Environment, setup, ISV replacement 2 weeks 8 to 12 weeks
Dry runs, reports and testing 3 weeks 8 to 12 weeks
Cutover and first close 1 to 4 weeks 4 to 6 weeks
Total About 2 to 3 months About 6 to 9 months

Illustration only, built from the published ranges above. For budget ranges, see our guide to ERP implementation cost.

Metrics to track

  • Trial balance variance between GP and Business Central by period, with a target of zero.
  • Subledger tie-out: AR aging, AP aging and inventory value matched to the GL control accounts.
  • Validation errors per dry run, which should fall to zero before cutover.
  • Replication and upgrade duration per run (this sets your cutover freeze).
  • Add-ons resolved: GP add-ons with a confirmed replacement or retirement.
  • Days to first close in Business Central compared with your GP close.

How software supports each stage

The assessment tool covers Stage 2, and the Cloud Migration tool with its Historical Snapshot covers Stages 3, 6 and 7. Configuration packages load what the tool skips, such as fixed assets. Financial reporting and Power BI replace Management Reporter, AppSource apps fill add-on gaps, and tools such as Popdock cover archived history. If you are still choosing a target, see our NetSuite vs Business Central guide.

How we researched this

We read Microsoft’s GP lifecycle announcements and every Microsoft Learn page in the GP cloud migration path, including prerequisites, setup, company configuration, data upgrade, completion and the migration FAQ. We checked Business Central list prices on Microsoft’s pricing page on November 4, 2026. We reviewed top-ranking partner guides and Marketplace listings for published timelines, and we note where a source sells services or software. No vendor or partner paid for coverage.

Related guides

Frequently asked questions

Is the GP to Business Central migration tool free?

Microsoft’s migration documentation does not list a separate charge for the Cloud Migration tool, which you run from inside Business Central online. You still pay for licenses, any extra storage and partner time.

Does the migration tool bring over all my GP history?

No. It brings summary GL totals for the years you select and open AR, AP and purchase order balances. Detail can come over as read-only Historical Snapshot records, and older data can be archived to Azure Data Lake.

Can I keep using GP after December 31, 2029?

The software will keep running, but Microsoft will stop technical support, product updates and tax updates on that date. Security updates and Service Plan coverage end April 30, 2031.

What happens to my GP payroll?

Business Central has no native payroll module, so you move to a payroll app from AppSource or an outside provider. Switching on January 1 keeps each employee’s W-2 in one system.

How long does a GP to Business Central migration take?

Published partner figures range from eight weeks for a fixed-scope single-company project to 9 to 12 months or more for complex estates with many companies, add-ons and integrations. Microsoft recommends at least two dry runs before cutover.

Sources

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read