Chapter VI of the EU Data Act gives cloud customers a legal right to leave their provider, caps the time and money a switch can take, and abolishes switching charges from 12 January 2027. For security and identity teams, a cloud exit is not only a contract event. Every workload identity, service account, key, secret, federation trust and audit log tied to the old provider has to be inventoried, recreated or retired inside a fixed transitional window, and the evidence has to survive the move.
This guide covers the switching rules in Articles 23 to 31 of Regulation (EU) 2023/2854, the related transparency and governmental access duties in Articles 28 and 32, and how to turn them into an exit plan. For the wider Data Act (connected product data, business to government access and unfair terms), see the EU Data Act Guide.
This page is general information, not legal advice. Status as of 17 Nov 2026. Confirm obligations against the official text of Regulation (EU) 2023/2854 on EUR-Lex and take advice for your own contracts.
Key takeaways
- The Data Act applies from 12 September 2025 (Article 50), so the Chapter VI switching duties already bind providers of data processing services offered in the EU.
- Switching rights must be written into the contract (Article 25(1)): a notice period of no more than two months, a transitional period of no more than 30 calendar days, and a data retrieval period of at least 30 days after that.
- If 30 days is technically unfeasible, the provider must say so within 14 working days and offer an alternative transitional period of no more than seven months (Article 25(4)).
- Until 12 January 2027 providers may charge reduced switching charges that do not exceed the costs directly linked to the switch; from 12 January 2027 no switching charges, including data egress charges, may be imposed (Article 29).
- Infrastructure providers must take reasonable measures to help the customer reach functional equivalence; other providers must offer open interfaces free of charge and export data in a structured, commonly used and machine-readable format (Article 30).
- The law moves data, not trust. Identities, credentials, keys and logging pipelines are the customer's own work, and they are usually what stretches an exit beyond 30 days.
Chapter VI at a glance
| Article | Topic | Core rule |
|---|---|---|
| Article 23 | Removing obstacles | Providers must not impose, and must remove, pre-commercial, commercial, technical, contractual and organisational obstacles to switching, including to terminating the contract, porting data and digital assets, achieving functional equivalence and unbundling where technically feasible. |
| Article 24 | Scope of duties | The duties in Articles 23, 25, 29, 30 and 34 attach to the services, contracts and practices of the source provider. |
| Article 25 | Contract terms | Written contract with switching clauses: two month maximum notice, 30 day maximum transitional period, exit support, exhaustive list of portable data categories, at least 30 days for retrieval, erasure after a successful switch. |
| Article 26 | Information | Providers must describe switching and porting procedures, methods, formats and known restrictions, and point to an up to date online register of data structures, formats and standards. |
| Article 27 | Good faith | All parties, including the destination provider, must cooperate in good faith so the switch is effective and the service continues. |
| Article 28 | International access transparency | Providers publish the jurisdiction of their ICT infrastructure and a description of measures against international governmental access to non-personal data. |
| Article 29 | Switching charges | Reduced, cost based charges allowed until 12 January 2027; none after that date. Charges must be disclosed before the contract is signed. |
| Article 30 | Technical aspects | Functional equivalence for infrastructure services; free open interfaces for others; compatibility with published specifications and standards; machine-readable export. |
| Article 31 | Specific regimes | Lighter rules for custom-built services not offered at broad commercial scale; non-production test and evaluation versions excluded. |
Scope: who and which services
Chapter VI applies to providers of data processing services offered to customers in the Union. The definition is broad enough to take in infrastructure, platform and software services, which is why the chapter distinguishes between infrastructure-type services (where functional equivalence is required) and everything else (where open interfaces and export formats carry the weight).
Three definitions in Article 2 shape most of the analysis:
- Switching (Article 2(34)) is the customer changing from one data processing service to another of the same service type, or to on-premises infrastructure, including by extracting, transforming and uploading data.
- Exportable data (Article 2(38)) is the input and output data, including metadata, directly or indirectly generated or cogenerated by the customer's use of the service, excluding assets or data protected by intellectual property rights or constituting trade secrets of providers or third parties.
- Digital assets (Article 2(32)) are elements in digital form, including applications, for which the customer has the right of use independently of the contract being switched from.
Article 2(35) defines data egress charges as data transfer fees charged for extracting data through the network, and Article 2(36) defines switching charges as charges, other than standard service fees or early termination penalties, imposed for the actions the Act mandates for switching, including egress charges.
Article 31 narrows the regime in two cases. Custom-built services, where most features have been developed for a specific customer and are not offered at broad commercial scale, are relieved of Article 23(d), Article 29 and Article 30(1) and (3). Non-production versions supplied for testing and evaluation for a limited time are outside the chapter. In both cases the provider must tell prospective customers which obligations do not apply.
Key obligations in the switching contract
Article 25 is where the timing lives. The contract must, at a minimum, include clauses that:
- let the customer, on request, switch or port exportable data and digital assets without undue delay and in any event within the mandatory maximum transitional period of 30 calendar days, during which the provider assists, acts with due care to maintain business continuity and maintains a high level of security (Article 25(2)(a));
- oblige the provider to support the customer's exit strategy, including by providing all relevant information (Article 25(2)(b));
- end the contract on successful completion of the switch, or at the end of the notice period where the customer only wants its data erased (Article 25(2)(c));
- set a maximum notice period for starting the switch that does not exceed two months (Article 25(2)(d));
- list exhaustively the categories of data and digital assets that can be ported, including at least all exportable data, and any internal function data excluded to protect trade secrets, provided the exclusion does not impede or delay switching (Article 25(2)(e) and (f));
- give a minimum data retrieval period of at least 30 calendar days after the transitional period ends (Article 25(2)(g));
- guarantee full erasure of exportable data and digital assets after the retrieval period, once the switch is successful (Article 25(2)(h)).
Article 25(3) lets the customer choose the destination: another provider, its own on-premises infrastructure, or simple erasure. Article 25(5) lets the customer extend the transitional period once, for a period it considers more appropriate. Where the provider cannot meet 30 days for technical reasons, Article 25(4) requires notification within 14 working days of the switching request, a justification, and an alternative period of no more than seven months, with service continuity throughout.
Egress fees and the 12 January 2027 deadline
Article 29 phases out the money barrier in two steps. From 11 January 2024 to 12 January 2027, providers may impose reduced switching charges, but those charges must not exceed the costs incurred by the provider that are directly linked to the switching process. From 12 January 2027, providers must not impose any switching charges on the customer for the switching process.
Before the contract is signed, the provider must give clear information on standard service fees, early termination penalties and any reduced switching charges (Article 29(4)). Where a switch is expected to be particularly complex or costly, the provider must also inform the customer and make that information publicly available.
Two practical points follow. First, standard service fees and early termination penalties are outside the definition of switching charges, so the commercial exit cost does not fall to zero just because egress does; read the minimum term and commitment clauses. Second, Article 34 deals separately with in-parallel use (multi-cloud), where egress charges may be passed on only to cover actual egress costs. Teams running active multi-cloud architectures should not assume the 2027 rule makes ongoing cross-cloud traffic free.
Technical aspects: functional equivalence, interfaces and formats
Article 30 splits the technical duty by service type. For services that deal with scalable and elastic computing resources limited to infrastructural elements such as servers, networks and virtual resources, the provider must take all reasonable measures in its power to help the customer achieve functional equivalence on a destination service of the same type (Article 30(1)). Functional equivalence (Article 2(37)) means re-establishing, on the basis of the customer's exportable data and digital assets, a minimum level of functionality in the new environment.
Other providers must make open interfaces available to an equal extent to all customers and destination providers, free of charge, to facilitate switching (Article 30(2)). Once common specifications or harmonised standards are published in the Union repository, providers must ensure compatibility with them within 12 months (Article 30(3)). Where none exist, the provider must export all exportable data in a structured, commonly used and machine-readable format at the customer's request (Article 30(5)).
Article 30(6) sets the limit: providers are not required to develop new technologies or services, disclose protected intellectual property or trade secrets, or compromise the security and integrity of the service. That last clause matters for identity teams. A provider will not export private keys from a hardware security module or reveal internal signing material, and the law does not ask it to.
Transparency on governmental access (Articles 28 and 32)
Article 28 requires providers to publish, and keep up to date, the jurisdiction to which the ICT infrastructure for each service is subject, and a general description of the technical, organisational and contractual measures adopted to prevent international governmental access to or transfer of non-personal data held in the Union where that would conflict with Union or national law. The websites carrying this information must be listed in contracts.
Article 32 requires those measures to exist. A third-country court judgment or administrative decision requiring access to non-personal data is recognised or enforceable only on the basis of an international agreement such as a mutual legal assistance treaty, or under the conditions in Article 32(3). Providers must disclose only the minimum data permissible and inform the customer before complying, unless the request serves law enforcement purposes and secrecy is needed. These disclosures feed directly into sovereignty and data residency assessments, and should be captured during vendor due diligence rather than at exit.
Enforcement and penalties
Article 37 requires each Member State to designate one or more competent authorities, with a data coordinator where there is more than one. Authorities responsible for Articles 23 to 31, 34 and 35 must have experience in data and electronic communications services. Data protection authorities remain responsible for personal data. Providers established outside the Union that offer services in it must appoint a legal representative in a Member State.
Article 40 leaves penalties to Member States: they must be effective, proportionate and dissuasive, and Member States had to notify their rules to the Commission by 12 September 2025. The size of fines for Chapter VI breaches therefore depends on national law; check the implementing legislation in each Member State where you buy services.
Timeline and current status
| Date | Event | Source |
|---|---|---|
| 11 January 2024 | Start of the reduced switching charges period | Article 29(2) |
| 12 September 2025 | Regulation applies, including Chapter VI; national penalty rules due | Articles 40 and 50 |
| 12 September 2026 | Article 3(1) product design duty applies to new connected products | Article 50 |
| 12 January 2027 | No switching charges, including egress charges, may be imposed | Article 29(1) |
| 12 September 2027 | Chapter IV unfair terms rules reach certain long running contracts concluded before 12 September 2025 | Article 50 |
As of 17 November 2026, the switching duties are in force and the reduced charges window has under two months to run.
What it means for security and identity teams
A provider can export databases and object stores within 30 days. What it cannot export is the trust fabric around them. In a typical cloud estate the following are bound to the source provider and must be rebuilt by the customer:
- Workload identities and service accounts. Roles, managed identities and service principals do not port. Each must be mapped to an equivalent on the destination, with least privilege re-derived rather than copied. See the Service Account Security Guide.
- Keys and secrets. Provider managed keys and HSM backed keys usually cannot leave the provider, which Article 30(6) accepts. Plan re-encryption under new keys, rotate every secret that was ever readable in the source environment, and revoke the old ones after cutover. See the Secrets Management Guide.
- Federation and CI/CD trust. OIDC trust policies from source control and deployment pipelines point at the old provider's token service. They need replacing and the old trust deleting, or a forgotten pipeline keeps deploy rights into an environment nobody watches.
- Audit logs and evidence. Logs are exportable data, but only for the retrieval window. Legal holds, DORA, NIS2 or sector retention rules may require years. Export logs to storage you control before the retrieval period ends; erasure under Article 25(2)(h) is final.
- AI agents and automation. Agents, bots and scheduled jobs hold tokens for the source APIs. Inventory them and re-issue credentials scoped to the destination, or they fail open or silently stop.
The 30 day transitional period is therefore realistic only when the identity and credential migration is planned before notice is served. The notice period (up to two months) is the time to prepare, not to start discovering.
Compliance and exit planning steps
- Review contracts. Check every cloud contract for the Article 25 clauses, the switching charges disclosure under Article 29(4), and the Article 28 transparency links. Flag missing clauses to procurement.
- Classify services. Mark which services are infrastructure-type (functional equivalence) and which are platform or software (open interfaces and export formats), and whether any fall under Article 31.
- Build an exit inventory. List exportable data, digital assets, identities, keys, secrets, certificates, DNS, network trust and log sinks per service.
- Write an exit runbook. Sequence notice, transitional and retrieval periods against identity re-creation, key rotation, log export and decommissioning, with named owners.
- Test it. Run a partial switch or restore to the destination for one workload to prove the 30 day plan, and record the result as evidence for DORA or NIS2 exit strategy requirements where they apply.
- Close down. After cutover, revoke all source credentials, delete federation trusts, confirm erasure in writing, and keep the evidence.
Common failure patterns
- Treating "zero egress from 2027" as zero exit cost, while minimum commitments and early termination penalties remain.
- Serving notice before identities and keys are mapped, then requesting the seven month extension the provider never needed.
- Letting the retrieval period lapse before audit logs are copied, losing evidence that regulators or courts later ask for.
- Copying source IAM policies one for one, carrying over years of excess privilege.
- Leaving CI/CD OIDC trusts and long lived access keys active in the source account after cutover.
- Missing that Article 34 in-parallel egress pass-through still applies to multi-cloud traffic.
Practitioner checklist
- Every in-scope cloud contract contains the Article 25 notice, transitional, retrieval and erasure clauses.
- Switching charges disclosed under Article 29(4) are recorded, and invoices after 12 January 2027 are checked for switching or egress charges.
- Article 28 jurisdiction and governmental access statements are captured in vendor risk records.
- An exit inventory lists all non-human identities, keys, secrets and certificates per service.
- Log export to customer controlled storage is scheduled inside the retrieval period.
- Source credentials and federation trusts are revoked and their revocation is evidenced after cutover.
- Written confirmation of erasure under Article 25(2)(h) is obtained and filed.
- The exit runbook has been tested on at least one workload in the last 12 months.
Standards and references
- EUR-Lex: Regulation (EU) 2023/2854 (Data Act), official text
- EUR-Lex: Regulation (EU) 2016/679 (GDPR)
- EUR-Lex: Regulation (EU) 2022/2554 (DORA)
- EUR-Lex: Directive (EU) 2022/2555 (NIS2)
- NIST: SP 800-53 Rev. 5 (SA-9 External System Services)
- ISO: ISO/IEC 27001:2022 Information security management systems
Related NHI Mgmt Group resources: EU Data Act Guide · DORA Guide · Secrets Management Guide · Cloud Security Guide