Skip to main content
Partner Stories

Dynamics GP to Business Central Migration [A Must Read for Finance Leaders]

If you still run Microsoft Dynamics GP, the decision in front of you is no longer whether to move. Microsoft has stopped selling new GP licences, and the support runway now has a firm end date. The decision that actually determines whether your migration is smooth or painful is how you move — and most teams get that decision wrong before the project even starts.

This guide is written for finance and operations leaders who have used GP for years, know it inside out, and are understandably cautious about giving it up. It covers the full picture — support timeline, migration approach, what data moves, licensing and the Bridge to Cloud incentive, tooling, timeline, and cost — with the depth of a consultant who has delivered these projects, not a brochure.

The clock GP customers can no longer ignore

Let's set the facts straight, because there is a lot of noise online.

Microsoft stopped selling new perpetual GP licences on 1 April 2025 and stopped new subscription licences on 1 April 2026. For customers already on GP, support continues — but not indefinitely. Product enhancements, regulatory and tax updates, service packs, and technical support end on 31 December 2029. Security updates continue until 30 April 2031.

Read that through a finance lens: after the end of 2029, your ERP stops receiving payroll and tax-table updates. For a system at the centre of your statutory reporting, that is not a background IT risk — it is a compliance liability with a countdown.

The takeaway is about timing your move, not panicking. A migration planned in 2026 or 2027 has room to be done properly, in phases, with your pick of an experienced partner. A migration forced in 2029 — when tax updates are expiring and every other GP customer is moving at once — will cost more, move faster than is comfortable, and compete for scarce implementation capacity. The cost of waiting is real, and it compounds.

Why this is not a lift-and-shift — and why that matters

Here is the single most important thing to understand, and the point most competing pages skip: moving from Dynamics GP to Business Central is not a lift-and-shift. It is a structural translation.

GP was built on Dexterity, with a segmented general ledger where account meaning is encoded into the account number itself. Business Central is a cloud-native platform built on AL, where that same analytical richness is expressed through dimensions — a fundamentally different and far more flexible model.

When teams treat the move as a straight copy — dragging GP's segment structure directly into Business Central — the result is predictable and expensive. You end up with a bloated chart of accounts, a reporting model that ignores the very feature that makes Business Central powerful, and a financial setup that gets harder to maintain as the business grows. Six months after go-live, someone in finance is asking why the "new system" is more awkward to report from than the old one. The technology was never the problem. The translation was.

This is why the quality of your partner matters more here than in almost any other ERP project. The migration is not a data-copy exercise. It is a chance to redesign how your business measures itself — and to lock in cleaner reporting for the next decade.

The decision that shapes everything: re-implementation vs. data lift

Almost every downstream cost, timeline, and risk traces back to one early choice: do you re-implement, or attempt to carry everything across?

A data lift feels comforting. Bring it all — every historical transaction, every legacy account, every workaround accumulated over fifteen years. It seems lower-effort. In practice it imports your technical debt into a brand-new system, and you pay to maintain that debt forever.

A re-implementation treats Business Central as a fresh start. You migrate master data (customers, vendors, items, chart of accounts), open transactions (open AR, open AP, outstanding orders), and opening balances. Historical detail is preserved in an archive for audit and statutory needs, rather than cluttering the live system. Crucially, you get to re-engineer processes that no longer fit, standardise how dimensions are used, and take advantage of capabilities GP never had.

For most GP customers — especially those with messy or duplicated data, years of customisations, or a chart of accounts that has grown organically — re-implementation is the approach that pays off. The instinct to "keep everything" is the instinct that produces the costliest projects. A good partner challenges that instinct early and shows you how to keep your history accessible without dragging it into daily operations.

Translating GP account segments into Business Central dimensions

This deserves its own section because it is where the real expertise lives.

In GP, a department, location, or cost centre is typically baked into the account segment. In Business Central, those become dimensions attached to transactions. The benefit is enormous: instead of creating a new account for every combination of department and location, you maintain a lean chart of accounts and slice data by dimension whenever you report.

Done well, this is the moment your reporting gets dramatically better. A CFO who previously waited days for a consolidated departmental P&L can build it in minutes, filtered live by dimension, with Business Central's built-in analysis and Copilot-assisted insights. Done badly — by replicating GP segments as thousands of standalone accounts — you inherit all of GP's rigidity in a platform designed to escape it.

