Guide · checked 23 October 2026
Dynamics GP end of life: the dates, what changes, and how finance teams move to Business Central
Microsoft ends support for Microsoft Dynamics GP on 31 December 2029 and stops security updates on 30 April 2031. New customers have not been able to license Dynamics GP subscriptions since 1 April 2026. The product keeps running after those dates; what stops is tax updates, fixes and help. This page sets out the dates as Microsoft has published them, what they mean for a finance team, and which GP habits need a plan when you move to Microsoft Dynamics 365 Business Central.
The dates Microsoft has published
| Date | What happens |
|---|---|
| 1 April 2026passed | Last day for new customers to license Dynamics GP subscriptions. |
| 31 December 2029 | End of support: product enhancements, regulatory (tax) updates and technical support stop. Microsoft moved this from 30 September 2029. |
| 30 April 2031 | Last security updates and patches. Same day: service plan coverage ends, subscription licenses can no longer be renewed, perpetual users can no longer be added, and SPLA use is expected to end. |
Dynamics GP 18.x is governed by Microsoft's Modern Lifecycle Policy. Microsoft's original end-of-support date was 30 September 2029; the 31 December 2029 date is the one on Microsoft Learn as of 23 October 2026. Sources are listed at the end of this page; check them before you plan around a date.
What each date means in practice
Now until 31 December 2029
Nothing changes in the software. You still get year-end tax updates (W-2, 1099, payroll tables for US companies), hotfixes and Microsoft support through your partner. This is the planning window: every finance team on Dynamics GP should know by the end of 2027 which product it is moving to, so the move happens in a quiet quarter rather than against a deadline.
1 January 2030 to 30 April 2031
No more tax updates and no more fixes. For a US company that runs payroll or files 1099s from Dynamics GP, the 2029 year-end is the last one the product will do unaided. Security patches still arrive if Microsoft decides one is needed. Partners can still help, but with no escalation path to Microsoft.
After 30 April 2031
No security patches, service plan coverage ends, subscription licenses cannot be renewed, and perpetual users cannot be added to existing systems. The database and the application still run; the risk is now entirely yours: an unpatched application that holds the general ledger, on an operating system and SQL Server version that will have their own end dates.
The options, plainly
- Move to Microsoft Dynamics 365 Business Central. Microsoft's recommended path, with its own migration tooling and promotions that change over time; ask your partner what applies now. Most Dynamics GP partners resell it, which keeps your existing relationship.
- Move to another ERP. Several mid-market products take Dynamics GP customers. The GP-specific habits below still need a plan; they just get solved differently.
- Stay past 2029. Workable for a company with no payroll in GP, simple tax filing and a disciplined IT team, for a year or two. The cost is a growing compliance and security exposure that auditors will ask about.
This page covers the Business Central route, because that is the product InXtend builds for. InXtend does not perform migrations and does not sell Business Central; your partner does both.
Dynamics GP habits that need a plan in Business Central
Most of Dynamics GP maps cleanly: chart of accounts, customers, vendors, items, open documents and history all have a home, and the standard migration tooling carries them over. The friction is in the routines a finance team runs every week without thinking about them. Each row below gives the GP routine, what standard Business Central does today, and the InXtend app being built for the gap. The apps are in development; details may change before release.
| In Dynamics GP you are used to | Standard Business Central | InXtend app |
|---|---|---|
| Batches with an edit list and batch approval | Journal batches exist, with a test report and an optional batch approval workflow. Documents are not grouped into named batches: they post one at a time or through Post Batch, with no edit list across them. | Document Batches |
| Reversing transactions and Back Out and Correct | Reverse Transaction on posted G/L registers; no automatic reversing accrual on a future date without a recurring journal. | Auto-Reverse Journals |
| Fiscal periods closed by series (Financial, Sales, Purchasing…) | One Allow Posting From/To range per company plus one per user. No lock per module. | Module Period Lock |
| NSF check processing in Receivables Management | Unapply the payment, then reverse it from the customer ledger; the NSF fee is a separate entry. | NSF Payment Reversal |
| National accounts (parent and child customers) | Bill-to Customer on the child account covers invoicing; there is no roll-up of balance, credit limit or statements. | National Accounts |
| Sales process holds and customer hold | Customer Blocked (Ship, Invoice, All) and the credit-limit warning. No hold reason, release log or per-order hold. | Order and Credit Holds |
| Receivables small-balance write-off routine | Write-offs are manual journal lines or the Payment Tolerance setup, which applies at payment time only. | Small Balance Write-Off |
| Credit card payment of vendor invoices | Pay the vendor from a bank account that represents the card, then settle the card statement. Workable, but two steps and no card reference on the invoice. | Credit Card Vendor Payments |
| Check remittance overflow and electronic signature add-ons | The standard check reports handle a long remittance by printing extra voided checks for the overflow lines, which uses check stock and confuses vendors. | Check Remittance |
| Default purchases account per vendor | Vendor Posting Group sets the payables account; the expense account comes from the G/L account on each line or from an item. No per-vendor default expense account. | Vendor Default Coding |
The ten apps together are the Transition Pack. Each installs on its own from AppSource (planned), so a company can take the two or three it needs.
A planning sequence that works
- Inventory the routines, not the screens. Ask each person in finance what they do on the first and last three working days of the month. The GP features above come out of that list, not out of a module map.
- Decide what history moves. Open items and balances always do; years of detail usually stay in a read-only GP company or a reporting database. This decision drives the migration cost more than anything else.
- Pick the cut-over period. A fiscal year start is cleanest; a quarter start is fine. Avoid the two months before a year-end tax run.
- Run the first month twice. Post the same month in GP and in the Business Central sandbox, and reconcile the trial balance. The differences are your training plan.
- Install the gap apps before go-live, not after. A controller who loses batch approval on day one does not trust the new system on day two.
Questions finance teams ask
- When does Dynamics GP end of life take effect?
- Microsoft ends Dynamics GP support (product enhancements, tax updates and technical support) on 31 December 2029 and stops security updates on 30 April 2031. New customers could no longer license Dynamics GP subscriptions after 1 April 2026.
- Can we keep running Dynamics GP after 2029?
- Yes. The software keeps working, and security patches continue until 30 April 2031. After that there are no patches, service plans end and you can't add perpetual users. Payroll and 1099 updates stop at the end of 2029, which is the practical deadline for most US finance teams.
- Is Business Central the only option?
- No. Microsoft recommends Microsoft Dynamics 365 Business Central and offers migration tooling for it, and most Dynamics GP partners sell it, but other ERP products also take GP customers. This page covers the Business Central route because that is what InXtend builds for.
- Does InXtend migrate Dynamics GP data?
- No. InXtend builds apps for Business Central. Migration is done by your Business Central partner with Microsoft's cloud migration tooling. The Transition Pack apps are installed afterwards, into the new Business Central environment.
- Which Dynamics GP features have no direct equivalent in Business Central?
- The ones finance teams notice first: batches with an edit list, reversing transactions, period closing by series, NSF processing, national accounts, sales holds, small-balance write-offs, credit-card vendor payments, long check remittances and per-vendor default expense accounts. The table on this page shows what standard Business Central does for each and where an app fills the gap.
Sources
- Microsoft Learn: Dynamics GP documentation home (lifecycle statement)
- Microsoft Learn: Lifecycle policies for Dynamics GP
- Microsoft Dynamics 365 blog, 5 June 2025: Explore migration options for Microsoft Dynamics GP and Microsoft Dynamics SL customers
Microsoft Dynamics GP, Microsoft Dynamics 365 Business Central and Dynamics 365 are Microsoft products. InXtend LLC is an independent software publisher and is not affiliated with, sponsored or endorsed by Microsoft. Dates on this page were checked against the sources above on 23 October 2026; Microsoft can change them.
Get the Transition Pack when it launches
We'll email you when the first apps are on AppSource and invite you to the early-access trial. No newsletter.