Vendor end-of-life
Third-Party Support as a Bridge to Your Future ERP
When a vendor announces the end of mainstream support for a product you still rely on, the immediate reaction is that you must move, and soon. From my work on dozens of what the industry calls legacy ERP systems, I have learned that the more useful reaction is the opposite. Slow down, and give yourself a deliberate window to plan a proper migration instead of a rushed one.
Third-party support exists because of that gap. It is a commercial arrangement where an independent provider takes over maintenance of a system after the original vendor stops, or where you choose it to escape a forced upgrade cycle. It is not a permanent home. It is a bridge, and it is only as good as the plan on the far side.
What third-party support actually is
Third-party support firms maintain software the vendor no longer fully supports, or support you want at a lower cost than the vendor's own extended maintenance. In practice the provider patches what it reasonably can, keeps the system running, handles defects it can reproduce, and issues legal and regulatory updates where it has the rights to do so.
These providers do not have the vendor's source code, so their fixes are typically applied at the binary level rather than by recompiling the product. For most business users that distinction is invisible. The system still opens on Monday morning and the month-end still closes. What matters is that the provider stands behind its work contractually and has the technical depth to honour it.
Why you would plan a bridge at all
Most organisations do not choose a bridge because they love their old ERP. They choose it because of the timing mismatch between a vendor deadline and their own capacity. A full legacy ERP migration takes, at a realistic pace, somewhere between 6 and 18 months from a standing start, and often longer once data quality and change management are honestly scoped. For more on the realistic shape of that schedule, see how long a full ERP replacement takes.
If your vendor support ends in eight months and your programme needs eighteen, you have three options. You overpay for vendor extended support, you run unsupported and accept the risk, or you buy a bridge. The bridge is the only one that preserves your freedom to plan rather than to react.
In one engagement a European distributor faced a support deadline that landed in the middle of their peak trading season. A two-year third-party support contract gave them the calendar space to move go-live to the quiet quarter, which saved far more than the support cost.
What it costs and what it covers
Cost is where third-party support is most attractive. As a rough rule, independent providers charge a fraction of what the vendor wants for extended support, often 30 to 50 per cent less on annual maintenance, and many include fixes and updates that a vendor would bill separately. Savings scale with the size of your estate, which is why larger enterprises look at this first. Rimini Street, one of the largest independent support providers, publishes figures in that same range.
What the contract covers varies more than you would expect, so read it closely. A good agreement includes defect fixes, legal and tax updates, security patching where possible, and a defined response-time commitment. Scrutinise what it excludes, especially anything about new functional features, which these providers will not develop, and any reliance on the vendor's codebase that the provider cannot actually touch.
The risks you need to name
Honesty matters here. Third-party support is a holding pattern, not a destination, and several risks come with it. Regulatory updates can be slower if the provider cannot rebuild from source. Security patching may be partial when the vendor holds the keys. And there is an integration risk if your third-party-supported ERP needs to keep talking to a modern cloud estate; the seams get older every year. This is worth weighing against the arguments in legacy ERP versus cloud ERP.
There is also the human risk. Key staff who know the old system retire or move on, and the knowledge walks out of the building. A bridge that lasts too long can quietly turn into a permanent stay, which is how organisations end up with a twenty-five-year-old ERP and no one left who understands it.
When a bridge genuinely makes sense
A third-party support bridge is the right tool when you have a real migration plan and a date, but the vendor's support clock is out of step with your delivery cycle. It also suits organisations that cannot absorb a forced upgrade during a strategic acquisition, a platform consolidation, or a period of leadership change.
What it is not for is a way to avoid making a decision. If you buy support with no plan to move, you have simply paid for the status quo with an extra middleman and a long-term debt that grows quietly. If that is your situation, read the cost of waiting another year on your legacy ERP before you sign.
The practitioners who use this tool well treat it as a defined phase. They set the exit date on day one, they keep the modernisation business case alive, and they use the freed capacity to do the slow, valuable work of cleaning master data before migration. The bridge buys time. The discipline decides what that time is worth.
Frequently asked questions
Is third-party support legal and safe?
Generally yes for support you are entitled to receive. Providers contract with you directly and many have operated for over a decade. The main legal nuance is that they must not copy the vendor's code or trademarks without permission, so their fixes are applied differently from the vendor's own.
What percentage of maintenance cost can third-party support save?
On the engagements I have seen, independent support typically costs 30 to 50 per cent less than the vendor's extended maintenance for comparable coverage. The real saving is often larger when you count fixes and updates the vendor would have billed separately.
Will third-party support delay my ERP migration?
Only if you let it. Used properly it buys time to plan a better migration, which tends to shorten the risky parts. If you sign without an exit plan, the bridge becomes permanent and effectively delays the decision indefinitely.
Which third-party ERP support providers exist?
Rimini Street and Spinnaker Support are the two most established independent providers for SAP and Oracle estates, among others. It is worth comparing two or three against each other and against the vendor's own extended support before deciding.
Sources and further reading
The argument in this article draws on public research. Where you want to go deeper, these are the sources cited in the text and further reading.
