Your ERP administrator just resigned, leaving you with three years of technical debt and a maintenance contract up for renewal in six months. Or your security auditor has submitted their report: your on-premise ERP infrastructure is riddled with vulnerabilities your team simply doesn’t have the bandwidth to fix. Or, more straightforwardly: you have 180 users on Sage 200 or Business Central, one “ERP point person” on your IT team, and the nagging feeling you’re paying too much for too little.
These situations are the daily reality for a majority of mid-market European companies. And each one raises the same fundamental question: should you keep managing your ERP operations in-house, or hand off some or all of it to an external provider? This guide is not an argument for or against outsourcing. It’s a decision framework so you can reach your own conclusion — with your own numbers.
The 5 Triggers That Push Mid-Market Companies to Outsource Their ERP
CIOs rarely choose ERP managed services out of philosophical conviction. The decision usually arrives under pressure from one of these five situations.
Overloaded IT Team or Difficulty Recruiting ERP Talent
A competent Sage 200 or SAP Business One administrator commands a salary that many mid-market companies struggle to match against the competition from SIs and software vendors in permanent hiring mode. When your internal ERP resource leaves, you’re looking at either six months to replace them, a 40% salary premium over their predecessor, or both.
A Managed Service Provider pools these scarce human resources across a portfolio of clients. You’re no longer buying a random contract from the job market — you’re buying a contractually defined service level.
End of TMA Contract with Your Legacy Integrator
The Application Maintenance (TMA) contract signed right after your go-live expires in six months. This is the ideal moment to rethink your operating model — and potentially reduce your annual bill by 20–35% by creating competitive tension between TMA providers, MSPs, and the vendor’s own support.
Contract renewal is also the only moment where you hold real negotiating leverage. Don’t let it pass without exploring your alternatives.
Migration to SaaS ERP: An Opportunity to Adopt a Managed Model from Day One
When you migrate from an aging on-premise ERP to SAP S/4HANA Cloud Public Edition, Dynamics 365 Business Central, or Odoo 18 in SaaS mode, the managed services question looks different. The vendor handles the infrastructure. But someone still needs to manage configuration, customisations, functional upgrades, and Level 2 user support.
Handing that role to an MSP certified on your new ERP from day one saves you from rebuilding internal expertise on a technology you’ve just adopted.
International Growth with Multi-Site ERP Difficult to Manage Centrally
Opening a subsidiary in Poland, a warehouse in Spain, and a holding company in Belgium means multiplying local regulatory requirements — e-invoicing mandates, local VAT rules, statutory reporting — across a single information system. Managing this with a centralised IT team that has never dealt with Poland’s KSeF or Spain’s SII exposes you to costly compliance failures or deployment delays.
An MSP with multi-country presence or multi-tax expertise can absorb this complexity at a lower cost than internalising it.
Adverse Security Audit on On-Premise ERP Operations
Keeping an on-premise ERP properly patched requires an operational discipline — patch cycles, regression testing, planned maintenance windows, P1 incident monitoring — that many generalist IT teams can’t sustain. An ISO 27001 or NIS2 audit that identifies your ERP as your primary attack surface is often the trigger that tips a CIO toward managed services.
The 3 ERP Outsourcing Models You Need to Know
These three models are not interchangeable. Choosing the wrong one is expensive.
TMA (Application Maintenance Services) — The Classic Model
TMA is the traditional model. An ERP integrator takes over corrective maintenance (bug fixes), adaptive maintenance (regulatory and version updates), and evolutionary maintenance (new features within the contracted scope). Infrastructure remains your responsibility or your hosting provider’s.
TMA fits when your ERP is operationally stable but you lack the internal resources to manage update cycles and Level 2–3 tickets.
What TMA does not cover: infrastructure monitoring, Level 1 helpdesk, and operational incident management (a database that bloats overnight, a batch job that fails at 3am). These fall either to your internal IT or to a separate MSP contract.
ERP Managed Services (MSP) — Full Operations: Infrastructure + Application + Ongoing Maintenance
The ERP Managed Service Provider handles the full scope: hosting, 24/7 monitoring, system and application patch management, user support (often Level 1–3), and ongoing maintenance management. You buy contractual availability, not hours.
MSP is the right model for mid-market companies that want to outsource all “run” activities and retain only “build” internally (projects, business integrations). It’s also relevant when your ERP runs on a private or hybrid cloud infrastructure you no longer want to operate yourself.
Key difference from native SaaS: an MSP can operate your existing, heavily customised ERP — including all your specific developments — without forcing a reimplementation. That’s often what makes it indispensable for ERPs that have accumulated a decade of customisations.
BPO (Business Process Outsourcing) — Outsourcing the Business Process Along with the Tool
BPO goes further than MSP: the provider doesn’t just operate your ERP, they execute your business processes through it. You buy an operational outcome — “all supplier invoices processed within 48 hours” or “payroll delivered by the 25th of each month” — not a technical SLA.
ERP BPO makes sense for well-defined, stable processes: accounts payable, payroll, expense management, collections. In return, it requires a longer contract relationship (3–5 years minimum) and the ability to measure outcome KPIs, not just technical service levels.
What a Strong ERP Managed Services Contract Must Contain
A poorly negotiated ERP managed services contract can lock you in for three to five years under terms you’ll regret at the first major incident.
Availability SLA: 99.5% vs 99.9% — What the Difference Actually Costs
A 99.5% availability SLA allows 43.8 hours of cumulative downtime per year. A 99.9% SLA allows 8.7 hours. The nominal difference seems small — until that downtime falls during your month-end close or annual inventory.
Negotiate two things systematically: first, the exact calculation methodology — are “planned maintenance windows” excluded from the counter? (They often are in standardised contracts.) Second, the penalties that apply when the SLA is missed. An SLA without contractual penalties is just a marketing promise.
Disaster Recovery: The RTO and RPO You Must Define
RTO (Recovery Time Objective) defines the maximum time to restore service after a major incident. RPO (Recovery Point Objective) defines the maximum acceptable data loss. Both metrics must appear in black and white in your contract, by criticality level.
For an ERP supporting accounting and commercial operations, an RTO of 4 hours and an RPO of 1 hour are reasonable benchmarks in production mode. An RTO of 48 hours is unacceptable if your ERP supports real-time operations.
Governance: Review Committees and Escalation
A good managed services contract includes documented governance: monthly review meetings with incident reporting, a P1 escalation procedure (24/7 on-call?), response time SLAs by priority (P1: 30 min, P2: 4h, P3: 24h), and a named contact on the provider side.
The absence of formalised governance is the leading source of disputes at contract end — “You never escalated properly, so the penalty doesn’t apply.”
Reversibility: The Clause That Matters Most
The reversibility clause is the most neglected point in managed services contracts and the most expensive to fix after signing. What happens when you decide to switch providers or bring operations back in-house? You need a clean database in a usable format, with up-to-date technical documentation.
Negotiate explicitly: data export format (raw SQL, not proprietary backups only), delivery deadline (30 days maximum), and technical handover support during the transition period (1–3 months). Some providers offer paid “portability” clauses — factor that cost into your 5-year TCO from day one.
Security: The Certifications to Require
For an ERP MSP in 2026, systematically require ISO 27001 certification (information security management), and for providers hosting on a hyperscaler, a recent SOC 2 Type II report (no more than 12 months old). If your ERP contains health data (pharma, medical devices), add the relevant data hosting certification for your jurisdiction (HDS in France, equivalent accreditations elsewhere in the EU). And regardless of scope, a GDPR-compliant DPA (Data Processing Agreement) is non-negotiable.
Managed Services vs Native SaaS ERP: When One Beats the Other
Native SaaS ERP (Dynamics 365, SAP RISE, Odoo Cloud)
A native SaaS ERP bundles application maintenance, updates, and infrastructure into its subscription. It’s the operationally simplest model: your internal team no longer manages patches, monitoring, or backups. Update cycles are automatic or semi-automatic depending on the vendor.
The trade-off: less customisation flexibility, strong dependency on vendor roadmap decisions, and data portability that must be planned from the outset.
Choose native SaaS when: your current ERP has no heavy customisations, your IT team is small, and your priority is operational simplicity over control.
Managed Services for On-Premise or Private Cloud ERP
MSP managed services make sense when your ERP is heavily configured, with specific developments that wouldn’t survive a reimplementation. It lets you continue leveraging your software investment while delegating operations to a competent third party.
Choose MSP managed services when: your ERP has 5+ years of accumulated configuration, your integrations with other systems (MES, WMS, CRM) are complex, and migrating to SaaS would impose a 12–24 month reimplementation project you don’t have the budget or bandwidth to absorb right now.
The Lift-and-Shift Trap: A False Economy Worth Avoiding
“Lift-and-shift” means migrating your existing on-premise ERP to an MSP or hyperscaler without changing its architecture or modernising it. The physical server disappears, replaced by a VM in a third-party data centre. Infrastructure costs drop 20–30%. But the technical debt stays intact — and often accumulates faster, because no one feels responsible for unmaintained modules.
Before signing a lift-and-shift contract, ask your MSP: “What’s stopping us from doing this natively in the cloud?” If the answer is “your ERP version is no longer vendor-supported,” you haven’t solved your problem. You’ve transferred your technical debt to a provider who will be paid to preserve it.
ERP Managed Services Costs: 2026 Benchmarks
Monthly Cost Ranges by ERP Size
The figures below are indicative and vary significantly depending on scope (TMA only, full MSP, partial BPO), configuration complexity, and provider location. Costs are shown in EUR; roughly equivalent in GBP and USD at current rates.
| ERP Size | TMA Only | Full MSP |
|---|---|---|
| 50 users (SME) | €1,500–3,500/month | €3,000–7,000/month |
| 150–200 users (mid-market) | €4,000–9,000/month | €8,000–18,000/month |
| 400–500 users (large mid-market) | €10,000–22,000/month | €18,000–45,000/month |
These ranges assume a standard ERP package with moderate customisation. A heavily customised ERP with critical interfaces (EDI, MES, WMS) can double the upper end.
5-Year TCO Comparison: In-House vs TMA vs MSP vs Native SaaS
The true TCO of in-house ERP operations is routinely underestimated. You must count the full loaded cost of your ERP manager (salary plus employer contributions), ongoing training, hardware, infrastructure licences, and — critically — the hidden cost of incidents left unresolved because internal resources are stretched.
Over a 5-year horizon, mid-market companies with 150–200 users frequently find that full MSP total cost is comparable to in-house operations — with a contractually guaranteed service level that internal teams can rarely match consistently. Native SaaS tends to show the lowest gross TCO, but only when migration doesn’t require a heavy reimplementation project.
How to Select an ERP Managed Services Provider: 8 Criteria
- Certifications on your ERP: Are they a Gold/Platinum partner of your vendor? How many consultants are certified on your specific version?
- Support model: Is the helpdesk in-house or outsourced offshore? What is the actual (not nominal) response time reported by their current clients?
- Operational disaster recovery: Have they actually activated their DR plan under real conditions? Ask for a reference from a client who experienced a P1 incident.
- Portfolio size and similarity: Do they manage clients of your scale and in your sector? An MSP accustomed to 30-user SMEs won’t be comfortable with your 300-user mid-market environment.
- Security certifications: ISO 27001 current, SOC 2 Type II if applicable, EU data residency (required for GDPR compliance).
- Transparency on subcontractors: An MSP hosting on AWS or OVHcloud must explicitly disclose their subcontracting chain and allow you to audit GDPR compliance.
- Pricing model and scope creep controls: Is the contract fixed-fee, consumption-based, or hybrid? How are out-of-scope requests billed and controlled?
- Reversibility policy: What is their documented exit policy? A provider that refuses to detail their reversibility terms during initial negotiations will be even less cooperative when you want to leave.
Simplified Decision Matrix
Before moving to an RFP, answer these five questions:
| Question | Towards TMA | Towards MSP | Towards Native SaaS |
|---|---|---|---|
| Can your internal IT team manage ERP infrastructure? | Yes | No | No |
| Does your ERP have heavy customisations? | Yes | Yes | No |
| Can you absorb a full migration project? | — | — | Yes |
| Is your sector heavily regulated? | Review with TMA | Yes (SOC 2, ISO 27001) | Depends on vendor |
| Is your priority cost or control? | Control | Control | Cost |
If you answer “No” to the first question and “Yes” to the second, MSP managed services is your natural scenario. If you answer “No” to the second and “Yes” to the third, explore native SaaS with a migration planned over 12–18 months.
To go deeper on contractual aspects before launching your managed services RFP, see our ERP TMA maintenance contract guide and our analysis of ERP cost optimisation levers after go-live. If your thinking runs in the opposite direction — moving from cloud managed services back to more controlled on-premise operations — read our article on ERP cloud repatriation: when and how.
