
The EU Data Act: switching cloud provider, and what to prepare first
The EU Data Act has applied since 12 September 2025, and part of it concerns something every IT team touches: the right to switch cloud provider, or move back to your own servers. The provider has to clear the way. But the deadlines are short once you request the switch, so the work happens before that moment.
The EU Data Act has applied since 12 September 2025 and requires cloud providers to make switching to another provider, or to your own infrastructure, possible.
After your request the deadlines are short: as a rule no more than thirty days of transition, then at least thirty days to retrieve your data. The preparatory work therefore has to be done earlier.
The regulation gives you your data back, not a working environment: rebuilding configurations, integrations and processes is still work. Have the legal side reviewed by a lawyer.
What the EU Data Act covers, and which part is about the cloud
The EU Data Act (Regulation (EU) 2023/2854) has applied since 12 September 2025. It has two halves that have little to do with each other. The first concerns data from connected products, such as machines, vehicles and smart devices, and who gets access to it. The second concerns switching between data processing services: cloud in every form, from infrastructure (IaaS) to software (SaaS).
This article is about the second half. The obligations sit with the provider of the cloud service: it has to remove obstacles that stand in the way of a switch, whether technical, contractual or commercial. You, as the customer, get rights, not new obligations.
Switching means three things in the regulation: to another provider, to your own infrastructure, or moving part of your data elsewhere while keeping the rest. If you are a UK organisation, the rules apply where you use services as a customer in the EU, for example through an EU subsidiary.
What the EU Data Act gives you as a customer
- A short notice period to start the switch: no more than two months.
- A transition period of, as a rule, no more than thirty days during which the provider cooperates. If that is technically unfeasible, it has to justify this within fourteen working days and the period may be longer, up to seven months.
- At least thirty days afterwards to retrieve your data, in a structured, commonly used and machine-readable format.
- Deletion at the end: the provider has to erase your data after the switch.
- Switching charges that disappear. Since September 2025, charges for switching, including the data egress that goes with it, may not exceed what the provider actually incurs. From 12 January 2027, according to the regulation, it may not charge for it at all.
These terms belong in the contract. A provider has to describe which data and digital assets you can take with you. So read that part, not just the price.
What the EU Data Act does not solve
The regulation removes the barrier the provider puts up. The barrier in your own environment stays, and it is usually higher.
- Data is not a working environment. For infrastructure, the provider has to help you reach an equivalent result with the new party. For software, you take your data with you, not the same screens, reports, workflows and integrations.
- Provider-specific services. The more you build on services only that one cloud offers, the more you rebuild when you switch. That is a design choice, not a contract issue.
- Custom-built services and trial versions are partly outside the rules. A service built specifically for you does not carry every obligation.
- The work itself. Migrating, testing and retraining people takes time from your own staff or a partner. That falls outside the switching charges the provider may levy.
- Existing contract terms, such as a minimum term. Whether an early termination fee is allowed in your case is a legal question.
The EU Data Act in practice: what IT should record in advance
A thirty-day transition period is short for a migration you have yet to work out. The right is only useful if you know what you are taking with you. For each cloud service, record:
- What is in it: not just files and databases, but also configurations, scripts, logs, backups, users and permissions.
- How it comes out: which export format, whether you have actually exported and restored it once, and how long that took at the current volume.
- Who holds the keys: the tenant, the admin accounts and the domain name registered to your organisation, not to a supplier.
- What it is tied to: single sign-on, DNS, mail routing, integrations with other systems. These are the threads that all have to move at once.
- Who may request it: a switching request starts the clock. Agree who does that on behalf of the organisation.
Run a test export once a year for the services that matter. An export that has never been tested is an assumption.
An exit plan per service, in this order
The regulation says how long the provider has to cooperate. It does not say how you plan your migration. An order that works:
- First the destination. Another provider, back to your own servers, or moving part of it. That determines which format and which integrations you need.
- Then the new environment. Set it up and test it with a copy of your data before you submit the request.
- Then the request. Only once the destination is ready do the deadlines start. Work the other way round and you migrate under time pressure.
- Run in parallel where you can, with a fallback point if the new environment does not do what it should.
- Close out: final export, confirmation of deletion, and revoke access for old administrators.
How we carry out such a move technically is on our page about cloud migration.
What it means for your next cloud contract
With a new contract, you can build the switch into your choice from the start. Ask a provider:
- which data and digital assets you can take with you under the contract, and in which format;
- how long the retrieval period after the switch is, and how you get confirmation that everything has been erased;
- which switching charges it still levies until 12 January 2027, and how it justifies them;
- which parts of its service only work with it, and what you lose when you leave.
That last question is the most useful, because the answer is not in the regulation but in the architecture. How a switch between suppliers works in practice, beyond the cloud too, is covered in changing IT supplier without damage.
Where our work stops
What we do. We map what a cloud service contains and what it is tied to, test exports, make sure the tenant, admin accounts and domain are registered to the client, and plan and carry out migrations, to another cloud or back to your own infrastructure. We work under ISO 9001 and ISO/IEC 27001.
What we do not do. We are not lawyers and we do not decide on behalf of a cloud provider. We do not assess contracts against the EU Data Act, we do not say whether a switching fee or a termination clause is allowed in your case, and we do not file complaints with a regulator. The deadlines and charges a provider applies are its responsibility. Have the legal side assessed by a lawyer.
Questions we get about this
The five that come up most often.
What is the EU Data Act?
The EU Data Act is a European regulation that governs who gets access to data from connected products and makes it easier to switch between cloud services. Cloud providers must remove obstacles so customers can move to another provider or to their own infrastructure.
When did the EU Data Act come into force?
The EU Data Act has applied since 12 September 2025. Since then, the rules on switching between cloud services have been in effect. According to the regulation, providers may not charge any switching fees at all from 12 January 2027.
Can my cloud provider charge me for switching?
Until 12 January 2027 it may charge switching fees, including data egress, but no more than what it actually incurs. After that, according to the regulation, it may not. The work of your own staff or a migration partner falls outside this.
Does the EU Data Act apply to SaaS?
Yes, the switching rules apply to data processing services in the broad sense, so also to software you use as a service. For software, though, you take your data with you in a usable format, not an equivalent working environment. Custom-built services are partly outside the rules.
Can you check our cloud contract against the EU Data Act?
No. We are not lawyers and we do not assess contracts against the EU Data Act. We can map which data and integrations sit in a cloud service, test an export, and plan and carry out a switch. For the legal assessment you need a lawyer.
Further reading
Where this piece connects.
Do you know what you would take with you?
Tell us which cloud services you use. For each one we map what it contains, what it is tied to and how long an export takes, so a switch is a plan rather than a leap.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.