Dynamics GP End of Support 2029 and Order Entry Plan

Nov 7, 2026

Convert a purchase order to Excel, CSV, or JSON

Upload a PDF, scan, or photo of a PO and get the line items as a spreadsheet in seconds.

PDF, JPG, PNG, BMP, HEIC, TIFF

Submit your purchase orders

Microsoft will end Dynamics GP support on December 31, 2029 for product enhancements, regulatory (tax) updates and technical support. Security updates and patches, if needed, stay available until April 30, 2031. Older versions end sooner, so the date that matters is the one for the version you run. Until you move, the daily cost is the same as today, and the biggest piece of it on the sales side is people retyping customer purchase orders.

This page lays out the dates as Microsoft states them, what they mean for a team that still runs Sales Order Processing, and how to decide what to automate now versus what to leave for the next system.

What Microsoft says about Dynamics GP support dates

Microsoft's own Dynamics GP lifecycle page gives the current picture. Support ends December 31, 2029. The earlier announced date was September 30, 2029, so the schedule has already moved once. After that, security updates and patches, if needed, are available until April 30, 2031.

Versions are treated differently. GP 18.x falls under the Modern Lifecycle Policy. The fixed lifecycle table lists GP 2018 and 2018 R2 with extended support ending January 11, 2028, and GP 2016 and 2016 R2 with extended support ending July 14, 2026. That last date has passed. If your company is still on a 2016 release, you are already outside extended support and the upgrade question is more urgent than the 2029 headline suggests.

Version or milestoneDate Microsoft states
GP 2016 and 2016 R2 extended support endsJuly 14, 2026
GP 2018 and 2018 R2 extended support endsJanuary 11, 2028
Dynamics GP support ends (enhancements, regulatory updates, technical support)December 31, 2029
Security updates and patches, if neededUntil April 30, 2031

Check your exact build against the lifecycle page before you plan. Dates for specific releases are the part that gets misremembered.

What this means for integrations and imports

Most GP shops load data through eConnect or through tools built on it, such as Integration Manager and SmartConnect. Microsoft's developer tools page calls Web Services the preferred tool for integrating data and says that in cases where an object is not available you can call the eConnect API directly. The same page notes that the eConnect procedures are encrypted, that Microsoft is not actively fixing certain issues in the eConnect shipping product because of the product life cycle, and that custom procedures might be lost during an upgrade.

The practical reading is that the import layer is in maintenance mode. It keeps working, but you should not build a large new custom integration on it. If you have a load that already works, keep it. If you are about to spend weeks building a PDF reader that writes eConnect documents, that effort will not carry over to your next system.

If your loads are failing today, the causes are usually environmental, not the data. The Integration Manager error reference covers the common ones.

The part of order entry that survives a migration

Whatever you run in 2031, customers will still email purchase orders as PDFs. A distributor receiving 60 customer POs a day has the same problem on Dynamics GP, Business Central or any other system: someone opens the attachment and keys each line. That step sits before the ERP, so it does not depend on which ERP you pick.

That is why the extraction step is worth separating from the load step. Reading the PDF into one row per line item, with the customer PO number repeated on every row and the buyer's item number kept next to the description, produces a file that any system can import. On GP you map it to the eConnect sales document nodes. Microsoft's archived eConnect reference lists six required elements on the sales header (SOPTYPE, DOCID, SOPNUMBE, DOCDATE, CUSTNMBR and BACHNUMB) and six on the line (SOPTYPE, SOPNUMBE, CUSTNMBR, DOCDATE, ITEMNMBR and QUANTITY). The full mapping is on the Dynamics GP sales order import page. After a move, the same file maps to the new system's import instead, for example Business Central sales order import or Dynamics 365 sales order import.

A sensible order of work before 2029

  1. Confirm your version and its dates. Use the lifecycle table above. A 2016 release is already past extended support.
  2. List the manual steps around GP. Sales order keying, vendor invoice entry and purchase order entry are the usual three. Time them for a week. The one that consumes the most hours is where automation pays back first.
  3. Automate document reading, not the ERP. Extract the rows from PDFs and load them with the tool you already have. The purchasing side is described in purchase order to Dynamics GP.
  4. Pick the next system on its own merits. Do not let a half-built GP integration decide it. Shortlist, price and demo.
  5. Plan the cutover file early. Open orders, open purchase orders and item cross-references all need to move. Clean cross-reference sheets of customer item numbers to your item numbers carry over to any system.

Teams making the case for a migration budget to leadership often need a short deck built from the numbers above. A tool that turns a report or PDF into a presentation saves an evening there.

How much does manual order entry cost while you wait

You can estimate it without anyone's benchmark. Count the customer POs per day, the average number of lines, and the minutes a person spends per order. Multiply by the loaded hourly cost of the person doing it. If three people each spend two hours a day on keying, that is six hours a day, and the number is yours, not a statistic. PurchaseOrders plans start at $49 a month, and a bulk upload takes up to 50 files at a time, so the comparison is usually quick.

Frequently asked questions

When does Dynamics GP support end?

Microsoft states that Dynamics GP support ends on December 31, 2029, covering product enhancements, regulatory (tax) updates and technical support. The previously announced date was September 30, 2029. Security updates and patches, if needed, are available until April 30, 2031.

Should I stop investing in Dynamics GP integrations?

Keep the ones that work and avoid large new custom builds on the eConnect layer. Microsoft says it is not actively fixing some eConnect issues because of the product life cycle. Put new effort into steps that move with you, such as turning customer PDFs into clean rows.

Can I still import sales orders into Dynamics GP after 2029?

Existing tools may keep running, but without technical support or enhancements. Regulatory updates stop at the support end date, which matters for tax. Plan the cutover before then rather than after.

Does PurchaseOrders connect to Dynamics GP?

No. It reads customer and vendor purchase order documents and returns Excel, CSV or JSON. You load the rows with eConnect, SmartConnect, Integration Manager or a script. Because the output is plain files, it also works with whatever system replaces GP.

Upload a purchase order PDF and see the rows it returns before you decide anything else.

Stop retyping purchase orders

Upload a PDF, scan, or photo of any PO and get clean Excel, CSV, or JSON line items in seconds.

Try it free

25 pages free. No credit card required.