From January 12, 2027, Cloud providers serving EU customers can no longer charge them for switching to a competitor or bringing workloads back in-house. That includes SaaS, not just infrastructure. Vendors that treat portability and exit as product features will turn a compliance deadline into a sales argument. Vendors that treat it as a legal footnote are in for an awkward quarter.
The Eagles sang about a hotel you could check out of but never actually leave. For years, plenty of Cloud contracts worked the same way. Leaving was technically allowed, but egress fees, proprietary formats, and long notice periods made it painful enough that most customers stayed put.
The EU Data Act is Brussels walking into that lobby, unlocking the exits, and taping a sign to the door: no checkout fee.
The deadline, and why SaaS is in scope
The Data Act, Regulation (EU) 2023/2854, has applied since September 12, 2025. Its Chapter VI deals with switching between “data processing services,” a deliberately broad term. As legal practice Osborne Clarke summarizes, it covers infrastructure, platform, and software as a service, in both Cloud and Edge settings.
That breadth surprises many SaaS founders. The public debate around Cloud lock-in has focused on hyperscalers and egress fees for infrastructure. But a CRM, an accounting platform, or an HR suite sold to EU business customers is just as much in scope.
The charging timeline is staged:
| Period | What providers may charge for switching |
| Until January 11, 2027 | Reduced charges, capped at the provider’s direct costs of the switching process |
| From January 12, 2027 | Nothing. Switching charges, including data egress charges linked to switching, are banned |
What the switching chapter requires
Beyond charges, Chapter VI sets out a set of contractual and technical obligations. In broad terms, a provider must:
• Offer a short notice period: Customers must be able to initiate a switch with a maximum notice period of two months.
• Complete the switch promptly: The default transition period is a maximum of 30 calendar days, extendable only where the provider can show that it is technically unfeasible.
• Let customers take their data: Contracts must specify the “exportable data” and digital assets that can be ported, including relevant metadata, and give customers at least 30 days to retrieve them after the transition.
• Erase properly: Once the switch is complete, the provider must delete the customer’s data, subject to its legal obligations.
• Be transparent: Contracts must describe the switching process, the available data formats, and any known risks to continuity.
• Support functional equivalence for infrastructure: For IaaS, providers must take reasonable measures to help customers achieve functional equivalence on the destination service. For SaaS and PaaS, the focus is on open interfaces and exporting data in structured, commonly used, machine-readable formats.
There are limited carve-outs, notably for services where the majority of main features have been custom-built for an individual customer, and for test or beta services. As Travers Smith points out, even custom-built services remain subject to most of the mandatory contract requirements.
A moving target: In November 2025, the Commission’s Digital Omnibus package proposed softening the switching rules: exempting custom-made services other than IaaS for contracts concluded before September 12, 2025, as well as introducing a lighter regime for non-IaaS services offered by SMEs and small mid-caps. As of mid-2026, those amendments were still a proposal working through the legislative process. Plan for the law as it stands, and keep an eye out for changes.
Contract and product implications
Compliance with Chapter VI is half legal drafting and half product engineering.
Contracts: Standard terms need explicit switching and exit clauses: notice periods, transition timelines, a list of exportable data, data formats, erasure commitments, and pricing that does not include switching charges after the deadline. The Commission has supported this work with a set of standard and model contractual clauses for Cloud contracts, which Maples describes as modular clauses on switching, exit, termination, security, and continuity. Its Data Act FAQs are the other essential reference.
Export tooling: Most SaaS products already offer some form of export. The question is whether it covers everything a customer needs to actually move: configuration, workflows, attachments, audit logs, and metadata, not just a CSV of records. A self-service export that a customer can run without opening a support ticket is the gold standard.
Interoperability: Documented APIs, open formats, and import tools for common competitors’ formats all reduce friction. The Data Act also points toward open interoperability specifications and harmonized standards, which will become a reference point once they mature.
Pricing: Any revenue line that depends on switching fees or exit-related professional services needs a rethink. Charging for genuinely separate services, such as a bespoke migration project the customer chooses to buy, remains a different matter; but the line should be drawn carefully and documented.
The opportunity: portability as a trust signal
Here is the counterintuitive part. Making it easier for customers to leave can make them more willing to sign. Call it the Sting school of procurement: set them free, and they are more likely to come back with a three-year renewal.
Enterprise procurement teams have been burned by lock-in. A vendor that can demonstrate a clean, fast, documented exit path removes one of the biggest objections in a long sales cycle. “You can leave in 30 days with all your data” is a powerful line in a proposal, especially when competitors are still hedging.
For European providers, the timing is especially good. Sovereignty is climbing the boardroom agenda, as our analysis of Europe’s sovereign Cloud geopatriation showed, and the proposed Cloud and AI Development Act would make sovereignty criteria part of public procurement. When switching costs fall, customers who want to move toward European providers face fewer barriers. Vendors positioned as the destination stand to gain.
The MSP angle: who manages the move?
Switching rights do not migrate data by themselves. Somebody still has to plan the move, map data between systems, test integrations, retrain users, and run old and new platforms in parallel.
That somebody is often an MSP, playing Cat’s Cradle with a migration plan instead of a ball of yarn. As switching becomes cheaper and more common, migration and exit planning can become a repeatable managed service: assessing portability before a customer signs, maintaining exit plans as part of governance, and executing migrations when the time comes. MSPs that build migration playbooks for the most common SaaS categories will be ready when demand arrives.
What to do now: a readiness checklist
1. Confirm which of your services count as data processing services under the Data Act, and whether any carve-outs genuinely apply.
2. Review standard contracts for notice periods, transition timelines, exportable data definitions, and erasure terms.
3. Remove switching and switching-related egress charges from price lists effective January 12, 2027.
4. Audit your export tooling: can a customer extract all exportable data and digital assets in a structured, machine-readable format without your help?
5. Document APIs and data formats publicly.
6. Write and publish an exit process customers can read before they sign.
7. Train sales teams to present portability as a feature.
8. Track the Digital Omnibus negotiations and Commission guidance for changes to the rules.
Portability, sovereignty, and the future of European Cloud will all be on the agenda at CloudFest Global, March 15–18, 2027. Registration is now open.
DISCLAIMER: This article is for general information only and does not constitute legal advice. Obligations depend on the specific service, contract, and jurisdiction. Always consult qualified counsel for advice on your situation.