The mapping exercise (which GP segments become dimensions, which become dimension values, and which quietly disappear) should be designed up front, with someone who has done it before and knows where the traps are — not improvised mid-project.

What data moves from GP to Business Central — and what to archive

Microsoft provides a cloud migration tool for Business Central that moves core GP data into your new environment, so critical financial, operational, and master data is ready at go-live. The discipline is knowing what belongs in the live system versus what should live in an archive.

DataTypical approachNotes
Chart of accountsMigrate, redesignedGP segments mapped to Business Central dimensions — not copied as-is
Customers & vendorsMigrate (master data)De-duplicate before moving; do not import decades of dormant records
Open AR / open APMigrateOpen customer balances, unapplied amounts, open payables
Open sales & purchase ordersMigrateIncluding partially received POs
Inventory / itemsMigrateItem master, on-hand quantities, costing method
Opening balancesMigrateReconciled trial balance as the anchor
Historical transactions (years of posted detail)Archive, don't importRetain in Azure Data Lake or a reporting database for read-only access; report via Power BI

The single biggest cost and performance lever is that last row. Historical detail almost never needs to live inside the operational ERP. Keeping it accessible for audit and reference — without loading it into Business Central tables — keeps day-to-day performance fast and the migration lean.

Business Central licensing for GP customers: Essentials, Premium, Team Member

Licensing is separate from migration services, and choosing the right mix is part of controlling total cost. Business Central Online has three core user types:

LicenceBest forIncludes
EssentialsMost GP finance/distribution customersFull core ERP: financial management, AP/AR, purchasing, sales, inventory, warehousing, project management
PremiumManufacturers and service organisationsEverything in Essentials plus Manufacturing and Service Management (production orders, BOMs, capacity planning, service contracts, dispatch)
Team MemberLight/occasional usersRead access across most of the system, plus limited actions (approve workflows, enter timesheets, update own records). Cannot post transactions or create master records

A common mistake is licensing every user at Essentials or Premium. Many organisations have a tier of approvers and viewers who fit Team Member, which materially reduces monthly cost. Map your user roles before you buy. 

Bridge to Cloud 3: how GP customers cut Business Central licensing by 30%

This is the incentive that changes the "why now" maths — and it has a deadline.

Microsoft's Bridge to Cloud 3 (BTC3) promotion gives qualifying on-premises Dynamics customers a 30% discount on Business Central Online licences, locked in for three years. For GP-to-Business Central moves specifically, the value can be even greater: Microsoft has offered "$0 users" — effectively free cloud user licences — based on the value of the customer's active Enhancement Plan, requestable annually within the promotional window.

Key terms to check against your situation:

  • Eligibility: you generally must have purchased on-premises Dynamics licences before 1 September 2024 and hold an active Enhancement Plan. Customers who used a previous Bridge to Cloud promotion are typically not eligible again.
  • Deadline: BTC3 is an active promotion running through 31 December 2027. The discount is most valuable when claimed early, because the three-year lock starts from when you transition.
  • Dual access rights: you can keep using and upgrading GP while Business Central is designed, built, and tested in parallel. There is no forced cutover that pulls the old system out from under your team.

Two things follow. First, the financial case for moving is strongest now, while the discount and dual access are available. Second, the eligibility rules are specific enough that you want a partner to confirm your entitlement before you plan the budget. (Internal link: free GP migration assessment.)

Matching migration scope to your business

Not every GP customer needs the same migration. Scope by functional area, and phase anything that isn't core to go-live:

  • Core financials: general ledger (redesigned to dimensions), AP, AR, cash management/bank reconciliation, multi-currency, standard financial reporting, and Power BI dashboards. This is the foundation every migration includes.
  • Sales & distribution: inventory with costing, sales orders and invoicing with customer/item pricing, purchase orders with receiving and invoice matching, and basic warehouse pick/pack/put-away.
  • Projects: job and project tracking, timesheets with approval, WIP, revenue recognition, and project invoicing.
  • Manufacturing: production orders with backflushing, bills of materials, routings, and capacity planning (Premium licence).

A practical pattern that reduces risk: migrate core financials (and distribution, if you sell physical goods) first, then schedule custom development, integrations, and third-party apps as a Phase 2 after go-live so they don't delay the core cutover.

How the migration actually runs: the cloud migration tool and a phased methodology

