Dynamics GP support ends December 31, 2029, and your GP EDI integration won't move with you. Here's how to rebuild EDI for Business Central without downtime.
Quick answer: Microsoft ends product updates, tax updates, and technical support for Dynamics GP on December 31, 2029, and security patches stop on April 30, 2031. Most GP customers are moving to Dynamics 365 Business Central. Your GP EDI integration won't migrate with your data, so EDI needs its own plan, ideally started before your ERP cutover date is locked.
If you run Dynamics GP and trade with retailers, distributors, or 3PLs, the ERP migration is only half the project. The other half is making sure purchase orders keep flowing in and ASNs and invoices keep flowing out the day you switch to Business Central.
That's where most GP-to-BC timelines slip. ERP partners scope the data migration, the chart of accounts, and the reports. EDI often lands on the plan late, after go-live dates are already promised to the business and to trading partners.
This guide covers the GP end-of-life dates that matter, why GP EDI doesn't carry over, your options for Business Central EDI, and a step-by-step plan to move without missing an order.
Dynamics GP End of Life: Key Dates
The date most teams quote is 2029, but several earlier milestones have already passed or are close.
Date | What Changes |
|---|---|
April 1, 2025 | New perpetual GP license sales ended |
April 1, 2026 | New GP subscription license sales ended |
July 14, 2026 | Extended support ended for GP 2016 and 2016 R2 |
January 11, 2028 | Extended support ends for GP 2018 and 2018 R2 |
December 31, 2029 | Product enhancements, tax updates, and technical support end for current GP (18.x) |
April 30, 2031 | Security updates and patches end |
Sources: Microsoft Dynamics GP lifecycle, Dynamics Communities interview with Microsoft's Mike Morton. Microsoft moved the 2029 date from September 30 to December 31.
A GP-to-Business Central migration typically takes 9 to 18 months from discovery to go-live, according to Microsoft partners. Working back from 2029, most companies need to start planning in the next 12 to 24 months, and partner capacity will tighten as the deadline gets closer.
Why Your GP EDI Integration Won't Migrate With You
Business Central isn't a new version of GP. It's a different product with a different data model, a different extension framework, and a different integration layer. Microsoft's cloud migration tool moves master data, open transactions, and history. GP customizations built on Dexterity have to be rebuilt as Business Central extensions, and integrations must be redeveloped against Business Central's APIs. EDI is one of those integrations.
Most GP EDI setups depend on at least one of these, and each needs to be rebuilt or replaced:
GP-specific connectors or add-ons built on GP's Dexterity or eConnect layers, which don't run in Business Central
Custom maps and SQL scripts that read from or write to GP tables directly
Flat-file imports and exports keyed to GP field names, document numbers, and batch logic
Trading partner configurations (ISA IDs, qualifiers, partner-specific rules) stored inside the old integration
When these break, the impact shows up with your customers first: POs that never create sales orders, ASNs that miss a retailer's window, and invoices that get rejected. For retail suppliers, each of those can mean chargebacks.
The upside: because EDI has to be rebuilt anyway, the migration is the cheapest moment you'll ever have to change how you do EDI.
Your Business Central EDI Options
Business Central doesn't include full EDI functionality out of the box, so every GP customer picks one of four paths.
Option | How It Works | Best For | Watch Out For |
|---|---|---|---|
Rebuild with your current EDI provider | Re-implement maps and connectors for BC with the same vendor | Teams with few partners and a vendor that already supports BC | You pay to rebuild, but keep the same model, pricing, and timelines |
BC extension from AppSource | Install an EDI app that runs inside Business Central | Teams with in-house BC developers | Maps and partner specs often stay your team's job to maintain |
Web EDI portal | Key or upload documents in a browser, no ERP connection | Very low volume, one or two partners | Manual re-entry doesn't scale and adds error risk |
API-first EDI platform | One API connection from BC to a network of pre-connected partners | Growing suppliers with multiple retail, distribution, or 3PL partners | Confirm which transactions and partners are already on the network |
The question to ask any vendor: when a trading partner changes its spec after go-live, who updates the map, and how long does it take?
How to Migrate EDI From GP to Business Central: 6 Steps
Inventory every trading partner and transaction. List each partner, the documents you exchange (850, 855, 856, 810, 860, 820, 997), your ISA IDs, and how each connects today (VAN, AS2, SFTP).
Pull current partner specs. Retailers update guidelines often. Build against the current version, not the one your GP maps were written for years ago.
Put EDI on the ERP project plan from day one. Give your BC partner and your EDI provider the same go-live date and a shared test window.
Map BC fields to each document. Confirm where BC stores what partners need: ship-to locations, item cross-references, carton and pallet data for ASNs.
Test with partners before cutover. Run test POs, ASNs, and invoices through BC and get partner sign-off before you switch production traffic.
Cut over and monitor. Switch one partner group at a time if you can, and watch acknowledgments (997s) and rejections closely for the first two weeks.
Tip: start steps 1 and 2 now, even before you pick a BC partner. They don't depend on the ERP and they take longer than most teams expect.
How Orderful Connects Business Central to Your Trading Partners
Orderful connects to Business Central, cloud or on-premise, through Microsoft's standard APIs. There's no custom AL code to maintain and no AppSource app to license.
Inbound POs become sales orders. EDI 850s create BC sales orders automatically, and 860 changes update them.
Shipments trigger ASNs. Posting a shipment in BC sends a validated 856.
Posted invoices go out as 810s. No separate billing step.
Every document is validated before it's sent. Outbound EDI is checked against each partner's requirements, so errors get caught before they become chargebacks.
Partner specs stay current. When a partner changes its requirements, Orderful updates automatically, with no manual rework.
One connection, a whole network. Partners already on the Orderful network go live in days, not months.
Caraway added Home Depot in 10 days and cut EDI costs by 30%. Liquid Death reduced partner setup time by 80%. See how Orderful works with Dynamics 365 Business Central.
Frequently Asked Questions
When does Dynamics GP support end?
Microsoft ends product enhancements, tax updates, and technical support for Dynamics GP on December 31, 2029. Security updates continue until April 30, 2031.
Can I still buy Dynamics GP?
No. New perpetual license sales ended April 1, 2025, and new subscription sales ended April 1, 2026. Existing customers can keep using GP.
Will my EDI work after I move from GP to Business Central?
Not without changes. GP EDI connectors, maps, and scripts are built for GP's data model and don't run in Business Central. Plan to rebuild or replace your EDI integration as part of the migration.
Does Business Central have built-in EDI?
Not full EDI. Business Central needs a third-party EDI solution, such as an AppSource extension, a Web EDI portal, or an API-first EDI platform.
How long does EDI migration to Business Central take?
It depends on your number of partners and documents. With Orderful, partners already on the network typically go live in days. Start partner inventory early so EDI doesn't delay your ERP go-live.
Should I migrate EDI before or after my ERP cutover?
Plan both together. Test EDI against Business Central before cutover so orders, ASNs, and invoices keep flowing on day one.
Moving Off GP? Start With Your EDI
Your ERP migration is the best chance you'll get to fix EDI for good. Talk to Orderful about connecting Business Central to your trading partners before your GP cutover date.
Sources
- 01Dynamics GP End of Life: Key Dates
- 02Why Your GP EDI Integration Won't Migrate With You
- 03Your Business Central EDI Options
- 04How to Migrate EDI From GP to Business Central: 6 Steps
- 05How Orderful Connects Business Central to Your Trading Partners
- 06Frequently Asked Questions
- 07Moving Off GP? Start With Your EDI
- 08Sources
