Guides

EU Data Act: When Cloud Switching Fees Are Abolished – What CIOs Need to Examine Now

Starting January 12, 2027, switching charges and egress fees will apply EU-wide.

By Benedikt Langer July 6, 2026 6 min read

EU Data Act: When Cloud Switching Fees Are Abolished – What CIOs Need to Examine Now

From 12 January 2027, cloud providers in the EU will no longer be allowed to charge switching fees or egress fees. Anyone who hasn’t identified which contracts, APIs and data formats bind them to their current vendor by then will still be switching blind-or paying more. Six months’ lead time is barely enough for serious exit planning.

Key Takeaways

Deadline is 12 January 2027, not 2026: Egress and switching fees vanish EU-wide on that date, for IaaS, PaaS and SaaS alike.
The fee was only the most visible lock-in: Proprietary APIs, vendor-specific data formats and IAM binding keep CIOs locked in longer than any invoice.
Contracts do not auto-renew: Existing clauses on automatic extension and migration fees must be actively reviewed, or the old cost structure remains in force.
The Data Act complements the GDPR: GDPR Article 20 governs data portability; the Data Act goes cloud-specific and directly tackles switching fees.

What is actually banned from 12 January 2027

Switching fees and egress fees disappear EU-wide for IaaS, PaaS and SaaS alike. The deadline applies to every provider serving EU customers, not only European vendors. Firms that once paid on every cloud migration or data export will suddenly face a very different negotiating table.

Many companies confuse the date with 2026-no accident. The Data Act entered force in January 2024, most provisions applied from 12 September 2025, yet the cloud-specific switching rules kick in only in January 2027. A compliance roadmap pegged to the old date leaves you unprepared on the deadline day.

Which contract clauses CIOs must review today

Term lengths, auto-renewals and contracts ending before the deadline decide whether a firm even benefits from the new rules. Letting an auto-renewal roll past 12 January 2027 risks years tied to old clauses. Clauses on egress thresholds and migration fees must be explicitly checked now.

Egress costs remain fully budget-relevant until January 2027. For FY 2026 that means old planning; from Q1 2027, new thinking. Ignoring the deadline in budgeting either wastes money or forfeits negotiating leverage that the new law suddenly creates.

Where the real lock-in hides-beyond the price tag

The fee was the most visible lock-in, but not the strongest. Proprietary APIs, vendor-specific data formats and identity binding keep CIOs locked in longer than any invoice. A cheap switching fee is useless if your application is woven into service-specific calls and only the original tool can read the data format.

The Data Act complements GDPR Article 20 on data portability, yet goes cloud-specific. While the GDPR defines the right to receive data, the Data Act targets the practical switching barriers in cloud operations. Clear separation: GDPR answers who gets the data; the Data Act answers what the switch itself costs.

What an exit strategy looks like in practice

An exit strategy on paper isn’t enough. CIOs need a migration stress test for at least one critical workload and an object-storage classification based on portability. Anything that hasn’t been tested will fail on the deadline. Documentation without testing is an audit fund with no practical value.

The stress test boils down to one simple question per workload: can the data export be read in an open format without tool-specific translation? Anyone who can answer “yes” for every workload has a realistic foundation. Anyone who hesitates has already found the real lock-in and must act before-not after-the deadline.

What must happen in the next six months

Concrete steps-not strategy papers-measured against 12 January 2027: compile the contract file with all auto-renewal and termination deadlines, plan FY 2026 egress costs as usual and rethink Q1 2027, run a lock-in audit per workload (API, data format, IAM binding), execute a migration test with one critical workload in 2026, and document an exit strategy with clear responsibilities-not as a PDF gathering dust.

Letting the six months slip by doesn’t just mean continued payments. It also means missing the narrow window where providers respond to the new legal landscape with voluntary concessions. The second half of 2026 is when switching fees become a negotiation topic-before the deadline, because providers know it’s coming.

Frequently Asked Questions

Do our current contracts automatically switch to the new terms on 12 January 2027?

No, they do not. Contracts must be amended, terminated on schedule, or renewed. Clauses on egress thresholds and migration fees should be reviewed explicitly; otherwise the old cost structure remains in force.

Does the Data Act also eliminate inter-region egress and data transfer between availability zones?

The Data Act targets cross-provider switching. Intra-provider region transfer sits in a grey area and is often still billable in practice. A contractual inquiry before the deadline is worthwhile.

What about SaaS data-export formats that only the SaaS tool itself can read?

That’s the real lock-in. The fee may vanish, but the format stays. Demand CSI exports to open formats now or run API-export tests; otherwise the vanished switching fee on the deadline won’t help.

Do we already need to bring up the new legal situation when renewing contracts in 2026?

Yes. The second half of 2026 is the negotiation window where providers react to the upcoming legal changes with voluntary concessions. Negotiating before the deadline yields double benefits: leverage and ongoing legal change.

Does the Data Act apply only to European cloud providers?

No. The 12 January 2027 deadline applies to every provider serving EU customers. US hyperscalers are just as affected as European vendors. Switching to a non-EU provider to sidestep the rules doesn’t automatically remove EU customer protections-though in practice it often lands you in a grey area.