A disciplined GP-to-Business Central project usually follows these phases:

  1. Assessment & design. Review your GP estate, data quality, customisations, integrations, and reporting needs. Decide re-implementation versus data lift, map GP segments to dimensions, define the target chart of accounts, and agree what history is archived versus migrated. This is where the biggest risks are removed — cheaply.
  2. Test migration. Microsoft's cloud migration tool moves GP data into a test Business Central environment so users can review converted data, catch issues, and confirm the approach before it's real.
  3. User acceptance testing & training. Users test key workflows while completing role-based Business Central training. Configuration and data conversion are adjusted from testing feedback.
  4. Final migration & go-live. The production cut-over is completed with a support safety net so the team can begin transacting with minimal disruption.
  5. Phase 2: extensions. Custom development, integrations, and third-party apps not in the core scope are delivered after go-live.

Notice the work that determines success is front-loaded. Teams that rush the assessment to "save time" pay for it during data validation.

What a realistic timeline looks like

Timelines vary with scope, data quality, integrations, and customisations. As planning brackets:

  • Standardised, fixed-scope core-financials migrations: commonly around 8–12 weeks.
  • Broader multi-module re-implementations (distribution, projects, or manufacturing): commonly 3–7 months, often phased.
  • Complex, multi-entity, or heavily customised estates: longer, and best delivered in stages.

Treat these as directional, not quotes — the honest answer to "how long?" starts with an assessment. What the brackets do tell you is that a project started now, in 2026, completes with room to spare before the 2029 support cliff. A project started in 2028 does not have that luxury.

What actually drives migration cost

Any partner who quotes a number before understanding your estate is guessing. What's useful is knowing the levers that move the cost, so you can control them:

  • Data quality and volume. Clean master data and a disciplined decision about how much history to migrate is the single biggest lever. Archiving rather than importing legacy detail often saves more than any other choice.
  • Customisations and ISV add-ons. Each GP customisation must be assessed: rebuild, replace with standard functionality, or retire. Many "must-have" customisations are standard features in Business Central — cutting both cost and long-term maintenance.
  • Integrations. Connections to CRM, payroll, banking, warehouse, or e-commerce each add scope; Business Central's native ties to the Microsoft ecosystem (Power BI, Power Automate, Dynamics 365 Sales) often simplify them.
  • Number of legal entities and users. Multi-company and multi-currency estates need more configuration and testing.
  • Licensing, offset by Bridge to Cloud 3. Licences are a separate line from services — but BTC3's 30% discount and $0-user offer can materially reduce the first three years.

The lowest-cost migration is rarely the one that changes the least. It's the one that makes disciplined decisions early about what to leave behind.

Common mistakes that turn a clean migration into an expensive one

  1. Copying the GP chart of accounts verbatim. The number-one regret — it imports GP's rigidity into a platform built to escape it.
  2. Migrating all historical data "just in case." It inflates cost, slows the system, and is almost never used operationally. Archive it to Azure Data Lake / Power BI instead.
  3. Rebuilding customisations no one uses. Audit first. Business Central may already do it, better.
  4. Over-licensing users. Approvers and viewers often fit Team Member, not Essentials.
  5. Leaving Bridge to Cloud 3 on the table. Missing the discount or the eligibility window is money left unclaimed.
  6. Starting too late. Waiting until 2028–2029 shrinks options and inflates price when partner capacity is scarcest.
 Dynamics GPDynamics 365 Business Central
ArchitectureOn-premises, DexterityCloud-native, AL extensions
GL modelSegmented account structureDimension-based
UpdatesManual, ending (support to 2029/2031)Continuous, twice-yearly release waves
Microsoft 365 integrationLimitedNative (Outlook, Excel, Teams)
AnalyticsAdd-on / manualBuilt-in reports + Power BI
AINoneCopilot included; agentic ERP (e.g. Payables Agent) expanding in 2026 wave 1
Long-term roadmapEnd of lifeMicrosoft's recommended SMB ERP

Copilot and agents are available to Business Central online customers — another reason the destination is the cloud, not a hosted copy of the old system.

Where Dynamics Square fits

Dynamics Square is a Microsoft Solutions Partner that focuses on Business Central migrations for exactly this kind of customer — established GP users who cannot afford a disruptive move. Our consultants have delivered the segment-to-dimension translation many times, and we start every engagement with an assessment rather than an assumption. That means you know your realistic timeline, your cost drivers, your licensing entitlement (including Bridge to Cloud 3), and your risks before you commit to anything.

