Cloud providers serving customers in the European Union face a significant change to their exit policies on 12 January 2027: the EU Data Act will prohibit switching charges, including data egress charges imposed as part of moving to another provider or to an on-premises system.

With less than three months remaining as of 17 October 2026, the approaching deadline puts cloud contracts, migration budgets and customer exit procedures under renewed scrutiny. For businesses considering a move, the distinction is practical: a provider’s charge for leaving is not the same as the engineering cost of carrying out a migration.

The deadline comes from an already adopted regulation, not a new legislative announcement. The Data Act has applied generally since 12 September 2025, but its prohibition on switching charges follows a separate timetable.

What changes in January

Under Article 29 of the Data Act, providers of data processing services must stop imposing switching charges from 12 January 2027. Before that date, the regulation permits reduced switching charges, but they must not exceed the costs the provider incurs that are directly linked to the switching process.

The forthcoming prohibition goes beyond a narrowly defined cancellation administration fee. The regulation’s definition of switching charges includes data egress charges associated with the required switching process—fees for transferring a customer’s data out of the provider’s infrastructure.

That matters because the cost of extracting large datasets can influence whether a company moves workloads at all. A migration involving years of transaction records, analytics data or media archives can look attractive on a competitor’s monthly price sheet while becoming much less appealing once the exit bill is included.

The rule does not make every transfer out of a cloud service free. Its focus is switching providers or moving to an on-premises environment. Routine outbound traffic while continuing to use a service is not automatically covered by the prohibition.

Nor does the definition simply absorb every payment a customer might owe. The regulation distinguishes switching charges from standard service fees and early termination penalties. Businesses will still need to examine contract terms rather than assume that the January deadline cancels existing financial commitments.

More than a change to the invoice

The Data Act’s cloud switching requirements address contractual, commercial, technical and organisational obstacles to leaving a service. Providers must support switching through written contractual provisions, with responsibilities and procedures set out before a customer begins the move.

The framework includes a maximum notice period of two months for initiating switching and, ordinarily, a maximum transitional period of 30 calendar days after that notice period. Longer transitions are possible under specified conditions, including technical infeasibility. These are therefore not unconditional promises that any enterprise cloud estate can be relocated in a month.

Customers also need clarity on what they can take with them. The law addresses exportable data and digital assets, but this should not be read as a right to receive a provider’s entire underlying technology. Intellectual property, trade secrets and the specific service involved affect the boundaries.

The scope is broader than virtual machines alone. Data processing services can encompass infrastructure, platforms and software delivered as cloud services, although the detailed duties and exceptions vary. Businesses should assess the actual service and its contractual model rather than rely only on labels such as IaaS, PaaS or SaaS.

A cheaper exit will not make applications portable by itself

For technology teams, the most consequential distinction is between financial freedom to leave and technical ability to leave.

A virtual machine running a conventional operating system may be relatively straightforward to reproduce elsewhere. An application built around a provider’s proprietary database, event-processing tools, identity controls and deployment services can be much harder to move. Removing a transfer charge does not rewrite those dependencies.

The Data Act includes measures intended to improve interoperability and switching, but it does not require every competing service to offer identical features. Its functional-equivalence provisions for infrastructure services should not be mistaken for a universal guarantee that every application will behave identically after migration.

A customer may still have to pay engineers to convert database schemas, rebuild access policies, test backup restoration and operate two environments during a cutover. Security reviews and performance testing remain necessary. These are cloud migration costs even when the outgoing provider no longer charges a switching fee.

That leaves providers competing on more than the absence of an exit bill. The quality of export tools, documentation and migration assistance can determine whether leaving is a manageable project or a disruptive rebuild.

What businesses should check before the deadline

The immediate task for procurement and infrastructure teams is to establish which expenses are genuinely tied to switching and which arise from the broader contract or technical project. A useful review should cover:

• Exit-related charges: Identify transfer fees, extraction fees and other charges associated with switching, rather than looking only for a line item called “exit fee.”
• Remaining commitments: Separate standard service charges and possible early termination penalties from the switching charges covered by the prohibition.
• Export arrangements: Check available formats, documented interfaces and the treatment of configuration data, metadata and digital assets.
• Migration responsibilities: Establish what the outgoing provider, receiving provider and customer must each do, including how service continuity will be handled.
• Technical dependencies: Test a representative workload to identify proprietary features that require replacement or redesign.

There is also a reason to scrutinise contracts before January. The transitional regime already limits switching charges to directly related costs; it is not permission to impose unrestricted exit fees until the prohibition begins.

For providers, the approaching date means billing rules and customer-facing processes need to agree. A contractual promise of free switching will be of limited value if an automated billing system still adds transfer charges during an eligible migration.

The January deadline will remove one defined financial barrier to changing cloud services. Whether it produces more switching will depend on what remains after that barrier disappears: application dependencies, contractual commitments and the reliability of the exit process itself.

Sources: Regulation (EU) 2023/2854, particularly Chapter VI on switching between data processing services, Article 29 on switching charges and Article 50 on application dates; European Commission overview of the Data Act. This report covers the regulation’s published requirements and approaching deadline, rather than a newly announced enforcement action.