What It Actually Costs to Leave MPLS: Termination Liability, Parallel Running and the Break-Even Month

Leaving MPLS costs more than the monthly saving suggests. Termination liability typically runs 50% to 100% of remaining-term charges, the parallel run adds three to six months of paying for two networks, and each site costs €2,500 to €6,500 to move. On a twelve-site estate, break-even lands between 16 and 79 months depending on how much term is left.

The monthly saving is the easy number. Every comparison page has it: MPLS at roughly €1,200 a month for a gigabit port, broadband at a few hundred, a 30% to 60% reduction in recurring transport spend. That number is not wrong. It is also not the number that decides anything, because it describes the destination and says nothing about the journey.

The number that decides is the exit. Termination liability on circuits that still have term left. Three to six months of paying for two networks at once. Two and a half to six and a half thousand euros of engineering and hardware per site. And the month — a specific month, which you can calculate — at which the accumulated savings finally overtake what the exit cost you. For a mid-market estate leaving mid-contract, that month is frequently in year three.

Jimber sells a SASE platform, which means we sell the thing on the other side of this migration. Stating that up front matters here more than in most articles, because the entire value of what follows depends on the cost sections being honest rather than flattering. If you catch us understating the exit, you should discount the recommendation.

Why nobody publishes the real MPLS exit cost

We tested a hypothesis before writing: that the exit mechanics are absent from the search results not by accident but because every publisher on page one has a reason to leave them out. The hypothesis held.

Page one across mpls replacement, mpls migration cost, mpls exit cost and mpls to sd-wan migration divides into three groups, and all three are interested parties.

Carriers — Proximus, Orange Belgium, the national regulator’s own guidance pages — treat termination as a legal formality. They publish general terms that state the maximum contractual penalty and say nothing about the commercial settlement that is actually reached in practice. Publishing the real buyout range would hand every customer a negotiating position.

SASE and SD-WAN vendors — Fortinet, Cloudflare, Check Point, Netskope — publish the recurring saving and stop there. A page that says “your operational savings begin in month 17” lengthens every sales cycle it touches. So the capital required to terminate the agreement, fund dual transport during cutover and re-engineer the edge security perimeter is simply not in the material.

Independent brokers and consultancies — Lightyear, ObsidianX — come closest, with genuine circuit pricing. But they are in the business of procuring circuits, not of unwinding contracts, so the granularity sits on the buying side and not the leaving side.

What remains is r/networking, where practitioners discuss real settlements in threads that no vendor will cite. The AI Overviews on these queries synthesise the vendor position — rigid expensive circuits, cheap aggregated broadband, dynamic path selection — because that is what the crawlable, authoritative corpus contains.

So the question nobody on page one answers is this one: what is the actual formula for termination liability across the European contract structures, how many months of parallel running do you have to capitalise, and in which month does the whole thing break even? The rest of this article is that answer. If you need the architecture explained first, that is MPLS explained and why SD-WAN is replacing it; if you want the engineering sequence rather than the money, that is the MPLS replacement exit playbook. This page owns the money.

The five contract shapes, and what each one charges you to leave

Total exit liability is the sum of four things: early termination charges on remaining term, clawback of any capital the carrier amortised into your monthly rate, shortfall charges against a volume commitment, and equipment recovery. Which of those apply depends entirely on the shape of the agreement.

Use the right-hand column as a checklist against your own contract. These are the clauses that determine your number; the number itself is in your paperwork, not in this table.

The Belgian position, and why the six-month rule does not help you

Belgian enterprises regularly ask about the statutory termination right. It exists, and it almost certainly does not apply to you.

Under the Law of 13 June 2005 on Electronic Communications, transposing the European Electronic Communications Code, Article 111/3 gives end-users and micro-enterprises the right to terminate a fixed-term electronic communications contract without early termination fees after the sixth month, with equipment clawbacks limited to a linear depreciation table of no more than 24 months. The threshold for a micro-enterprise is fewer than nine employees. An organisation of 50 to 1,000 people is explicitly excluded, and commercial freedom of contract governs instead. Belgian incumbents enforce termination indemnities equivalent to 100% of the remaining fees unless something else was negotiated at signature.