If you're mapping out your move, the most useful next step is not a sales call — it's a clear-eyed look at your own estate.

Book a free GP migration assessment with a Microsoft-certified consultant. We'll review your GP setup, confirm your Bridge to Cloud eligibility, flag the decisions that most affect cost and risk, and give you a realistic roadmap — whether or not you work with us.

You may also want to compare Business Central licensing and pricing, review our Business Central implementation methodology, or read a GP migration case study from a business like yours.

The support clock is running, and the strongest licensing incentive has a deadline. A move planned now, with the right approach, is far less disruptive than the version you're probably imagining.


Frequently Asked Questions

Is Dynamics GP really being discontinued? 

Yes. Microsoft has stopped selling new GP licences and published an end-of-life roadmap. New perpetual licence sales ended 1 April 2025 and new subscription sales ended 1 April 2026. Product enhancements, tax and regulatory updates, and technical support end 31 December 2029, with security updates ending 30 April 2031. GP still runs, but after 2029 it no longer receives the tax and compliance updates finance teams rely on.

Can I just lift and shift my GP data into Business Central? 

Not effectively. GP's segmented, Dexterity-based structure doesn't map one-to-one onto Business Central's dimension-based model. A direct copy typically produces a bloated chart of accounts and poor reporting. Most GP customers are better served by a re-implementation that migrates master data, open items, and balances while archiving historical detail.

What data can be migrated from GP to Business Central? 

Core financial and master data — chart of accounts (redesigned to dimensions), customers, vendors, open AR and AP, inventory, and open sales and purchase orders — moves via Microsoft's cloud migration tool. Sales orders, projects, and manufacturing data can also be migrated depending on scope. Historical posted detail is usually archived rather than imported.

Do we lose our Dynamics GP history? 

No. Historical GP data can be retained through snapshot or reporting databases and read-only access — commonly loaded into Azure Data Lake and reported via Power BI — for audit and reference. Keeping it out of live Business Central tables preserves visibility without slowing the system.

How long does a GP to Business Central migration take? 

Standardised, fixed-scope core-financials migrations commonly run around 8–12 weeks. Broader multi-module re-implementations (distribution, projects, manufacturing) typically take 3–7 months and are often phased. Complex multi-entity estates take longer. Only an assessment of your specific environment gives a reliable date.

How much does a GP to Business Central migration cost? 

Cost depends on functional scope, data quality and volume, customisations, integrations, and the number of entities and users. The biggest lever is how much history you migrate versus archive. Licensing is a separate line from migration services — and Bridge to Cloud 3 can reduce it by 30% for three years. A proper assessment gives a realistic figure; anyone quoting before that is guessing.

What is Bridge to Cloud 3 and do we qualify?

 Bridge to Cloud 3 (BTC3) is a Microsoft promotion giving qualifying on-premises Dynamics customers a 30% discount on Business Central Online licences for three years, plus "$0 users" for GP-to-BC moves based on Enhancement Plan value. You generally need to have bought on-premises licences before 1 September 2024 and hold an active Enhancement Plan. It runs through 31 December 2027. Eligibility rules are specific, so confirm entitlement before budgeting.

Which Business Central licence do we need — Essentials or Premium? 

Essentials covers core ERP (financials, AP/AR, purchasing, sales, inventory, warehousing, projects) and suits most GP finance and distribution customers. Premium adds Manufacturing and Service Management for organisations running production or service operations. Light users (approvers, viewers) often fit the lower-cost Team Member licence.

What is the difference between Dynamics GP and Business Central? 

GP is an on-premises ERP on legacy architecture with a segmented GL. Business Central is a cloud-native ERP with a dimension-based model, native Microsoft 365 integration, continuous updates, built-in analytics, and Copilot AI. Business Central is Microsoft's recommended successor for SMB and mid-market organisations.

Does Business Central include AI and Copilot? 

Yes. Copilot is included with a Business Central Online licence at no extra cost, offering assistive features and task automation. Microsoft's 2026 release wave 1 expands autonomous agents — for example a Payables Agent that reads invoices, matches vendors and accounts, and prepares them for approval with human oversight. Copilot and agents are available to Business Central online customers.

Should we move to Business Central or Dynamics 365 Finance? 

For most SMB and mid-market GP customers, Business Central is the natural successor Microsoft recommends. Larger, more complex organisations may evaluate Dynamics 365 Finance. An assessment clarifies which platform fits your scale and processes.