Picture the CFO of a $150 million distributor. The company has run its accounting and operations on the same ERP system since 2009. It works. The people who know it know it well, and over fifteen years it has been bent into the shape of the business with reports, custom fields, and a few integrations nobody fully remembers building. Then a letter arrives from the reseller: the vendor is ending support, and here is a proposal to move to the vendor’s new cloud product, with a start date this spring. The CFO did not plan an ERP project this year. The vendor planned it for her.
This is happening across the mid-market right now, and the risk is not the deadline itself. The risk is that the deadline makes the decision.
The Dates Are Real
Microsoft will end product support and updates for Dynamics GP, a longtime mainstay of mid-market accounting, on December 31, 2029, with security patches continuing until April 30, 2031. Microsoft moved the original end date from September 30, 2029 to the end of that year so that customers could finish a full payroll and tax year, and it is pointing GP customers toward Dynamics 365 Business Central, its cloud product for smaller and midsize businesses.
SAP set its dates for the classic SAP ERP, often called ECC, in 2020: mainstream maintenance for SAP Business Suite 7 ends at the close of 2027, followed by optional extended maintenance, at additional cost, through the end of 2030. SAP has since offered longer runways tied to moving into its private cloud, and in November 2026 it extended one of those options through 2035, but trade press reports that it is aimed at large, complex customers and requires the move to SAP’s cloud by the end of 2030.
Not every vendor is pushing. Oracle has committed Premier Support for its on-premises E-Business Suite 12.2 through at least 2037. That contrast is useful. A deadline is the vendor’s business decision about its own product roadmap. It is not an independent finding that your system no longer fits your business.
Count Backward From the Date
A deadline in 2029 or 2030 sounds distant. Work backward and it is not. A careful selection takes months. Implementations take longer than anyone budgets: user group research reported by trade press puts the average move to SAP S/4HANA at about a year and a half, with many projects running past two years, and smaller systems still take the better part of a year once data cleanup, testing, and training are counted. Most finance teams want to cut over at the start of a fiscal year, not in the middle of a close, and they want a year-end behind them on the new system before the old one loses support.
Add those together, and a GP customer that wants a calm transition should be making its decision in 2027, with the project running in 2028. An SAP ECC customer facing 2027 is already inside its window. Our view is that the useful deadline is the decision date, not the vendor’s end date, and for many firms the decision date is next year.
The Like-for-Like Trap
When a vendor sets the timeline, the path of least resistance is to move to that vendor’s next product and carry everything over. The reseller knows the old system and sells the new one. The finance team wants the same reports. The customizations get rebuilt because they existed before. Eighteen months later, the company has spent a significant sum to arrive where it started, on a different platform, with the same workarounds and the same data problems.
Our experience is that this is the most common outcome of a deadline-driven ERP project, and the most expensive one, because the cost is invisible. Nothing failed. The company simply bought fifteen more years of the old way of working at the price of a new system. An ERP choice tends to last ten to fifteen years, so the question is not only what runs on January 1, 2030, but what the business will need from its core system in 2040.
The other failure is louder. Revlon’s 2018 annual report disclosed that difficulties implementing a new SAP ERP system disrupted operations at its North Carolina manufacturing facility, hurt net sales, and caused a material weakness in its internal controls over financial reporting. Revlon was a large company with a large budget. Rushed, poorly governed ERP projects fail at every size.
Four Choices, Not One
A vendor deadline presents one option. In our view there are at least four, and the right one depends on the business, not the date.
The first is to stay longer. Paid extended maintenance, security-only support periods, and third-party support providers can all buy time, sometimes years, for a system that still does its job. That is a legitimate choice when the business is stable and the system is not holding it back, provided someone has weighed the security and compliance exposure and written it down.
The second is to move within the vendor’s family, such as from GP to Business Central or from ECC to S/4HANA. This is often the shortest path, and it can be the right one. It should be chosen against alternatives, not assumed.
The third is to replace the system with a different product after a real selection. Our list of mid-market ERP picks is a starting point, not an answer, and every product on it looks good in a demo.
The fourth, and the one most often skipped, is to simplify first. Retire the customizations that exist only because of how the business worked in 2009. Clean the customer, vendor, and item data. Redesign the handful of processes that cause most of the manual work. A company that does this before choosing a platform makes a better choice and runs a shorter project, whichever platform it picks.
Who Is Advising You
Most mid-market ERP decisions are guided by the people who sell or implement the software. Many of them are skilled and well intentioned, and they are also paid by the outcome. The reseller who supported your old system has a natural interest in moving you to its vendor’s new one. That is not a criticism; it is how the channel works, and we have described the same dynamic in managed IT, where your MSP often works for its program OEMs, not you.
What a mid-market firm usually lacks is someone at the table who is paid by the company, not the vendor, and who has run these projects from the buyer’s side. That is the role we described in Sometimes a Project Manager Is Not Enough: a project manager keeps the plan on schedule, but someone has to own the decisions the plan depends on.
Where the Knowledge Lives
Before any of these choices, find out what you actually have. Many mid-market companies run more than one ERP: an acquired subsidiary on a different system, a plant on an older version, a spreadsheet that does the job of a module nobody bought. Each one has its own clock.
Then find out who understands it. In a fifteen-year-old system, the logic behind the custom reports and integrations often lives in one or two people, sometimes a long-tenured employee and sometimes a consultant who has moved on. That knowledge has to be captured before the project begins, not discovered during testing. We wrote about the broader version of this risk in When Your Single Point of Failure Is a Developer.
What This Will Not Do
The opening scenario is a picture, not a client. The support dates come from Microsoft’s and SAP’s own announcements and can change, as GP’s already has once; the SAP 2035 option and the Oracle commitment are summarized from vendor statements and trade press. The project durations are averages from user group surveys and vary widely by scope. Our four choices, the like-for-like warning, and the advice to decide in 2027 are our judgment, drawn from running ERP projects from the buyer’s side. None of this tells you which system to run. What it supports is a sequence: know what you have, decide what the business needs, and then choose a path, before the vendor’s calendar chooses it for you.
Where to Start
Write down every system that does ERP work in your company, the vendor’s support date for each, and the one or two people who understand how it has been customized. Then put the decision date, not the end date, on next year’s calendar. If you would like an outside view of your options before a vendor proposal frames them, our independent assessment covers exactly this decision. If you would rather talk it through first, you can reach us through the contact form on our About page.
