Dynamics GP end of support (Dec 31, 2029): moving 20 to 200 user GP sites to ERPNext instead of Business Central
Short answer
Microsoft’s Dynamics GP lifecycle page says GP support ends on December 31, 2029 for product enhancements, regulatory (tax) updates and technical support, and that security updates, if needed, continue until April 30, 2031 (checked Nov 11, 2026). Microsoft is steering GP customers to Dynamics 365 Business Central, which is licensed per user: Essentials $80 / £61.50, Premium $110 / £84.60 and Team Members $8 / £6.20 per user per month, paid yearly (official US and UK pricing pages; UK prices exclude VAT). For 50 full users that is $48,000 / £36,900 a year on Essentials before partner services. ERPNext is open source under GPL-3.0 and has no per-user licence fee. You pay for hosting, implementation and support instead: Frappe Cloud lists site plans from $5 a month and servers from $40 a month. Our view: Business Central is the lower-risk move if you want Microsoft’s own GP migration tool, Microsoft 365 integration and your current partner. ERPNext makes sense for GP sites of 20 to 200 users that also run inventory, purchasing or light manufacturing, where per-user cost grows with headcount, and that will fund a proper implementation instead of a licence.
Contents
- Who this guide is for
- The GP dates, exactly as Microsoft states them
- Per-user licence vs no licence: the core cost difference
- The migration path to each option
- Mapping GP to ERPNext
- Where ERPNext fits GP sites well, and where it does not
- Business Central or ERPNext: a decision table
- A GP-to-ERPNext plan for a January cutover
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, controllers and IT leads at companies running Microsoft Dynamics GP with roughly 20 to 200 users, in the US or UK, who need to decide what replaces GP before support ends. Microsoft’s answer is Business Central. This guide puts ERPNext next to it honestly, including where Business Central is the better choice. It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources: Microsoft’s Dynamics GP lifecycle page, Microsoft’s GP end-of-support announcement (updated Jan 15, 2025), Microsoft’s GP to Business Central online migration overview and Microsoft’s GP company migration configuration guide for GP and the Microsoft migration path; the Business Central pricing page (US) and Business Central pricing page (UK) for Business Central prices; the Frappe Cloud pricing page, Frappe Cloud site plans page and Frappe Cloud server plans page for ERPNext hosting prices; and the ERPNext repository on GitHub, ERPNext Data Import documentation and ERPNext opening balance documentation for ERPNext. All checked on Nov 11, 2026.
What we do not do here
We do not estimate implementation fees for either option. They depend on your companies, modules, customisations and data, and any number we gave without seeing them would be invented. We also do not size Frappe Cloud servers for a user count without load testing your own workload.
The GP dates, exactly as Microsoft states them
| Milestone | Date | Source |
|---|---|---|
| End of product enhancements, regulatory (tax) updates and technical support for Dynamics GP (Modern Lifecycle, version 18.x) | December 31, 2029 | Microsoft GP lifecycle page |
| Security updates and patches, if needed, available until | April 30, 2031 | Microsoft GP lifecycle page |
| Previously announced end of support (superseded) | September 30, 2029 | Microsoft GP lifecycle page and the Jan 15, 2025 update to Microsoft’s announcement |
| GP 2016 / 2016 R2 extended support (Fixed Lifecycle) | Ends July 14, 2026 (already passed) | Microsoft GP lifecycle page |
| GP 2018 / 2018 R2 extended support (Fixed Lifecycle) | Ends January 11, 2028 | Microsoft GP lifecycle page |
Microsoft’s announcement explains the move from September to December 2029: it lets GP customers meet payroll and tax obligations for the full year. Two practical consequences follow. First, if you are on GP 2016 or an un-updated GP 2018, you are already on a shorter clock. Microsoft notes that installing any compatible GP tax release or hotfix on GP 2018 takes you to version 18.5 or later, which moves you onto the Modern Lifecycle. Second, 2029 is the last calendar year Microsoft’s tax updates are planned to cover. For a calendar-year company, the safest plan is to go live on the replacement for the start of a fiscal year, and no later than January 2029. Then you close 2028 in GP and run 2029 in the new system with a year of margin.
As of Nov 11, 2026 there are just over three years to the support end date. That sounds like a lot. For a GP site with several companies, add-ons and years of history, a selection, a pilot and a fiscal-year cutover easily use most of it.
Per-user licence vs no licence: the core cost difference
Business Central is licensed per user per month. The official prices on Microsoft’s US and UK pricing pages, checked Nov 11, 2026:
| Business Central licence | US (USD) | UK (GBP, excl. VAT) | What it covers |
|---|---|---|---|
| Essentials | $80.00 per user / month, paid yearly | £61.50 per user / month, paid yearly | Finance, sales and operations, with Microsoft Copilot included |
| Premium | $110.00 per user / month, paid yearly | £84.60 per user / month, paid yearly | Everything in Essentials plus service management and manufacturing |
| Team Members | $8.00 per user / month, paid yearly | £6.20 per user / month, paid yearly | Limited access: read data, approve workflows, create or update select information |
ERPNext has no licence fee at any user count. The software is published under the GNU General Public License v3.0 on GitHub. You can self-host it, or use Frappe’s managed hosting. Frappe Cloud’s pricing page, checked Nov 11, 2026, lists site plans from $5 a month on shared infrastructure and servers from $40 a month. Its site plans page lists AWS plans at $5, $10, $25, $38 and $50 a month, and its servers page lists, for example, an AWS server in London with 4 vCPUs, 16 GB of memory and 100 GB of disk at $360 a month. Frappe Cloud does not publish GBP prices, so GBP figures for it are indicative conversions.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3403 per £1 for 9 Nov 2026, the latest published figure when we checked on Nov 11, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
Licence cost by user count
The table shows Business Central licence cost for a year at list price, using Microsoft’s official USD and GBP prices. It assumes every user needs a full licence, which is the worst case. Many GP sites have light users who could be Team Members.
| Full users | Essentials, per year (USD / GBP) | Premium, per year (USD / GBP) | ERPNext licence |
|---|---|---|---|
| 20 | $19,200 / £14,760 | $26,400 / £20,304 | $0 / £0 |
| 50 | $48,000 / £36,900 | $66,000 / £50,760 | $0 / £0 |
| 100 | $96,000 / £73,800 | $132,000 / £101,520 | $0 / £0 |
| 200 | $192,000 / £147,600 | $264,000 / £203,040 | $0 / £0 |
This is the honest version of the “no licence” argument. ERPNext removes a cost that grows with headcount, but it does not remove cost. You still pay for hosting (from a few hundred dollars a year on a small Frappe Cloud plan up to dedicated servers), implementation, support and upgrades. Business Central buyers pay for implementation and support too, so those lines appear on both sides. The licence line is the one that differs, and it grows every time you add a user.
Read this before using the table in a business case
Microsoft partners may quote different terms, and Business Central has other licence types and add-ons not shown here. Get a written quote for your exact user mix. On the ERPNext side, ask for a hosting and support quote sized on your own transaction volumes, not on user count alone.
The migration path to each option
To Business Central: Microsoft’s own tool
This is Business Central’s biggest advantage, and we say so plainly. Microsoft provides a cloud migration tool from GP on-premises to Business Central online. According to Microsoft’s overview, it migrates system and company setup (payment terms, shipping methods, sites), master data for accounts, customers, vendors and items, transactional data, customer, vendor and item classes, Vendor 1099 data, and historical data. It moves data table by table through Azure Data Factory and tracks success and failure per table. Microsoft recommends a test run on a sandbox first. It also warns: do not set up cloud migration against a production environment already in use, because the migration can overwrite data.
The configuration guide shows how GP’s account structure maps: you choose two GP segments as Business Central’s global dimensions, and the remaining segments become shortcut dimensions. You set the oldest GL year to migrate, and choose master-data-only modules, inactive records and which historical transactions to bring as a “GP Detail Snapshot”.
To ERPNext: a data migration you design
There is no Microsoft-built tool for ERPNext, and we did not find a Frappe-published GP migrator. A GP-to-ERPNext move is a designed data migration. You extract from the GP SQL Server database or GP SmartLists, transform the data, and load it with ERPNext’s own tools. The ERPNext Data Import documentation imports CSV or Excel templates and can insert new records or update existing ones. ERPNext’s accounting migration documentation covers importing a Chart of Accounts, opening balances posted against a Temporary Opening account (which should be zero once all openings are loaded), and an Opening Invoice Creation Tool for open receivables and payables.
In practice this means more design work up front than the Microsoft path. In return, you get a clean start: you choose what history to carry, rather than replicating GP’s structure.
Mapping GP to ERPNext
| Dynamics GP | ERPNext | Notes |
|---|---|---|
| Companies | Companies (multi-company in one site) | Decide whether inter-company accounting stays inside ERPNext |
| Account segments (natural account plus department, location and so on) | Account, Cost Center and Accounting Dimensions | Map the natural segment to the Chart of Accounts and other segments to cost centres or dimensions |
| Fiscal periods | Fiscal Year and Accounting Period | Align the cutover with the start of a fiscal year where possible |
| Customers and customer classes | Customer and Customer Group | Carry posting defaults in the group or customer account settings |
| Vendors and vendor classes | Supplier and Supplier Group | Check 1099 reporting needs for US vendors in the pilot |
| Items, item classes and sites | Item, Item Group and Warehouse | Serial and lot tracking map to serial and batch numbers |
| Open receivables and payables | Opening invoices via the Opening Invoice Creation Tool | Load remaining amounts, not original amounts |
| Inventory quantities and costs | Opening stock via Stock Reconciliation | Agree the valuation method before loading |
| Checkbooks | Bank Accounts | Reconcile in GP before cutover |
| Sales Order Processing and Purchase Order Processing | Sales Orders, Sales Invoices, Purchase Orders, Purchase Receipts | Migrate open documents; archive closed history |
| Fixed Asset Management | Assets with depreciation schedules | Load net book value and remaining life |
| Payroll | Keep or choose a dedicated payroll provider | Validate payroll and payroll tax for your jurisdiction separately; do not assume parity |
| Management Reporter and SmartList reports | ERPNext financial reports, report builder, Frappe Insights | Rebuild the reports finance actually uses; retire the rest |
| ISV add-ons | ERPNext standard features, marketplace apps or custom apps | List every add-on and its owner early; this is often the longest tail |
History is a decision, not a default. Our usual recommendation: migrate masters, open documents and opening balances, plus monthly GL balances for two or three prior years for comparison reporting. Keep a read-only copy of the GP database (or a reporting database built from it) for anything older. Auditors and tax authorities need access to history, not necessarily inside the new ERP.
Where ERPNext fits GP sites well, and where it does not
| Area | ERPNext fit for a 20 to 200 user GP site | What to test in the pilot |
|---|---|---|
| Core financials (GL, AP, AR, bank, multi-company, multi-currency) | Strong | Your segment model as cost centres and dimensions; period close; consolidation |
| Distribution (stock, purchasing, sales, warehouses, batches, serials) | Strong; included without extra licences | Pricing rules, units of measure, landed cost |
| Light to mid manufacturing (BOMs, work orders, job cards) | Good; included in the same system | Routing complexity, subcontracting, costing method |
| Projects and timesheets | Good | Billing rules and project costing |
| US and UK payroll | Do not assume; plan a dedicated payroll provider | Payroll integration to the GL |
| GP ISV add-on equivalents | Varies by add-on | Each add-on’s function in ERPNext standard or an app |
| Microsoft 365 and Power Platform integration | Via APIs and connectors, not native | Which integrations finance relies on daily |
Business Central or ERPNext: a decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| You want the lowest-risk, vendor-supported path from GP and plan to keep your GP partner | Business Central | Microsoft’s GP migration tool and partner ecosystem |
| Your users live in Microsoft 365 and Power BI and you want native integration | Business Central | Same vendor stack |
| You have 50+ users and expect headcount growth | ERPNext (price both) | Licence cost grows per user on Business Central; ERPNext has none |
| You need inventory, purchasing and light manufacturing for everyone, not just finance | ERPNext (price both) | Included in one system; Business Central manufacturing needs Premium |
| You want to self-host or keep tight control of data location | ERPNext | Open source; self-host or choose a Frappe Cloud region |
| You depend on several GP ISV add-ons that have Business Central versions | Business Central | Same ISVs often support both |
| Your team has no appetite for a designed data migration | Business Central | The Microsoft tool does much of the mechanical work |
A GP-to-ERPNext plan for a January cutover
| Phase | Work | Done when |
|---|---|---|
| Discovery (6–8 weeks) | Inventory companies, segments, modules, add-ons, reports and integrations; agree history policy | Signed scope and a mapping workbook |
| Pilot (8–12 weeks) | Load one company’s masters and a recent year of balances; run a month-end close in ERPNext | Finance closes a pilot month and agrees the numbers |
| Build (3–6 months) | Configure, build reports and integrations, decide payroll, train key users | User acceptance testing signed off |
| Dress rehearsals (2 cycles) | Full trial migrations from a GP copy, with reconciliation | Balances match GP to the cent |
| Cutover (fiscal year start) | Close the year in GP, load openings, go live | First month closed in ERPNext |
| Hypercare and archive | Support, decommission GP to read-only, archive access | GP retired before Microsoft support ends |
These durations are our planning ranges for a mid-sized GP site, not a promise; multi-company and heavy add-on use push them up. Working backwards from a January 2029 go-live, discovery should start no later than early 2028. Starting in 2027 leaves room for a second fiscal-year window if the first slips.
Best for, and wrong choice when
ERPNext is the right GP replacement when
You have 20 to 200 users, run distribution or light manufacturing alongside finance, want to stop paying per user, and will fund a properly designed migration and implementation.
ERPNext is the wrong choice when
You need the lowest-risk path with Microsoft’s own migration tool, you depend on GP add-ons with direct Business Central equivalents, or the business cannot spare finance staff for a pilot and two dress rehearsals.
Business Central is the wrong choice when
Per-user licences will be your largest recurring ERP cost as you grow, or you need full ERP functionality for many users who would each need a Premium licence.
Frequently asked questions
When does Dynamics GP support end?
Microsoft’s GP lifecycle page says support for product enhancements, regulatory (tax) updates and technical support ends on December 31, 2029, and security updates, if needed, are available until April 30, 2031 (checked Nov 11, 2026).
Can I keep running Dynamics GP after 2029?
The software does not stop working, but after December 31, 2029 there are no tax updates or technical support from Microsoft, and security patches end on April 30, 2031. Running an unsupported finance system is a risk you would have to accept explicitly.
How much does Business Central cost per user?
Microsoft’s pricing pages list Essentials at $80 / £61.50, Premium at $110 / £84.60 and Team Members at $8 / £6.20 per user per month, paid yearly (UK prices exclude VAT; checked Nov 11, 2026).
Is ERPNext really free?
ERPNext is open source under GPL-3.0 with no licence fee. You still pay for hosting (Frappe Cloud lists site plans from $5 a month and servers from $40 a month), implementation and support.
Is there a GP to ERPNext migration tool?
We did not find a Microsoft or Frappe-published one. A GP-to-ERPNext move is a designed migration using ERPNext’s Data Import tool, Chart of Accounts import and opening balance tools. Microsoft’s own migration tool targets Business Central online.
How do GP account segments map to ERPNext?
Map the natural account segment to the ERPNext Chart of Accounts, and other segments such as department or location to Cost Centers or Accounting Dimensions.
When should a GP site go live on its replacement?
For a calendar-year company, at the start of a fiscal year and no later than January 2029, so the 2029 year runs on the new system while Microsoft still supports GP as a fallback.