ERP Support Services: In-House vs Vendor vs Third-Party AMS

ERP Support Services in 2026

ERP support services fall into four models: an in-house team, the vendor's own maintenance contract, a partner or consultancy providing application management services (AMS), or an independent third-party support provider. Many organisations end up running a blend — internal staff for day-to-day questions, plus an external contract for technical depth. The right mix depends on how stable your system is, how heavily you have customised it, and whether you plan to upgrade or stay put.

Support is the part of ERP ownership that gets decided last and costs the longest. Implementation ends; support runs for the next decade. Yet many organisations inherit a support model by default — they keep paying the vendor's annual maintenance because it arrives on the renewal invoice — rather than choosing one deliberately.

This guide explains what each model covers, what it typically costs, and how to work out which one fits your situation.

---

What Are ERP Support Services?

ERP support services are the ongoing activities that keep a live ERP system running after go-live: fixing defects, applying patches and security updates, delivering regulatory and tax changes, answering user questions, and making small enhancements. They are distinct from implementation, which delivers the system, and from upgrades, which move it to a new version.

In practice, "support" covers a wider span than a helpdesk. A mature support function handles four different kinds of work, and the distinction matters because different providers are good at different ones:

• Break-fix — something is broken and needs diagnosing. Errors, failed integrations, jobs that stopped running.
• Maintenance — patches, security fixes, and the statutory updates that keep payroll and tax compliant.
• User support — "how do I raise a credit note?" Training gaps show up here, which is why ERP training and support budgets are related.
• Small enhancements — new reports, tweaked workflows, an extra field. Often the largest hidden bucket, and the one most likely to be under-resourced.

A support contract that only covers the first two will leave the other two on your internal team by default.

The Four ERP Support Models Compared

Each model trades cost against control and coverage. Nobody is objectively best — they suit different systems at different stages of life.

The most common source of confusion is assuming vendor maintenance and AMS are alternatives. They usually are not. Vendor maintenance keeps the software supported; AMS supports your implementation of it — the customisations, the integrations, the reports your team actually uses. Many organisations need both, which is why support costs are routinely underestimated.

What ERP Support Costs

Support pricing follows a few consistent patterns, though every contract is negotiated.

Two things reliably distort a support budget. The first is enhancements — the steady trickle of "can we just add…" requests that no one costed. The second is customisation: every custom object is a recurring liability that has to be retested at each patch or upgrade, so a heavily customised system costs materially more to support than a vanilla one, regardless of who supports it.

For a fuller picture of where support sits in lifetime cost, see the ERP TCO calculator and the ERP implementation cost breakdown.

When Third-Party Support Makes Sense — and When It Doesn't

Third-party support is the most misunderstood model, so it is worth being precise about the trade.

Independent providers such as Rimini Street, Spinnaker Support, and Support Revolution will maintain your existing ERP version — including versions the vendor has stopped supporting — typically at around half the vendor's maintenance fee. They supply break-fix, security, and regulatory updates, and they will support customisations that vendor contracts generally exclude.

What you give up is the upgrade path. Third-party support provides no new releases, no vendor-issued patches, and no access to the vendor's newest functionality.

The cost of going back has historically been a real deterrent: vendors charged back-maintenance for the lapsed period, plus a fee to reinstate. That is now changing, at least for SAP. On 9 July 2026, following discussions with the European Commission (case AT.40823), SAP announced it would not charge administrative fees for customers returning to maintenance, and would limit back-maintenance to the lesser of six months or 50% of the fees for the time off — with a defined set of older products triggering no back-maintenance at all. SAP has said this applies to current and future customers worldwide across its on-premise products. Other vendors' reinstatement terms differ and can be substantially more expensive, so check your own contract rather than assuming the SAP position is the market norm.

That makes the decision largely a question of intent:

• It fits when the system is stable and fully deployed, you have no near-term plans for new functionality, and you want to reduce run costs — often while funding a migration elsewhere.
• It does not fit when you are mid-programme, expect to adopt new modules, or are on a version you intend to upgrade within a year or two.