Two provisions do remain useful. After the initial fixed term ends, a tacitly renewed contract can be terminated by an enterprise subscriber with a maximum notice period of one month — though carriers frequently restart a multi-year term when a bandwidth upgrade or hardware refresh is executed, so check whether your “renewed” contract is in fact a new one.

And under Article 108 §4, a unilateral amendment to contractual terms gives you a one-month window to terminate without penalty. That right does not apply where the price change follows a contractual indexation clause tied to the consumer price index or health index, which is standard in Belgian enterprise agreements. Read the increase notice carefully: an indexed rise closes the door, a commercial restructuring opens it.

The per-site cost of the transition itself

Separate from anything the carrier charges you, every site costs money to move. These are sourced ranges in euros, verified against carrier commercial schedules and practitioner deployment records; they are ranges rather than quotes, and your own figures will sit somewhere inside them depending on how urban and how on-net the site is.

The contingency line is the one most often left out of a business case and the one most often spent. A 10% to 15% abort rate across a twelve-site estate means one or two failed cutovers, each requiring remediation and a second engineer visit. Budget for it as a certainty distributed across the project rather than a risk that might not land.

The parallel run, and why you cannot skip it

For three to six months on a mid-market estate you will be paying for two networks. This is not caution or poor planning; it is the arithmetic of five constraints that each have a floor.

Provisioning lead times. Dedicated internet access from enterprise carriers across Western Europe takes 60 to 120 calendar days. Municipal excavation permits, fibre splicing and building entry works routinely extend that. Commodity broadband arrives in 10 to 20 days but carries no performance SLA, so it cannot be the primary path at a site that needs one.

Transit interconnect. During a phased rollout, migrated sites on internet transport still have to reach unmigrated sites on the legacy MPLS core. That requires a dual-homed transit hub or colocation interconnect where MPLS VRFs are redistributed into the new fabric over BGP — and that infrastructure stays funded and operational until the last branch moves.

Cutover cadence. Internal teams generally manage two or three branch cutovers per week. Twelve sites is four to six weeks of deployment windows. Fifty sites is four to six months.

Post-cutover stabilisation. Engineering practice is to keep the physical MPLS circuit on site as an unadvertised fallback for 30 to 45 days after cutover, so that latent MTU mismatches or application routing failures can be fixed without taking the branch down.

Decommissioning notice. Carriers require 30 to 90 days’ written cancellation notice ahead of the billing cycle. Serve it after a successful cutover and you pay for an idle circuit for up to three months.

The single most effective lever on total exit cost is not negotiating the penalty down. It is aligning the end of parallel running with the natural expiry of the contract, so that the penalty never arises.

The break-even model, worked

Four inputs and one division. The output is the month in which accumulated savings finally overtake what the exit cost you — which, in the worked example below, ranges from 16.4 months on a co-terminated contract to 79.2 months on an unmitigated eighteen-month exit. Substitute your own numbers for every figure.

Break-even, in months, equals your total sunk capital divided by your net monthly saving.

Total sunk capital is the early termination liability (remaining-term penalties, construction clawbacks and any commitment shortfall), plus the one-time transition capital across all sites, plus the parallel-run expense (overlap months × the monthly cost of the replacement stack, which you are paying on top of the legacy bill).

Net monthly saving is the legacy monthly spend minus the replacement monthly spend, where the replacement includes circuits, platform licensing and managed support — not circuits alone.

A twelve-site worked example

An illustrative mid-market enterprise: headquarters in Brussels, a datacentre in Amsterdam, ten branches across Flanders, Wallonia and the southern Netherlands. Every figure below is illustrative, drawn from sourced benchmark ranges, and is there so you can see the structure rather than adopt the numbers.

