The Data Act and the Cloud: what will change in 2027 when switching providers

Imagine that your company has been working with a Cloud provider for years. All of its infrastructure, applications, and data depend on it. One day you decide to switch to another provider because it offers better conditions, but you discover that transferring all that information turns out to be much more complicated and expensive than expected.

This situation, known as vendor lock-in or technological dependence on the provider, is one of the major challenges of Cloud Computing.

The European Union wants to change the rules of the game. With the arrival of the Data Act (European Data Act), companies will have greater ease in switching Cloud providers, recovering their data, and reducing certain economic barriers.

And there is a particularly important date: January 12, 2027.

But what actually changes? Will we be able to migrate from AWS to Azure or Google Cloud at no cost? And what happens to the applications we have already developed?

What is the Data Act and why does it affect the Cloud?

The Data Act, also known as the European Data Act, is Regulation (EU) 2023/2854, a regulation that seeks to facilitate access to and use of data and foster a more competitive digital market.

Although it covers different areas, one of its objectives is to reduce the barriers that make it difficult to switch Cloud service providers.

Until now, many organizations have encountered obstacles such as:

  • Data egress fees: charges for transferring information out of certain platforms.
  • Technological dependence: applications built on a provider’s exclusive services.
  • Restrictive contracts: conditions that make exiting difficult or expensive.
  • Interoperability issues: technologies that do not work the same way across different Cloud environments.

The Data Act introduces obligations to reduce these obstacles and make it easier for companies to switch providers, move their services to on-premise infrastructures, or, where appropriate, use multiple providers simultaneously.

The regulation began to apply generally on September 12, 2025, although some provisions have specific dates.

What exactly changes on January 12, 2027?

The most important change is related to provider switching costs, also known as switching charges.

Starting January 12, 2027, providers subject to these obligations will not be able to charge the switching fees regulated by the Data Act, except for the exceptions provided for in the regulation.

Until that date, they may apply reduced costs that do not exceed the expenses directly related to the process.

Aspect Until January 2027 From January 12, 2027
Switching charges Permitted at a reduced rate Eliminated, with exceptions
Data export Obligation to facilitate it Maintained
Switching assistance Mandatory according to the regulation Maintained without switching charges
Internal migration costs Borne by the company Still exist

Important: this does not mean that all migrations are free.

The work of adapting applications, contracting target infrastructure, or running tests will continue to generate costs. There may also be contractual penalties for early termination and permitted charges for certain simultaneous uses of services.

The difference is that the source provider will have fewer possibilities to use switching costs as a barrier to retain its customers.

What data must be recoverable when switching Cloud providers?

One of the fundamental novelties of the Data Act is that it establishes obligations regarding the portability of exportable data and certain digital assets.

Depending on the service, this may include:

  • Databases and stored information.
  • Business files and documents.
  • Input and output data generated by the services.
  • Exportable configurations and metadata.
  • Certain digital assets necessary to facilitate the switch.

However, it does not mean that the provider is obliged to hand over its proprietary software, trade secrets, or protected technologies.

For example, a company using an enterprise management SaaS must be able to recover the corresponding exportable data, but that does not imply obtaining a copy of the provider’s software to install it on another platform.

Data portability does not automatically mean application portability.

What does functional equivalence in the Cloud mean?

The Data Act also introduces the concept of functional equivalence, especially relevant in Infrastructure as a Service (IaaS) offerings.

This means that the source provider must take reasonable measures to facilitate the customer’s ability to use an equivalent service in another environment.

But there is an important nuance: functional equivalence does not guarantee that two providers offer the exact same functionalities.

For example, moving a virtual machine can be relatively simple. In contrast, migrating an application that uses proprietary databases, specific artificial intelligence tools, or exclusive platform services may require significant modifications.

Therefore, the Data Act facilitates the switch, but does not eliminate the need to plan it technically.

The big problem the Data Act does not eliminate: vendor lock-in

Eliminating switching charges is an important step forward. However, the biggest obstacle to leaving a Cloud provider is not always economic, but technological.

Imagine an application that depends on five exclusive services of a single provider. Even if you can export its data for free, you will have to find alternatives, adapt the code, and verify that everything continues to work.

Here a fundamental difference emerges:

  • Contractual dependence: difficulties derived from the conditions imposed by the provider.
  • Technological dependence: difficulties derived from how the architecture has been designed.

