The Data Act Switching Deadline: Egress Fees Disappear on 12 January 2027 — Renegotiate Now

The egress fee was never really about the cost of moving data. It was the moat. The EU Data Act is draining it, and most firms are waiting for a deadline they should be treating as a negotiating position today.

For years the charge to extract your own data from a cloud provider has done a quiet job: it made leaving expensive enough that you stopped pricing the option. A migration that looked sensible on compute and storage economics fell apart the moment someone modelled the egress bill on a few hundred terabytes. The provider rarely had to win the retention argument on merit. The exit toll won it for them. Regulation (EU) 2023/2854 — the Data Act — sets a date on which that toll ends, and a shorter window in which it must already have shrunk. The mistake I keep seeing is reading this as a compliance milestone to observe rather than a commercial event to act on.

What Article 29 actually removes, and when

Article 29 governs the gradual withdrawal of switching charges. It does two distinct things. From 12 January 2027, a provider of data processing services may not impose any switching charge on a customer for the switching process. Before that date — the Data Act has applied since 12 September 2025 — a provider may impose only reduced switching charges, and those may not exceed the costs it actually incurs that are directly linked to the switch. The full-price exit toll is already unlawful. The cost-based residue is on a timer.

The point that matters commercially is the scope of the term. “Switching charges” under the Data Act expressly captures data egress charges levied for the purpose of switching. This is not a narrow rule about a bespoke migration line item. It reaches the per-gigabyte data-transfer-out pricing that has underwritten the lock-in for a decade. From January 2027, for the act of leaving, that number has to be zero. Until then it can only be a genuine cost pass-through, not a margin.

What the article does not touch is the standard fee for the service itself. You keep paying for the compute and storage you actually consume up to the moment you leave. The regulation removes the penalty for leaving; it does not make the service free. Holding those two ideas apart is the whole of the analysis, because the charge you are trying to kill will try to survive by relabelling itself as the charge that is allowed to remain.

Where the charge hides after the headline

A prohibition on switching charges does not abolish the commercial instinct behind them. Expect the cost to migrate into categories the Data Act leaves standing. Four are worth checking line by line.

• Ordinary egress dressed as switching, or the reverse. Egress you incur during normal operation — feeding a multi-cloud pipeline, serving traffic, running parallel workloads — is not switching and remains chargeable. A provider has every incentive to classify your exit traffic as ordinary usage. The distinction is the act of leaving, and it needs to be pinned down in the contract, not left to a billing dispute.
• Early-termination penalties in fixed-term deals. A proportionate early-termination charge in a genuine fixed-term commitment is a different animal from a switching charge and survives. A three-year reserved-capacity term signed now becomes the new exit cost once the egress toll is gone. Read the termination clause as the successor to the egress bill.
• “Additional services” and bespoke migration support. Work outside the provider’s Data Act obligations — handling non-standard data, custom tooling, hands-on migration assistance you asked for — can still be priced. The risk is scope creep, where routine export gets rebilled as premium support.
• Egress on data you cannot practically export. A zero switching charge on data you cannot get out in a usable form is worth nothing. This is where the charge question meets the functional-equivalence duty the Data Act places on your provider: the right to leave without a fee is only real if what you extract actually runs on the other side.

Why you renegotiate now rather than wait for the date

The contract you sign this quarter will almost certainly still be running in January 2027. If it bakes in egress pricing, multi-year lock-ins and termination terms drafted for the old world, the deadline arrives and finds you still bound by the economics it was meant to dismantle. The regulation changes the default; your paper does not update itself.

There is leverage in this that expires if you sit on it. Right now you can go to a provider and point out that the egress charge underpinning their retention case is already capped at cost and disappears entirely within the term you are being asked to sign. That is a stronger position than most procurement teams realise they hold. The firms that treat 12 January 2027 as a date to comply with will renegotiate from weakness in 2027. The firms that treat it as a fact to negotiate against will reprice their exit terms in 2026, while the other side still has something to concede.

The audit, and the number it produces

The work is concrete. Pull every data processing service contract and find, in each, the switching and egress provisions, the termination charges, the fixed-term commitments, and any pre-contract disclosure of standard fees and switching costs — the Data Act requires that disclosure, and its absence is itself a finding. Map which of your data is genuinely portable and which is trapped behind a proprietary format, because that is the difference between a right on paper and an exit you can execute. This is the same discipline as pricing lock-in before you commit to a data platform, applied to contracts you already hold.

The output is a single number you have probably never had: the real cost of leaving each provider, with the egress toll removed and the residual charges named. That number was the thing the fee existed to keep you from calculating. Now that you can, the interesting question is which of your architecture decisions were made because leaving was genuinely wrong, and which were made because the right to leave had a price tag you never seriously tested. The Data Act has just removed the price tag. It has not made the decision for you — it has only taken away your excuse for not making it.