Legacy spend. Two 1 Gbps MPLS circuits with carrier SLAs at an illustrative €1,200 per month each for the two core sites (€2,400). Ten 100 Mbps branch circuits at an illustrative €650 each (€6,500). A consolidated carrier management wrapper at an illustrative €1,100. Total: €10,000 per month.

Replacement spend. Dual diverse 1 Gbps DIA at the two core sites at an illustrative €650 each (€1,300). Each branch on 200 Mbps DIA at an illustrative €348 plus a 500/100 Mbps business broadband link at an illustrative €80, giving €428 per branch (€4,280). SASE and SD-WAN licensing at an illustrative €120 per site (€1,440). Total: €7,020 per month.

Net monthly saving: €2,980, or 29.8%. Not 60%. The gap between this figure and the one in the vendor comparison is the difference between a design with a dedicated primary circuit at every branch and a design with two commodity broadband links.

Run the branches on dual business broadband instead and transport drops to an illustrative €160 per site, total replacement spend falls to an illustrative €4,340 and the saving rises to €5,660, or 56.6% — which is where the marketing number comes from. It is achievable. It is also a different resilience design, and you should decide which one you are buying before you decide which saving you are quoting.

One-time transition capital. Ten branch broadband drops at an illustrative €250 (€2,500), with primary DIA install fees assumed waived under 36-month terms. Twelve edge appliances at an illustrative €850 (€10,200). Twelve site installations including after-hours premiums at an illustrative €1,000 (€12,000). A 15% contingency reserve (€3,000). Total: €27,700.

Parallel run. Three months of average site overlap across the estate, at the €7,020 replacement run rate: €21,060.

On the dual-broadband design, with a €5,660 monthly saving, those break-even points compress to an illustrative 8.6, 17.0 and 41.7 months respectively. Note what that variant holds fixed: both the one-time capital and the €21,060 overlap cost stay at the figures calculated for the DIA design. In reality the overlap would also be cheaper, because you would be double-paying for a cheaper replacement stack — so treat 8.6 months as the conservative end rather than the precise answer.

The conclusion the arithmetic supports: exiting with more than twelve months of unmitigated term remaining is a poor financial decision. Scenario C is not a long payback, it is not a payback — 79 months exceeds the useful life of every piece of equipment in the project. Scenario A pays back inside a normal budget cycle. The whole game is moving your situation from C towards A, and the two ways to do that are negotiation and timing.

What actually gets negotiated

The stated contractual penalty is an opening position, not a settlement. Practitioner reports from network engineering communities put commercial buyouts at 30% to 50% of remaining-term charges, and describe carriers waiving the termination fee entirely where the customer converts the circuit instead of cancelling it. Four levers come up repeatedly.

Convert the circuit rather than cancel it. The most effective lever is giving the carrier an alternative revenue stream. Instead of terminating, negotiate to convert the MPLS port into dedicated internet access over the same physical local loop for the remainder of the term. Faced with losing the account entirely, carriers frequently waive termination fees to retain high-margin internet transit revenue, even where monthly spend falls by around 40%. This also solves your primary-circuit problem at the site, which is why it tends to be the first thing to try.

Settlement ceilings. Where full termination goes ahead, practitioner reports put commercial buyouts at 30% to 50% of remaining-term monthly charges, particularly where the customer commits to a lump-sum payment within 30 days or keeps other services — a corporate mobile fleet, for instance — with the same carrier.

Documented SLA breach. Contracts contain a termination-for-cause clause. Proving persistent material failure against contractual MTTR or packet-loss thresholds, then serving a formal 30-day cure notice, gives a route out without penalty if the carrier does not remedy. This requires the documentation to exist already, which is an argument for keeping SLA performance records whether or not you intend to leave.

Infrastructure sunsets. Ongoing copper and PSTN decommissioning across Europe is leverage. When a carrier retires a legacy connection and moves the service to fibre under altered commercial terms, that is frequently a unilateral change — and the right to cancel without penalty follows from it.