The Data Act helps reduce both, but it cannot guarantee that an inadequately prepared application will be automatically portable.

Therefore, the best strategy consists of designing infrastructures that allow evolving without depending completely on a single ecosystem.

How to prepare your Cloud infrastructure for the Data Act

The good news is that you don’t need to wait until January 2027 to get started.

A Cloud Exit Strategy consists of defining how to move applications, data, and services to another environment when necessary, while maintaining security and business continuity.

To prepare your architecture, it is advisable to work on four areas.

1. Identify technological dependencies

The first step is to know which services each application uses and which ones are difficult to replace.

Not all components have to be provider-independent, but it is important to know the impact of changing them.

2. Automate the infrastructure

Infrastructure as Code (IaC) tools, such as Terraform, allow defining and managing infrastructure through code.

This makes it easier to reproduce configurations and automate deployments, although it will normally be necessary to adapt certain resources to the target provider.

3. Use containers and open standards

Technologies like Docker and Kubernetes can facilitate the deployment of applications in different environments.

Similarly, using documented APIs, open formats, and interoperable technologies helps reduce unnecessary dependencies.

4. Test recovery and migration

An exit strategy should not remain just a document.

It is advisable to periodically verify that data can be exported, that applications can be recovered in another environment, and that downtime is acceptable for the business.

Checklist: Is your company ready to switch Cloud providers?

Before January 2027, review these points:

  • Contracts: do you know the exit conditions and possible penalties?
  • Data: do you know what information can be exported and in what formats?
  • Architecture: have you identified proprietary services or critical dependencies?
  • Automation: can you reproduce your infrastructure in another environment?
  • Security: have you planned how to transfer identities, permissions, and configurations?
  • Continuity: have you calculated how long the service could be interrupted?
  • Testing: have you ever verified that your exit strategy works?

If several answers are negative, it is probably a good time to review your architecture.

What should you ask your Cloud provider before 2027?

In addition to reviewing your infrastructure, it is advisable to request clear information about export procedures, available formats, switching timelines, and any known technical limitations.

The Data Act normally contemplates a maximum transitional period of 30 calendar days for the switch, once the corresponding notice period has ended, although it foresees situations in which other timeframes may be needed.

It is also worth consulting the new non-binding standard contractual clauses of the European Commission, approved on October 29, 2026, and published on November 6. These clauses serve as a reference for establishing more transparent switching and exit conditions.

The Data Act is an opportunity to build a more flexible Cloud

The arrival of January 2027 represents a step forward in freedom of choice for Cloud customers.

But the true benefit does not consist solely of reducing exit costs. It is about building a more flexible infrastructure, prepared to evolve and less conditioned by the decisions of a single provider.

Companies that review their contracts, understand their technological dependencies, and design a portability strategy will be better prepared to take advantage of this new scenario.

Prepare your Cloud architecture for the upcoming changes

Is your Cloud infrastructure ready to switch providers? At Luce IT, we help you evaluate the portability of your architecture and reduce technological dependencies through our experience in Cloud & Architecture and solutions such as SmartOps, which facilitate infrastructure automation and management. Contact our team and discover how to prepare your Cloud environment for the upcoming regulatory changes.

Frequently Asked Questions about the Data Act and Cloud

1. What is the Data Act in Cloud Computing?

It is a European Union regulation that, among other measures, establishes obligations to facilitate switching between Cloud providers, improve data portability, and reduce technical and contractual obstacles.

2. What happens on January 12, 2027, with Cloud exit costs?

From that date, provider switching charges subject to Article 29 of the Data Act are eliminated, with certain exceptions. The inherent costs of a migration, such as adapting applications or contracting new services, may still exist.

3. Does the Data Act require AWS, Azure, and Google Cloud to allow migration?

Yes, their services included within the scope of application must comply with the corresponding obligations. However, this does not guarantee that all applications can be moved without technical modifications.

4. How long does a Cloud provider have to facilitate the switch?

The Data Act normally establishes a maximum transitional period of 30 calendar days, following the notice period, with specific exceptions and mechanisms for more complex situations.

5. How to avoid vendor lock-in in a Cloud architecture?

A common strategy consists of identifying technological dependencies, using open standards where appropriate, automating the infrastructure, designing an exit strategy, and performing periodic portability tests.

 

Descargar Caso de Éxito UNED

Descargar Caso de Éxito Northgate

Luce IT
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.