Talk to us
WhatsApp us

Free cloud cost review: we will find the waste in your AWS or Azure bill in 5 business days. Book it

Cloud migration

The EU Data Act and cloud switching: what changes on 12 January 2027

The Data Act removes switching charges from 12 January 2027. It makes leaving a cloud provider cheaper — but not free, and not automatic.

  • Updated
  • 3 min read

The short answer

Under the EU Data Act, cloud providers serving EU customers have been allowed to charge only at-cost switching and data egress fees since 12 September 2025, and from 12 January 2027 they may not charge for switching at all. The rules also set maximum notice and transition periods. Ongoing egress during parallel multi-cloud use is not covered by the ban.

Key takeaways

  • Switching charges are prohibited from 12 January 2027 for customers in the EU
  • Until then, providers may charge only their actual costs
  • Parallel multi-cloud use and ongoing egress are not covered by the ban
  • The rules make exit cheaper; they do not make it simple
The EU Data Act and cloud switching: what changes on 12 January 2027

For years, the cost of leaving a cloud provider was partly technical and partly commercial. Moving data out was charged by the gigabyte, contracts had long notice periods, and the friction kept customers where they were. The EU Data Act changes the commercial part. Its cloud-switching rules have applied since 12 September 2025, and on 12 January 2027 the final stage takes effect: providers may no longer charge customers for switching.

What the switching rules require

The Data Act applies to providers of data processing services — cloud infrastructure, platforms and software — offered to customers in the EU. Its switching chapter gives customers a set of rights that providers must write into their contracts:

  • A maximum notice period. Customers can start switching with no more than two months' notice.
  • A transition period. Once switching starts, the provider must support it for a transitional period, normally thirty days, which can be extended in defined circumstances.
  • Data export. Customers must be able to retrieve their exportable data and digital assets, and providers must describe what can be exported.
  • Charges. Since 12 September 2025, switching and egress charges must not exceed the provider's costs. From 12 January 2027, they are prohibited entirely.

What the ban does not cover

The headline — "free switching" — is easy to over-read. Three things remain chargeable or outside the rules:

  • Parallel use. If you run workloads across two providers at once, ongoing data transfer between them is not switching. Providers may charge for it, at cost.
  • Normal egress. Data served to your users or partners in the ordinary course of business is not switching either.
  • Your own costs. Re-architecting, re-testing, retraining and running two environments during a migration are the bulk of any move, and the Data Act does nothing about them.

In practice, the large providers had already announced free data transfer for customers leaving their platforms in 2024. The Data Act turns that from a policy that could change into a legal obligation for EU customers, and extends it to providers that had not followed suit.

Who benefits most

The change matters most for organisations that were held in place by egress costs rather than by technology: data-heavy estates with large object stores, analytics platforms and backups. It also matters for businesses using smaller European cloud and hosting providers, whose contracts often had longer notice periods and less generous exit terms than the hyperscalers'.

It matters least where the real lock-in is architectural — workloads built deeply on one provider's proprietary services. Moving those is a rebuild, and the cost of switching charges was never the main obstacle.

How to plan a move around January 2027

  1. Read your current contract. Find the notice period, the exit provisions and how the provider has updated its terms for the Data Act.
  2. Separate switching from parallel running. Plan the migration so the period in which both environments run, and exchange data, is as short as is safe.
  3. Time the bulk transfer. If a large data transfer would fall shortly before 12 January 2027, it may be worth scheduling it after that date. If the move is urgent, at-cost charges apply until then.
  4. Document the exit request properly. The rights are triggered by a formal request under the contract; make sure it is made the way the contract specifies.
  5. Budget for your own effort. The ban removes a line from the bill, not the project.

The wider effect: exit planning becomes credible

For regulated firms, the Data Act arrives alongside rules that already require exit plans — DORA for EU financial entities, and operational-resilience regimes elsewhere. An exit plan that assumed punitive egress charges can now be revised with lower costs. That makes it more realistic to test, which is what regulators increasingly expect. If you are reviewing a provider relationship, our Paris and Berlin migration pages show how the rules apply in those markets.

Frequently asked questions

Switching charges are prohibited from 12 January 2027. Between 12 September 2025 and that date, providers may charge only their actual costs for switching and egress.

No. Ongoing transfer between providers during parallel use is not switching, and providers may still charge for it at cost.

It applies to providers offering data processing services to customers in the EU, regardless of where the provider is based. Customers outside the EU are not covered by these rights.

It removes the provider's switching charges. Your own costs — re-architecture, testing, running two environments and moving people — usually remain the largest part of any migration.

Planning an exit or a second provider?

We will review your contract terms and estate, separate what is switching from what is parallel running, and build a migration plan that keeps the costs you still pay as low as possible.

Keep reading

How to sequence migration waves

A wave plan is where a migration succeeds or turns into an eighteen-month grind. How to group workloads, size the waves, and gate…

3 min read

What belongs in an AWS landing zone

The foundation every workload lands on. What a landing zone contains, why each part has to exist before migration starts, and…

3 min read