Dynamics GP End of Life: Keep Your B2B Storefront Running

The memo usually lands on the controller's desk first. Microsoft has published the Dynamics GP end of life dates for the ERP many still call Great Plains. An ERP shortlist meeting goes on the calendar, and every agenda item is about the general ledger, payroll, and the chart of accounts.

Nobody puts the storefront on the agenda. But if you sell through Shopify B2B on GP, the store is wired into the system being retired. Buyer logins map to GP customer numbers. Contract prices come from GP price levels. Stock comes from GP sites, and every web order lands as a GP sales order. Move the ERP without a plan for those wires, and the first person to notice is a buyer who sees the wrong price.

Quick answer: Microsoft ends Dynamics GP product enhancements, tax and regulatory updates, and technical support on December 31, 2029, and stops security patches on April 30, 2031. Its recommended replacement is Dynamics 365 Business Central. For a distributor or manufacturer selling through Shopify B2B, this is a storefront event as well as an ERP event, because the integration, pricing, and customer mapping all point at GP. The store survives the move when Shopify owns the buyer experience (companies, locations, catalogs, order history) and GP sits behind a thin, replaceable connector. Then switching ERPs means re-pointing the connector, not rebuilding the store.

Dynamics GP end of life: the dates, from Microsoft's own pages

Plenty of pages still quote September 30, 2029. That date is stale: Microsoft moved the end of support to December 31, 2029 in an update to its original announcement, and its Dynamics GP lifecycle page carries the same dates. For the current release, GP 18.x, which runs under the Modern Lifecycle Policy, the timeline is:

• April 1, 2025: no new customers for GP perpetual licenses.
• April 1, 2026: no new customers for GP subscription licenses. Both sales dates come from Microsoft's end-of-life announcement on the Dynamics Community.
• December 31, 2029: end of product enhancements, regulatory (tax) updates, and technical support.
• April 30, 2031: last date for security updates and patches, if needed.

Older releases run on the Fixed Lifecycle Policy. Extended support for GP 2016 and 2016 R2 ended on July 14, 2026, and extended support for GP 2018 and 2018 R2 ends on January 11, 2028. Microsoft notes that installing any compatible tax release or hotfix on GP 2018 moves you to 18.5 or later, and onto the Modern dates.

Circle December 31, 2029 if you sell online. GP won't stop on January 1, 2030. What stops is the stream of regulatory updates and the Microsoft support line you would call about a failed posting.

Is Microsoft Dynamics GP being discontinued?

Yes. Microsoft Dynamics GP end of life is a scheduled wind-down, not a sudden shutdown. New customer sales have stopped, support and tax updates end December 31, 2029, and security patches end April 30, 2031. Existing customers keep running GP, with support continuing until the end of 2029.

With no new customers coming in, the GP installed base only shrinks from here. That hits the ecommerce integration harder than the general ledger, because it is the piece most likely to need a developer who knows both GP and Shopify on a busy Monday.

What is replacing Dynamics GP?

Microsoft's answer is Dynamics 365 Business Central. The GP lifecycle page says Microsoft is encouraging customers to transition to it, and Microsoft Learn publishes tools for moving GP data into Business Central online. Plan the storefront around Business Central unless your shortlist says otherwise.

That choice has a direct storefront consequence. Business Central online ships with a first-party Shopify connector, but Microsoft's own FAQ states that the connector is available only for Business Central online, not for on-premises deployments. If your ERP team is leaning toward on-premises because GP was, the ecommerce team needs to hear that now. The Business Central to Shopify integration page covers what the native connector handles and where Microsoft documents its limits.

Why Dynamics GP end of life is a storefront event

The pages currently ranking for this topic treat it as an accounting migration. For a B2B seller it is also a commerce migration. A working Dynamics GP to Shopify integration carries GP's shape into the store in at least five places:

• Customer identity. Shopify companies and buyer logins are matched to GP customer numbers.
• Pricing. Account prices come from GP standard pricing (price levels) or extended pricing (price sheets and price books), and the two behave differently.
• Inventory. Stock is read per GP site, so each Shopify location is tied to a GP site code.
• Units of measure. Each, case, and pallet logic follows GP's unit of measure schedules.
• Order write-back. Web orders become GP sales orders in Sales Order Processing, usually through eConnect or GP Web Services, with the document types your warehouse expects.

None of those survive an ERP swap untouched. What matters is where they live. In the connector, they get replaced. In the storefront, they get rebuilt.

What a GP to Business Central migration carries, and what it leaves to you

Microsoft's article on migrating Dynamics GP data to Business Central online is specific about what its cloud migration tools move. Customers come across (all, or active only), with every address set up as a shipping address. Open receivables arrive at the amount still owed. Items bring their location, quantity on hand, and serial or lot tracking. Open purchase orders can come too.

