EU Data Act - Cloud Switching Charges Abolished (12 Jan 2027)

From 12 January 2027 data-processing service providers may no longer charge switching fees; contracts must allow exit within 30 days and support functional equivalence for like-for-like services.

JurisdictionEuropean Union
CategoryPrivacy & Data Protection
StatusUpcoming
Effective date
Latest development

Analysis

From 12 January 2027, the EU Data Act (Regulation (EU) 2023/2854) abolishes switching charges for data processing services, requires contractual rights to switch within a limited notice and transition period, and obliges providers—especially Infrastructure-as-a-Service (IaaS)—to support functional equivalence when customers move to like-for-like services.Data Act – EUR‑Lex Official Journal PDF Data Act – European Commission summary

Below is a structured, compliance-focused analysis tailored to your description (no switching charges from 12 Jan 2027, exit within 30 days, functional equivalence), aligned with the official text and Commission explanations.

Key Requirements

1. Abolition of Switching Charges (including data egress)

2. Contractual Switching Right, Notice Period and Exit/Transition Window

  • Customers must have a contractual right to switch to another provider or move to on‑premises, without undue delay and within a specified maximum notice and transition period.
  • Commentaries on Article 28–30 of the Data Act explain that contracts must allow customers to switch to another data processing service provider or port exportable data and digital assets to on‑premises IT, “without undue delay and within a maximum transitional period of 30 days” following a notice period not exceeding two months.Alston & Bird – Switching Requirements Digital Chiefs – Switching Duties
  • Implementation guides describe that customers may trigger a switch with a maximum of two months’ notice, and providers must complete the transition within a maximum of 30 days from the end of that notice, unless they demonstrate technical infeasibility.Stepto – EU Data Act Cloud Switching

3. Functional Equivalence for Like‑for‑Like Services (especially IaaS)

  • IaaS providers must support “functional equivalence” when a customer switches to a service of the same type.
  • The Commission explainer states that providers of Infrastructure as a Service must take measures to facilitate that, where a customer switches to a service of the same type, the customer gets materially comparable outcomes in response to the same input for features that both services share (“functional equivalence”).Data Act explained – European Commission
  • Legal summaries define functional equivalence as ensuring a minimum level of functionality after switching in the new environment, so that the destination service delivers materially comparable outcomes to the same input, for overlapping features.EY Law – New provisions for cloud switching Digital Chiefs – Switching Duties
  • Technical commentary clarifies that IaaS providers must take all reasonable measures to help customers achieve functional equivalence on the destination service for like‑for‑like offerings.Stepto – EU Data Act Cloud Switching

4. Timing and Applicability

  • Legacy contracts and long‑term agreements.
  • The Official Journal text indicates that Chapter IV (which includes certain contractual fairness and switching obligations) applies from 12 September 2027 to contracts concluded on or before 12 September 2025, where they are of indefinite duration or expire at least ten years from 11 January 2024.Official Journal PDF – Regulation (EU) 2023/2854
  • Commentary notes that legacy B2B contracts must be cleared of unfair terms and aligned with switching rules by 12 September 2027 for qualifying long‑term contracts.Datargo – End of Switching Fees

Compliance Challenges

1. Technical Complexity of Achieving Functional Equivalence

  • Challenge: Designing architectures and deployment models that allow functional equivalence across different cloud providers or environments.
  • Analyses highlight that achieving materially comparable outcomes across heterogeneous IaaS environments requires standardised deployment practices, containerisation, and interoperability tooling.Data Act explained – European Commission Digital Chiefs – Switching Duties
  • Technical guides note that providers need “exit engineering”—scripts, images, and configuration export pipelines—to meet the functional equivalence duty.Stepto – EU Data Act Cloud Switching
  • Example: Multi‑cloud migration projects often encounter incompatibilities in networking, IAM, and storage services, making “like‑for‑like” behaviour difficult to guarantee.
  • Industry reports on cloud portability describe significant re‑engineering when moving workloads between hyperscalers due to proprietary services and differing APIs.Alston & Bird – Switching Requirements EY Law – New provisions for cloud switching