The model tends to surface around vendor end-of-life deadlines. SAP ECC 6.0 on enhancement packages 6–8 reaches the end of mainstream maintenance on 31 December 2027, with optional extended maintenance to the end of 2030 at a surcharge — which is why ECC customers weigh third-party support against migrating to S/4HANA. If you are on EhP 0–5, note that your mainstream maintenance already ended on 31 December 2025 and no extended maintenance is offered, so the decision is live now rather than in 2027. Long-lived platforms such as Microsoft Dynamics GP raise the same question. Third-party support is a bridge with a defined end, not a destination; if you choose it, decide in advance what it is a bridge to. Our guide on whether to upgrade or replace your ERP works through that decision.

How to Choose an ERP Support Model

Work through these steps in order — they narrow the options faster than collecting quotes.

1. Establish where you are in the version lifecycle. Find your version's end-of-support date before anything else. A system two years from a hard deadline has a different answer to one on the current release. This single fact usually narrows the options.
2. Separate the four kinds of support work. Split last year's tickets into break-fix, maintenance, user questions, and enhancements. Many teams find enhancements and user support dominate — and those are precisely what vendor maintenance does not cover.
3. Count your customisations honestly. Heavily customised systems are poorly served by vendor maintenance, which excludes custom code. This is the factor that most often points towards AMS or third-party support.
4. Decide your three-year intent. Staying put, upgrading, or replacing? Third-party support suits staying put; vendor maintenance is the price of the upgrade path. Choosing a support model before deciding this gets the order wrong.
5. Price the internal option properly. Compare against genuine cover — not one person's salary, but the holiday, attrition, and out-of-hours risk that comes with a team of one.
6. Check the exclusions, not the inclusions. Every provider's marketing lists what is covered. The budget is set by what is not: integrations, custom reports, month-end support, response times outside business hours.

---

Frequently Asked Questions

What is included in ERP support services?

Most ERP support covers break-fix, patches, security updates, and statutory or regulatory changes. Broader AMS contracts add user support, configuration changes, and small enhancements. Vendor maintenance generally excludes your customisations, integrations, and user questions — read the exclusions before assuming coverage.

How much do ERP support services cost?

Vendor maintenance on a perpetual licence typically runs around 18–22% of the original licence cost per year (SAP Enterprise Support, for example, is priced at 22%). Third-party support commonly costs around half the vendor fee, though advertised savings range as high as 90%. Partner AMS is usually a monthly retainer or hour block, priced by scope. SaaS subscriptions bundle basic support, with premium tiers charged extra.

What is the difference between ERP support and ERP maintenance?

Maintenance is the vendor's contractual obligation to keep the software patched, secure, and legally compliant. Support is the broader operational job of keeping your implementation working, including customisations, integrations, and users. Maintenance is one component of support, not a synonym for it.

What is third-party ERP support?

Third-party support is maintenance from an independent provider rather than the software vendor. Providers such as Rimini Street, Spinnaker Support, and Support Revolution maintain your current version — including out-of-support versions — usually at around half the vendor's fee, but without new releases or vendor-issued patches.

Can I switch ERP support providers?

Yes, though timing matters. Vendor maintenance renews annually, so switching usually aligns with the renewal date and requires notice. Leaving and later returning has historically meant paying back-maintenance for the lapsed period; SAP announced in July 2026 that it would cap that at the lesser of six months or 50% of the fees for the time off and drop administrative fees for returning customers, but terms vary by vendor. Treat the move as a multi-year decision.

Do I still need internal ERP staff if I outsource support?

Almost always. Even a broad AMS contract needs someone internal who owns the system, prioritises the backlog, and translates business needs into requests. Outsourcing support changes what your internal team does; it rarely removes the need for one.

Is ERP support included in a SaaS subscription?

A basic support tier is normally included in cloud ERP subscriptions, covering platform availability and vendor-side defects. It does not usually cover your configuration, integrations, or user enablement, and higher-touch tiers with faster response times are typically charged as an upgrade.

---

Related Resources

• ERP Consultants: Best Firms 2026
• Independent ERP Consultants
• ERP Implementation Cost Breakdown
• ERP TCO Calculator
• ERP Integration: Methods, Tools, and Best Practices
• ERP Training: How to Train Your Team
• SAP ECC 6.0 End of Support: 2027 & 2030 Dates
• Support Announcements & Choices for Microsoft Great Plains Users
• Should You Upgrade or Replace Your ERP?
• ERP Software: Systems, Vendors, and How to Choose