Three gaps in that list land on the storefront team.

Unit of measure schedules have no direct equivalent. Business Central stores units of measure per item, not as GP-style schedules. Your pack-size rules have to be re-expressed before the storefront can point at them.

Sales history becomes a snapshot. Historical Sales Order Processing transactions can move into GP Historical Snapshot extension tables. They are readable and reportable, but they are not live Business Central sales documents. If reorder history in your store reads GP documents, plan for that.

Price levels are not on the list. The article covers fiscal periods, accounts, customers, vendors, items, checkbooks, and history. It never mentions GP price levels or price sheets. For a distributor with contract pricing, rebuilding pricing in Business Central is its own project, and the store's prices are only as right as that rebuild.

Check one more pricing detail before anyone promises the native connector will cover you. Microsoft's guide to syncing prices from Business Central to Shopify says the connector calculates each price from a temporary sales quote at a quantity of 1. It also says you can't export different prices or discounts based on quantity. If a contractor pays less per unit at 100 than at 10, that quantity break has to be handled somewhere else.

How to plan a Shopify B2B storefront that survives the ERP move

When the ERP changes, the store should keep its buyers, catalog, URLs, and order history, and only the connector underneath should change. Six decisions get you there.

1. Let Shopify own the buyer structure. Shopify B2B models a buyer as a company with one or more company locations, and each location can have its own tax ID, addresses, pricing, payment terms, and contacts. Make that structure the permanent record of who your buyers are. Store the GP customer number as a reference on the company, so the ERP move is a remap of references, not a rebuild of every account. 2. Treat price as an answer the ERP gives, not a table the store copies. Confirm whether you run GP standard or extended pricing, write down every rule that produces a contract price, and decide how Business Central will express those rules before cutover. 3. Name Shopify locations for what they are, not for GP site codes. A branch in Columbus is a branch in Columbus in both ERPs. Map it to its GP site inside the connector, and re-map it later. Push stock that is truly available, not raw on-hand, for the reasons covered in available to promise vs on hand. 4. Keep the order history buyers see in Shopify. Make sure reorder lists and saved carts read from Shopify, so they don't break when GP history moves into snapshot tables. 5. Keep the connector thin and isolated. GP stays the system of record, never the system of experience. No storefront logic goes into GP, and no GP logic leaks into the theme. Interfaces differ a lot between ERPs, as the breakdown of what each ERP actually exposes to an ecommerce integration shows. 6. Write the cutover plan before you need it. Decide how orders placed during the cutover window will queue, which system confirms prices that weekend, and how held orders replay into Business Central without duplicates. An order that retries into a second sales order is worse than one that waited.

Integrate GP now, or wait for Business Central?

If you run GP 18.x today, in October 2026, you have just over three years of normal support and about four and a half years of security patches left. That is a long time to leave a B2B channel unbuilt, or a working one frozen.

Wait if a Business Central project is already funded and scheduled, and build the store once against the ERP you will actually run. Integrate GP now if the ERP decision is still open: a thin connector gets the channel live while the harder project runs on its own timeline. The riskiest path is doing both at once, with an ERP migration and a store launch sharing one cutover weekend and one tired team.

NAV shops face the same fork on a shorter clock, as the Dynamics NAV integration page explains, and the Microsoft Dynamics integration overview shows how each Dynamics product connects to Shopify. If Finance and Operations is on your shortlist, the Shopify and Dynamics 365 guide for manufacturers compares it with Business Central.

> The storefront test: if you replaced your ERP tomorrow, what would you rebuild? Buyer accounts, catalogs, prices, locations, order history, or only the connector? Everything on that list except the connector is a design decision you can still change.

Plan the storefront before you sign the ERP contract

ERP selection takes months, and finance gets most of them. Spend some of that time on three storefront questions: which pricing model you really run, which records Shopify should own for good, and how orders behave during cutover.

Uncap Connect is designed around this split. It keeps pricing, inventory, customer data, and orders current in both directions, with the ERP as the system of record, and it is ERP-agnostic by design. The Uncap team confirms fit for a specific ERP and the sync depth you need directly, so have that conversation about both the GP you run today and the Business Central you are moving to.

If you want the whole picture mapped before anyone writes code, Uncap Blueprint is a fixed-price, four-week plan. It covers ERP integration mapping, data migration taxonomy, total cost of ownership, and a replatforming risk register, and you keep it whether or not you build with us. Uncap has been a Shopify Platinum Partner since 2013, with 380+ storefronts launched on Shopify. Talk to Our Experts, and bring your GP version, your pricing model, and the date your ERP decision is due.