When MPLS is still the right answer

MPLS remains correct for sites needing deterministic latency under 10 milliseconds, for legacy on-premises voice that cannot tolerate jitter above 20 milliseconds, for locations without diverse fibre where civil works are prohibitive, and where a regulator mandates physically isolated transit. In practice this covers a few sites, not the estate.

This section exists because an article from a SASE vendor that concludes MPLS is never justified is not credible, and because for a specific set of sites it genuinely is the correct architecture.

Deterministic latency for industrial control. Production facilities running synchronised robotics, PLCs, distributed control systems or SCADA control loops need bounded round-trip latency under 10 milliseconds and negligible jitter. The public internet routes on BGP peering economics rather than path optimisation, and the packet delay variation that introduces can trigger automated safety trips. That is a production stoppage, not a performance complaint.

Legacy on-premises voice. Modern cloud UCaaS handles impairment with forward error correction and dynamic jitter buffers. Legacy on-premises PBX systems and inter-site SIP trunking on G.711 do not: audio degrades once packet loss passes 1% or jitter passes 20 milliseconds. MPLS enforces this deterministically by prioritising voice in expedited forwarding queues across a private backbone.

SLAs with financial teeth. Enterprise MPLS contracts carry 99.99% or 99.999% availability backed by four-hour on-site mean time to repair, with a dedicated carrier NOC and pre-positioned spares. Commercial business broadband rarely commits to better than 24 to 48 business hours. The difference in remedy is starker still: high-tier MPLS SLAs oblige the carrier to reimburse substantial percentages of monthly spend or compensate direct commercial damages, while public internet SLAs typically cap liability at service credits of 5% to 15% of the prorated daily circuit charge. If a site outage costs you more per hour than the circuit costs per year, that asymmetry is the whole argument.

Last-mile infrastructure deficits. In rural regions, older industrial zones and logistics parks — parts of Wallonia, the Ardennes, rural northern Netherlands — there is frequently one physical cable and one operator on it. New DIA means civil excavation quoted in tens of thousands of euros, and the available alternative is asynchronous VDSL2 or consumer cellular. Where symmetrical throughput is genuinely required, the existing leased line may be the only physical option.

Mandated isolation. Central banking interfaces, payment clearing and certain trading platforms periodically require logical or physical isolation from the public internet. Organisations handling classified government data or defence manufacturing contracts face national accreditation authorities that do not accept public internet encryption as sufficient, which makes private carrier-certified circuits a legal obligation rather than an engineering choice.

In practice this rarely means the whole estate stays. It means three sites stay and nine move, and the break-even model runs on the nine.

What changes about security, and what NIS2 expects you to document

Moving site traffic from a private carrier core to public underlays changes the perimeter, and the compliance consequence is a documentation obligation rather than a prohibition. You encrypt all inter-site traffic, clamp TCP MSS before cutover, add local inspection at every branch, and document both the cryptography and each new internet provider as a supply chain dependency.

MPLS packets cross carrier backbones unencrypted on label-switched paths, isolated from other customers by VRF tables but travelling in cleartext across carrier equipment. On a public underlay, 100% of inter-site traffic has to be encrypted with IPsec or WireGuard. That adds processing load at the edge and reduces the effective MTU from 1500 to roughly 1420 bytes, which means TCP MSS clamping — typically to 1360 to 1400 — configured on the edge devices before cutover. MTU mismatch and silent fragmentation account for a large share of cutover failures, and this is the single configuration item most worth checking twice.

Local internet breakout at every branch replaces backhaul to a central firewall, which exposes local interfaces directly and requires next-generation firewalling, intrusion prevention, DNS filtering and DDoS protection at each site. And MPLS gave you flat any-to-any Layer 3 reachability: one compromised branch reached everything. A Zero Trust model replaces that with continuous identity authentication and application-level microsegmentation, which is the part of the change that actually improves your position rather than merely preserving it.