2. Contract Remediation and Elimination of Switching/Egress Fees

  • Challenge: Revising existing contracts and pricing models that rely heavily on egress or switching fees.
  • Analyses show many EU‑facing cloud providers have historically used egress fees and early termination penalties as lock‑in mechanisms, which now must be removed or substantially reduced.Alston & Bird – Switching Requirements Datargo – End of Switching Fees
  • Commentary notes that Europe’s switching rules are “rewriting cloud contracts before they take effect”, as providers restructure revenue models away from egress fees.The Debate – Europe’s Switching Rules

3. Operational Readiness for 30‑Day Exit Window

  • Challenge: Operationalising a maximum 30‑day transition period after notice, including data transfer, workload migration, testing, and cut‑over.
  • Legal guidance stresses that providers must complete switching within 30 days (subject to narrow technical infeasibility exceptions), requiring robust exit processes.Alston & Bird – Switching Requirements Stepto – EU Data Act Cloud Switching
  • Commentaries warn that large enterprise migrations may not fit comfortably in 30 days without pre‑planned exit pathways and pre‑exported data.Digital Chiefs – Switching Duties

4. Governance and Compliance Alignment Across Jurisdictions

Implementation Best Practices

1. Contract and Policy Review

2. “Exit Engineering” and Technical Tooling

3. Governance, Risk and Compliance (GRC) Integration

4. Customer Communication and Transparency

  • Action: Clearly communicate switching rights and conditions in customer‑facing materials.
  • The Data Act emphasises transparency and fairness in contractual terms and switching arrangements.[Regulation (EU) 2023/

Recent developments

  • — Analysis of how Article 29 of the EU Data Act is already reshaping cloud contracts ahead of the **12 January 2027** ban on cloud switching and egress charges, including examples of providers pre‑emptively waiving exit fees and renegotiating pricing and term structures.[7] (source)
  • — News update highlighting the countdown to **12 January 2027**, stressing that cloud switching charges for moves between data processing services must be fully withdrawn by that date and outlining key compliance steps for privacy and data protection teams.[14] (source)
  • — Overview for CIOs and portfolio managers explaining that the core obligations of Regulation (EU) 2023/2854 took effect on **12 September 2025**, with switching and data‑egress fees to be completely abolished from **12 January 2027**, and describing practical contract and governance changes.[9] (source)
  • — Industry research report on EU cloud switching and exit readiness, detailing the transitional regime for cost‑covering switching charges up to **12 January 2027** and the complete abolition of switching and related data‑egress fees for covered switching processes from that date, plus readiness benchmarks across major providers.[13] (source)
  • — Article on cloud portability becoming mandatory under the EU Data Act, emphasizing that switching and egress fees end on **12 January 2027**, outlining the interim cap to direct costs only, and assessing operational and legal impacts on cloud architectures and customer migration planning.[3] (source)
  • — Blog analysis of the EU Data Act’s cloud‑switching mandate, explaining the shift from cost‑based switching fees until **12 January 2027** to a total prohibition thereafter, and exploring consequences for PaaS lock‑in, multi‑cloud strategies, and negotiation dynamics between enterprises and providers.[4] (source)
  • — Guidance piece for CIOs on preparing for the abolition of cloud switching and egress fees from **12 January 2027**, with practical recommendations on revising exit strategies, re‑evaluating hyperscaler contracts, and leveraging the new regime for data portability and vendor diversification.[1] (source)
  • — Industry blog describing how, from January 2027, the EU Data Act imposes a maximum two‑month termination notice and abolishes switching fees, turning traditional cloud lock‑in into a liability and prompting providers to redesign offerings and customers to plan strategic exits and re‑hosting paths.[6] (source)
  • — FAQ on Data Act cloud switching fees and deadlines clarifying that only reduced, cost‑linked switching charges are allowed until **12 January 2027**, when all switching and data‑egress charges for the switching process are prohibited, and distinguishing these from ongoing service or early‑termination fees that can still apply.[8] (source)
  • — Policy and architecture briefing explaining phased applicability of the EU Data Act, including the **complete elimination of cloud switching and egress charges from 12 January 2027**, and advising software and cloud providers on design and contract decisions to comply while maintaining sustainable business models.[5] (source)

Related regulations

Put it into practice

Browse all regulations · Compliance deadlines · Latest updates