The New Standard: An Exit You Can Demonstrate
The claim that cloud exit has become an engineering obligation can now be stated precisely. The EU Data Act requires providers of covered data-processing services to remove specified obstacles, expose the portable surface, support a secure and time-bounded transition, and—depending on the service model—facilitate functional equivalence or provide open interfaces and structured export. It does not make migration automatic. The final judgment is whether a customer can demonstrate an exit for the service they actually use, with its assets, constraints, costs, and evidence visible.
What the Data Act changes
Before this framework, a customer could ask for portability and still discover that the practical meaning of “portable” lived in a provider's contract, pricing model, interface design, or internal process. A provider could describe an export while leaving the customer to discover its scope during termination. A high egress charge could make a legal right to leave economically unattractive. A service could be technically downloadable but difficult to restore because the destination did not understand its data, configuration, or behaviour.
Regulation (EU) 2023/2854 changes the default relationship without declaring that clouds are interchangeable. Facilitating switching and developing interoperability standards are express subjects of the Regulation. Chapter VI applies to data and services processed by providers of data-processing services, including providers serving customers in the Union regardless of where those providers are established. Recital 78 connects the ability to move while retaining minimum functionality and avoiding downtime with competition, lower barriers to entry, and resilience. Recital 79 explains why the Regulation adds minimum obligations to earlier self-regulatory efforts: open standards and interfaces were not generally available and uptake of voluntary frameworks was limited.
That change has several connected parts. The contract must state the customer's rights and the provider's duties in a form the customer can store and reproduce. It must support the customer's exit strategy, specify the categories of data and digital assets that can be ported, identify justified exclusions, and explain assistance, continuity, retrieval, erasure, and applicable charges. The provider must disclose procedures, formats, restrictions, technical limitations, and an up-to-date register of data structures and relevant standards or open specifications. These requirements move important knowledge to a point in time when the customer can still evaluate and negotiate the relationship.
The legal clock reinforces that shift. The maximum notice period for initiating a switch is two months. After notice, the ordinary transition period is no more than 30 calendar days. If that period is technically unfeasible, the source provider must notify and justify the problem within the specified 14-working-day window after the switching request and propose an alternative of no more than seven months. The customer retains a one-time right to extend the transition period for a period they consider more appropriate. Throughout an agreed transition, continuity and a high level of security remain relevant obligations.
The process does not end when the destination receives a file. The customer must have at least 30 calendar days after the transitional period to retrieve the remaining material. Full erasure of exportable data and directly related digital assets follows successful completion and the agreed retrieval period, or a later period agreed with the provider. The order of these states matters: erasure should not destroy the only usable copy before the destination has been validated, and termination should not be mistaken for successful migration.
The charge rules address a different part of lock-in. From 11 January 2024 to 12 January 2027, reduced switching charges may not exceed the provider's directly incurred costs for the switching process. From 12 January 2027, providers may not impose switching charges for that process. The rule does not erase standard service fees or every early-termination penalty. Nor does it make all data movement free when a customer keeps two services running in parallel. For in-parallel use, providers may still pass through incurred egress costs without exceeding them, because continuous traffic is an operating feature of coexistence rather than the one-off transfer needed to leave.
This is the regulatory change in its most useful form: the provider must make the path legible and remove specified obstacles, while the customer must decide whether the destination is good enough and prove it.