In short
From 12 January 2027, providers of data processing services may not impose any switching charges for the switching process, including data egress charges (Art. 29(1) and Art. 2(36) Data Act). Standard service fees and proportionate early termination penalties remain permissible. Custom-built services are exempt under Art. 31(1); in-parallel use is governed by Art. 34(2).
What applies from 12 January 2027: Article 29 in its own words
Article 29 of Regulation (EU) 2023/2854 is headed “Gradual withdrawal of switching charges” and sets out two phases. From 11 January 2024 to 12 January 2027, providers of data processing services may impose reduced switching charges for the switching process (paragraph 2); these must not exceed the costs incurred by the provider that are directly linked to the switching process concerned (paragraph 3). From 12 January 2027, providers “shall not impose any switching charges on the customer for the switching process” (paragraph 1; see Regulation (EU) 2023/2854, EUR-Lex). The deadline falls on a Tuesday.
The rationale is set out in Recital 88: unnecessarily high data egress charges and other unjustified charges unrelated to actual switching costs inhibit switching, restrict the free flow of data and can cause lock-in effects. Switching charges “should therefore be abolished after three years from the date of entry into force of this Regulation”. The Regulation was published in the Official Journal on 22 December 2023 and, under the first subparagraph of Article 50, entered into force on the twentieth day following publication, which works out as 11 January 2024; Article 29(2) names that date as the start of the transition period.
The deadline concerns the charge only. The other switching obligations in Chapter VI (Articles 23 to 31) have applied since 12 September 2025 under the second subparagraph of Article 50. Unlike Chapter IV, Article 50 contains no separate transitional rule for Chapter VI covering contracts concluded before that date.
From 12 January 2027 the switching process itself can no longer be charged for. What stays the same: ongoing service fees, agreed fixed terms and the technical effort of the migration.
| Period | Rule | Provision |
|---|---|---|
| 11 January 2024 to 12 January 2027 | Reduced switching charges permitted, capped at the costs directly linked to the switch | Art. 29(2) and (3) |
| since 12 September 2025 | Chapter VI applies: contract clauses, information duties, technical switching support | Art. 50, 2nd subpara. |
| from 12 January 2027 | No switching charges for the switching process | Art. 29(1) |
What counts as a switching charge – and what does not
Article 2(36) defines switching charges as “charges, other than standard service fees or early termination penalties, imposed by a provider of data processing services on a customer for the actions mandated by this Regulation for switching […], including data egress charges”. Under Article 2(35), data egress charges are data transfer fees charged to customers for extracting their data through the network from the provider’s ICT infrastructure to the system of a different provider or to on-premises ICT infrastructure.
Recital 89 draws further lines. Standard service fees for providing the services themselves are not switching charges and remain applicable until the contract ceases to apply. Fixed-term contracts, including proportionate early termination penalties, remain possible in accordance with Union or national law. Costs arising from outsourcing decided by the source provider during the switching process should not be borne by the customer. Additional services going beyond the statutory switching obligations may be charged for if the customer requests them and agrees to the price in advance.
In practice this means that from 2027 the switch itself can no longer be priced, while the contractual commitment still can. For customers, the review therefore shifts from the egress line in the price list to contract term, termination rules and the line between mandatory and additional services.
| Cost item | Treatment from 12 January 2027 | Provision |
|---|---|---|
| Data egress when switching | Switching charge, no longer permitted | Art. 2(35) and (36); Art. 29(1) |
| Fee for mandated switching actions, e.g. assistance under Art. 25(2)(a) | Switching charge, no longer permitted | Art. 2(36); Art. 29(1) |
| Ongoing service fees until the contract ends | Standard service fee, still permitted | Art. 2(36); Recital 89 |
| Proportionate early termination penalty under a fixed-term contract | Not a switching charge, still permitted | Art. 2(36); Recital 89 |
| Additional service requested by the customer beyond the switching obligations, price agreed in advance | Permitted | Recital 89 |
| Costs of outsourcing decided by the provider | Not to be borne by the customer | Recital 89 |
| Egress during in-parallel use of several services | Permitted, capped at the costs incurred | Art. 34(2) |
Who is affected and which services are exempt
Under Article 2(8), a data processing service is a digital service that enables ubiquitous and on-demand network access to a shared pool of configurable, scalable and elastic computing resources. Recital 81 assigns such services to the delivery models IaaS, PaaS and SaaS and mentions variations such as Storage as a Service and Database as a Service. Under Article 1(3)(f), the Regulation applies to providers offering such services to customers in the Union, irrespective of their place of establishment. A customer under Article 2(30) is any natural or legal person in a contractual relationship with the provider; the definition is not limited to consumers or small businesses.
Article 24 limits responsibility to the services, contracts or commercial practices provided by the original provider. Beyond that, three limitations are central when reviewing contracts:
To clarify before the deadline: if a service falls under Article 31(1), the charging ban does not apply to it – and the provider must have said so before the contract was signed.
- Custom-built services: under Article 31(1), Article 29 does not apply to data processing services of which the majority of main features has been custom-built for the specific needs of an individual customer, or where all components have been developed for that customer, and which are not offered at broad commercial scale via the provider’s service catalogue. The same applies to Article 23, point (d), and Article 30(1) and (3). The provider must inform the prospective customer before contracting which obligations do not apply (Article 31(3)).
- Test and evaluation versions: Chapter VI as a whole does not apply to services provided as a non-production version for testing and evaluation purposes and for a limited period of time (Article 31(2)).
- In-parallel use: where a service is used in parallel with another, providers may impose data egress charges, but only to pass on egress costs incurred, without exceeding them (Article 34(2)). Multi-cloud architectures with ongoing data exchange therefore fall under a cost cap rather than the zero charge of Article 29(1).
What the cloud contract must contain under Article 25
Article 25(1) requires the customer’s rights and the provider’s obligations relating to switching to be clearly set out in a written contract, which the provider makes available before signing in a way that allows the customer to store and reproduce it. Paragraph 2 sets out the minimum content; point (i) expressly requires a provision on the switching charges that may be imposed under Article 29. From 12 January 2027 this means that a clause putting a price on the switching process conflicts with Article 29(1). The minimum content at a glance:
- Switching on request to another provider or to on-premises infrastructure, without undue delay and at the latest after a mandatory maximum transitional period of 30 calendar days, during which the provider gives reasonable assistance, maintains business continuity, informs about known risks and ensures a high level of security (paragraph 2(a)).
- An obligation to support the customer’s exit strategy, including by providing all relevant information (point (b)).
- Termination of the contract on successful completion of the switch or, where the customer only wishes to erase its data, at the end of the notice period (point (c)).
- A maximum notice period for initiating the switching process of no more than two months (point (d)).
- An exhaustive specification of the categories of data and digital assets that can be ported, including at least all exportable data, plus an exhaustive list of exempted provider-internal data (points (e) and (f)).
- A data retrieval period of at least 30 calendar days after the transitional period and full erasure afterwards, provided the switch was successful (points (g) and (h)).
- Switching charges under Article 29 (point (i)) and the customer’s right to extend the transitional period once (paragraph 5).
The timeline of a switch under Article 25
Article 25 produces a timeline that belongs in every exit plan. At the end of the notice period the customer states whether it will switch to another provider, move to on-premises infrastructure or have its data erased (paragraph 3). Where the 30-day transitional period is technically unfeasible, the provider must notify the customer within 14 working days of the switching request, duly justify this and indicate an alternative transitional period of no more than seven months, during which service continuity must be ensured (paragraph 4).
One linguistic detail: the English version of paragraph 2(a) states that the transitional period is one “during which the service contract remains applicable”; the German version has no equivalent clause (see Verordnung (EU) 2023/2854, EUR-Lex DE). In contract drafting it is advisable to state expressly that service and fees continue during the transitional period.
| Phase | Duration under the Data Act | Provision |
|---|---|---|
| Notice period for initiating the switch | no more than two months | Art. 25(2)(d) |
| Mandatory transitional period | no more than 30 calendar days after the notice period | Art. 25(2)(a) |
| Notification of technical unfeasibility | within 14 working days of the switching request | Art. 25(4) |
| Alternative transitional period | no more than seven months | Art. 25(4) |
| Extension by the customer | once, for a period the customer considers more appropriate | Art. 25(5) |
| Data retrieval | at least 30 calendar days after the transitional period | Art. 25(2)(g) |
| Erasure | after the retrieval period or an agreed later period | Art. 25(2)(h) |
Information duties: what providers must disclose
Before entering into a contract, providers must give clear information on standard service fees, possible early termination penalties and the reduced switching charges of the transition period (Article 29(4)). Where relevant, they inform customers about services involving highly complex or costly switching, or for which switching is impossible without significant interference in the data, digital assets or service architecture (paragraph 5). Where applicable, both are to be published in a dedicated section of the website or in another easily accessible way (paragraph 6).
In addition, providers must give information on available switching and porting procedures, formats and known technical limitations, plus a reference to an up-to-date online register of the data structures, formats and standards of the exportable data (Article 26). On their websites, providers state the jurisdiction of the ICT infrastructure deployed and describe their measures against unlawful international governmental access to non-personal data; those websites must be listed in the contract (Article 28).
On the technical side, Article 30 distinguishes by type of service. For pure infrastructure services, providers take all reasonable measures so that the customer achieves functional equivalence after switching (paragraph 1). Other providers make open interfaces available free of charge (paragraph 2) and, as long as no common specifications or harmonised standards have been published, export all exportable data on request in a structured, commonly used and machine-readable format (paragraph 5). They are not required to develop new technologies or disclose protected digital assets (paragraph 6).
For customers, the information under Article 29(5) is the most valuable: it shows where switching remains expensive even though the switching charge disappears.
What cloud contracts need now: checkpoints for customers
The following checkpoints are derived from Articles 25, 29, 31 and 34; their order and scope are an Alev-B recommendation, not a requirement of the Regulation. The Vendor / Third-Party Assessment helps with the provider inventory, notice dates and lead times can be tracked in Renewal Readiness, and the Cloud Exit & Digital Sovereignty assessment shows how switchable your estate is in technical terms.
- Take stock: which contracts concern data processing services within the meaning of Article 2(8), which service type (IaaS, PaaS, SaaS) and which provider?
- Check price lists and contract annexes for items tied to switching: exit fees, migration flat fees, egress prices for data export on switching. From 12 January 2027 they are no longer permitted under Article 29(1).
- Clarify exemptions: did the provider state before contracting that a service falls under Article 31 (paragraph 3)? If that statement is missing, the classification belongs on the agenda of the next supplier meeting.
- Separate parallel operation: ongoing data flows between two clouds are governed by Article 34(2) (cost cap), not by the zero charge; egress costs belong in architecture and cost planning.
- Compare the mandatory clauses under Article 25: notice period of no more than two months, transition of no more than 30 calendar days, retrieval of at least 30 calendar days, exhaustive data categories, erasure commitment, extension right.
- Assess term and termination penalties: standard service fees and proportionate early termination penalties remain permissible (Article 2(36), Recital 89). Renewal dates are therefore the moment when commitment can be renegotiated.
- Price additional services in advance: services beyond the switching obligations may only be charged if the customer requests them and agrees to the price beforehand (Recital 89). The line between mandatory and additional services therefore belongs in the contract.
- Test the exit route in practice: run through formats, the online register (Article 26, point (b)) and export paths once with real data before a switch is due.
What providers need to change before the deadline
For providers of data processing services, Article 29(1) means a pricing and contract changeover on 12 January 2027: switching and egress items for the switching process fall away, contract templates under Article 25(2)(i) need to be adjusted accordingly, and the pre-contractual information under Article 29(4) loses the part on reduced switching charges. The duty to inform about particularly complex or costly switching remains (Article 29(5) and (6)).
Services going beyond the statutory obligations need an offer whose price the customer accepts before the service is performed (Recital 89). Services meant to fall under Article 31(1) require pre-contractual information under Article 31(3); the classification should be documented, because it carries the exemption from the charging ban.
As drafting support, the European Commission published the non-binding model contractual terms and standard contractual clauses for cloud computing contracts provided for in Article 41 on 19 November 2025. Three sets of clauses translate Chapter VI into contract language (Switching & Exit, Termination, Security & Business Continuity), three more cover transparency, unilateral amendments and liability; their use is voluntary, and the Commission names translation into all EU languages as the next step (see European Commission, Model Contractual Terms and Standard Contractual Clauses).
Supervision and penalties: who enforces the charging ban
Each Member State designates competent authorities (Article 37(1)). The authority responsible for Articles 23 to 31 and Articles 34 and 35 must have experience in the field of data and electronic communications services (Article 37(4)(b)); its tasks expressly include “ensuring that switching charges are withdrawn in accordance with Article 29” (Article 37(5)(i)). Penalties are laid down by the Member States and must be effective, proportionate and dissuasive (Article 40(1)). The Regulation sets no EU-wide fine ceiling for Chapter VI; Article 40(4) refers to the GDPR fining framework only for Chapters II, III and V.
In Germany, the Bundesnetzagentur is the competent authority under the Data Act Application and Enforcement Act (DADG) and operates a complaints portal (see Bundesnetzagentur, Data Act). According to its press release of 30 May 2026, it also monitors compliance with the rules on switching cloud providers (see Bundesnetzagentur, press release of 30 May 2026).
At EU level, the Commission is empowered to establish a mechanism for monitoring switching charges by delegated act (Article 29(7)). By 12 September 2028 it will evaluate the Regulation, including the diminution of switching charges (Article 49(1)(i)) and the impact of Articles 23 to 31 on pricing and the diversity of services offered (Article 49(2)).
Digital Omnibus: what the proposal would change for cloud switching
On 19 November 2025 the Commission presented its proposal for a Digital Omnibus (COM(2025) 837, procedure 2025/0360(COD)), which would among other things amend Regulation (EU) 2023/2854 (see COM(2025) 837, EUR-Lex). Article 1, point 15 of the proposal would insert two paragraphs into Article 31: for customised services other than those under Article 30(1), and for services provided by SMEs and small mid-caps, Chapter VI and Article 34 would not apply where the contract was concluded before or on 12 September 2025. The proposal would also clarify that fixed-term contracts may include proportionate early termination penalties.
For the charging ban one detail is decisive: both special regimes apply “with the exception of Article 29”, and contractual provisions contrary to Article 29(1), (2) or (3) would be “considered null and void” (Article 31(1a) and (1b) as proposed). Recital 18 of the proposal explains that the new lighter regimes should not undermine the gradual withdrawal of those charges. The proposal would therefore not move the 12 January 2027 deadline.
As of 30 October 2026, the European Parliament’s Legislative Observatory lists the procedure at the stage “Awaiting committee decision”; the latest document recorded there is a committee draft report (PE786.818) of 22 June 2026 (see Legislative Observatory, 2025/0360(COD)). No act has been adopted; the Regulation as currently in force remains authoritative.
What the deadline does not solve
The charging ban removes an invoice line, not the migration effort. The provider owes functional equivalence only for infrastructure services, and there only in the form of reasonable measures (Article 30(1)); it is not required to develop new technologies (Article 30(6)). Business logic in proprietary services, data models without a standard format and operational knowledge held by the provider remain costs for the customer. Why switchability is therefore an architecture question rather than a contract question is explored in Digital sovereignty in IT delivery.
The wording also leaves transitional cases open: Article 29 contains no specific rule for switches initiated before 12 January 2027 and completed afterwards. Anyone planning a switch in that window should agree the charging question with the provider in writing beforehand and have it legally assessed.
Deadline chain: Data Act, cloud switching and follow-up dates
The dates at a glance; further deadlines from NIS2, DORA, the CRA and the AI Act are listed in the deadline calendar, and the overview EU regulation places the frameworks in context.
| Date | Event | Provision |
|---|---|---|
| 22 December 2023 | Publication in the Official Journal (OJ L, 2023/2854) | Official Journal |
| 11 January 2024 | Entry into force; start of the reduced-charges phase | Art. 50, 1st subpara.; Art. 29(2) |
| 12 September 2025 | General date of application, including Chapter VI | Art. 50, 2nd subpara. |
| 19 November 2025 | Commission publishes standard contractual clauses for cloud contracts and the Digital Omnibus proposal | Art. 41; COM(2025) 837 |
| 30 May 2026 | Bundesnetzagentur announces it has taken over responsibility under the DADG | Bundesnetzagentur press release |
| 12 January 2027 | No more switching charges | Art. 29(1) |
| 12 September 2027 | Chapter IV (unfair contractual terms) also applies to indefinite or long-running legacy contracts | Art. 50, 6th subpara. |
| 12 September 2028 | Commission evaluation, including of switching charges | Art. 49(1) and (2) |
Sources and status
This article reflects the position as of 30 October 2026; all sources were accessed on that date. It is intended for orientation and does not replace legal advice; the text published in the Official Journal is authoritative.
Regulation (EU) 2023/2854 (Data Act), OJ L 2023/2854 of 22.12.2023, in particular Articles 1, 2, 23 to 31, 34, 37, 40, 41, 49 and 50 and Recitals 81, 88 and 89: EUR-Lex, English version and EUR-Lex, German version.
European Commission, Proposal for a Regulation (Digital Omnibus), COM(2025) 837 final of 19.11.2025, Article 1, point 15 and Recitals 17 and 18: EUR-Lex, COM(2025) 837.
European Parliament, Legislative Observatory, procedure 2025/0360(COD), procedural status 2026: Legislative Observatory.
European Commission, Model Contractual Terms and Standard Contractual Clauses for cloud computing contracts under Article 41 Data Act, published 19.11.2025: digital-strategy.ec.europa.eu.
Bundesnetzagentur, Data Act – die Europäische Datenverordnung, 2026: bundesnetzagentur.de/data-act; press release of 30.05.2026: bundesnetzagentur.de.
Key Takeaways
- From 12 January 2027, providers of data processing services may not impose switching charges for the switching process (Art. 29(1)); until then only reduced charges, capped at the costs directly linked to the switch, are permitted (paragraphs 2 and 3).
- Switching charges expressly include data egress charges; standard service fees and proportionate early termination penalties do not count (Art. 2(35) and (36), Recital 89).
- Custom-built services under Art. 31(1) are exempt; for in-parallel use of several services, egress remains permissible up to the costs incurred (Art. 34(2)).
- Since 12 September 2025 cloud contracts must contain the mandatory clauses under Art. 25: notice period of no more than two months, transition of no more than 30 calendar days, data retrieval of at least 30 calendar days.
- In Germany the Bundesnetzagentur enforces the rules under the DADG; penalties are laid down by the Member States (Art. 37, Art. 40).
- The Digital Omnibus proposal COM(2025) 837 expressly excludes Art. 29 from the planned relief and, according to the Legislative Observatory, has not been adopted (as of 30 October 2026).
Frequently Asked Questions
From that date, providers of data processing services may not impose any switching charges for the switching process (Art. 29(1) Data Act). Under Art. 2(36) this covers all charges for the switching actions mandated by the Regulation, including data egress charges. Ongoing service fees until the end of the contract are not affected.
Not for data export as part of a switch. Where two data processing services are used in parallel, Art. 34(2) allows data egress charges, but only to pass on the costs incurred and without exceeding them. Multi-cloud operation is therefore subject to a cost cap, not a zero charge.
Yes, within limits. Early termination penalties are not switching charges under Art. 2(36), and Recital 89 expressly mentions fixed-term contracts including proportionate early termination penalties as permissible. Before contracting, the provider must give information about such penalties (Art. 29(4)).
For SaaS, in principle yes: Recital 81 assigns IaaS, PaaS and SaaS to data processing services. Not covered are services whose main features have mostly been custom-built for an individual customer and which are not offered at broad commercial scale via the catalogue (Art. 31(1)). The provider must say so before the contract is concluded (Art. 31(3)).
Not under proposal COM(2025) 837. The planned relief for customised services and for SME and small mid-cap providers with legacy contracts applies expressly with the exception of Art. 29, and conflicting contract clauses would be null and void. According to the Legislative Observatory, the procedure is awaiting a committee decision (as of 30 October 2026).
The Bundesnetzagentur is the competent authority for the Data Act under the DADG and operates a complaints portal. Under Art. 37(5)(i), ensuring that switching charges are withdrawn is one of the tasks of the competent authority; penalties are laid down by the Member States under Art. 40.