On the regulatory side: NIS2 Article 21 requires state-of-the-art cryptography for data in transit, so the migration needs documented end-to-end cryptographic integrity across all inter-site paths. Article 21(2)(d) covers supply chain, and this is the clause people miss — you have replaced one telecom agreement with several regional ISPs, and each of them now has to be assessed and monitored.

Under the Belgian CyFun framework, which the CCB operates as the NIS2 baseline, you will be asked for an updated network architecture dossier confirming that branch internet breakouts do not expose operational technology or sensitive environments without intermediate inspection. Financial entities have more: DORA Articles 28 to 44 require pre-migration risk evaluation, proof of multi-vendor transport diversity, confirmation that the broadband links do not share a common physical point of failure, and exit plans covering the failure of the edge cloud provider.

None of that blocks the migration. All of it is easier to produce during the project than to reconstruct afterwards, which is the practical advice.

Steelman: staying put through the term

The network manager arguing to stay is not being obstructive, and if he has survived a failed WAN migration he is arguing from evidence. Three points, taken at full strength.

Paying unmitigated liquidated damages is financially irrational. Scenario C above is the argument in a table. Transferring €180,000 from an operating budget into a carrier penalty to capture €2,980 a month is a transaction that never returns. Running the term out costs nothing, extracts the full utility of investments already sunk, and buys the months needed to design, trench and validate the replacement without a deadline. The correct migration date is frequently a date in the future, and choosing it is not procrastination.

One accountable carrier is worth more than it looks on the invoice. MPLS puts a single provider on the hook for end-to-end transport under a contract with financial consequences for chronic degradation. Dual-broadband SD-WAN moves the troubleshooting burden onto your team. When a path is cut or an intermediate autonomous system misroutes, you are the one arbitrating between two local ISPs, a software vendor and a managed security provider, none of whom own the fault. For a lean IT department, administering a dozen ISP accounts, invoices and support queues consumes real capacity — and that capacity has a cost that does not appear in the break-even model above.

Best-effort is still best-effort. Dynamic path selection and forward error correction mitigate the characteristics of the public internet; they do not remove them. At peak, public routes carry latency spikes, jitter and loss that degrade real-time applications, and no overlay changes what the underlay is doing. Where an unplanned stoppage carries severe financial consequence, paying for engineered bandwidth with deterministic queue prioritisation is a defensible risk decision rather than a legacy habit.

Where the argument weakens: it is a case for timing, not for permanence. Every point above is answered by co-terminating the migration with contract expiry rather than by renewing for another 36 months. And a renewal signed to avoid a penalty resets the clock, which converts a one-time cost into a recurring reason never to leave. If you stay, stay deliberately, with the exit designed and the expiry date in the project plan.

What to do before you ask for a quote

Three things, in order, and none of them requires a vendor.

First, pull every circuit contract and build one row per circuit: end date, monthly charge, notice period, and whether installation or construction was waived. Co-termination opportunities become visible immediately, and so does the true size of your liability — which is frequently smaller than assumed because the estate expires in waves rather than at once.

Second, price the conversion option with your incumbent before pricing the exit. Converting MPLS ports to DIA on the same loop is the cheapest path out of the penalty and it is a conversation, not a project.

Third, run the break-even calculation above with your own numbers before anyone builds you a business case. If it lands past month 24, the answer is not “don’t migrate” — it is “migrate on a different date”.

When you do move, the security layer and the transport layer no longer have to be separate purchases: that consolidation is where the replacement stack cost in the model above either works or does not. Jimber runs both as a single EU-sovereign platform. If you want the cost model applied to your actual circuit list, send us the estate or book a demo. The platform side is at jimber.io/sd-wan and jimber.io/sase.

Related reading, if you need a different part of the picture:

• What MPLS is and why SD-WAN is replacing it — the architecture, if you need it before the money.
• The MPLS replacement exit playbook — the engineering sequence rather than the cost.
• 2026 enterprise MPLS pricing — current circuit benchmarks to replace the illustrative figures above with your own.
• SD-WAN versus MPLS compared and the complete guide to SD-WAN — performance and security, side by side.
• The hidden costs of a SASE migration — what shows up after the project rather than during it.
• Managed SD-WAN for service partners — if you deliver connectivity to clients rather than consume it.

Frequently asked questions

How is an MPLS early termination fee calculated?

Multiply the remaining months of term by the monthly recurring charge, then apply the contractual settlement factor, which typically falls between 50% and 100%. The carrier adds clawbacks for any waived installation charges or civil construction costs amortised into your rate at turn-up. Commitment shortfalls and equipment recovery are charged separately.

How long is the parallel run when migrating off MPLS?

Three to six months for a mid-market network. It is driven by dedicated internet access lead times of 60 to 120 calendar days, the need to run a dual-homed transit hub while some sites are migrated and some are not, a 30 to 45-day post-cutover stabilisation window, and 30 to 90 days of contractual cancellation notice before the billing cycle.

Can a Belgian business exit a telecom contract after six months?

Only if it qualifies as a micro-enterprise with fewer than nine employees. Article 111/3 of the Belgian Electronic Communications Act grants that right to consumers and micro-enterprises. Organisations with ten or more employees are explicitly excluded and are governed by ordinary contract law, making them liable for the negotiated termination damages in full.

What are the one-time costs of moving from MPLS to SD-WAN?

Per site: circuit installation from €150 to €3,500 depending on whether civil works are needed, edge hardware from €500 to €2,500, field engineering from €600 to €1,200, out-of-hours cutover labour from €500 to €1,000, and a rollback contingency of €800 to €1,500 per incident. Consolidated, €2,500 to €6,500 per site.

Does moving from MPLS to the public internet breach NIS2?

No, but it changes what you have to document. NIS2 Article 21 requires state-of-the-art cryptography in transit, so all inter-site traffic must be encrypted with audited cryptography such as IPsec or WireGuard and the coverage evidenced. Article 21(2)(d) then requires you to assess and monitor each new internet provider as a supply chain dependency.

What happens to a minimum annual revenue commitment if I drop MPLS circuits?

If total annual carrier spend falls below the committed threshold, you are billed an under-utilisation shortfall charge equal to 50% to 100% of the difference. The mitigation is to check the contributory services definition: dedicated internet access or a corporate mobile fleet with the same carrier often counts towards the commitment, which lets you redirect spend rather than forfeit it.

Can I avoid the termination fee entirely?

Two routes work in practice. Align each site cutover with that circuit’s natural expiry date so no penalty arises. Or negotiate a conversion: trade the MPLS service for dedicated internet access over the same physical local loop for the rest of the term. Carriers frequently waive the fee to retain the transit revenue, even at 40% lower monthly spend.

When is it too late in the contract to migrate profitably?

With more than twelve months of unmitigated term remaining, the upfront capital generally outweighs cumulative transport savings within a normal planning cycle. In the worked example, an exit with eighteen months left and no negotiated reduction breaks even at 79 months, which exceeds the useful life of the equipment. Negotiate the liability down, or move the date.

When should an enterprise stay on MPLS?

Where sites run industrial control systems needing deterministic sub-10ms latency, where legacy on-premises PBX and SIP trunking cannot tolerate jitter above 20 milliseconds, where the location has no diverse fibre and civil works are prohibitive, or where a regulator or accreditation authority mandates physically isolated transit. Usually this applies to a few sites, not the estate.

Why do finance teams get surprised in year one?

Because year one costs more, not less. The organisation absorbs the full legacy run rate plus the new circuits during the overlap, buys hardware, pays for field engineering, and may settle a termination liability. Recurring savings of 30% to 50% then amortise that from roughly month 16 onwards. Setting that expectation before kick-off is what protects the project’s credibility.