- Chapter VI switching obligations (Articles 23-31), including contract requirements (Article 25), online register (Article 26), jurisdiction transparency (Article 28), switching charges (Article 29), and technical aspects (Article 30).
EU Data Act: Fair Access to Connected Product Data and Cloud Switching Cloud Switching Compliance Checklist
A procurement- and audit ready checklist for Chapter VI switching obligations.
Use it as a vendor due diligence list (customer) or an implementation checklist (provider).
Structured answer sets in this page tree.
Cited legal and guidance references.
EU Data Act Chapter VI requires providers of data processing services to remove switching obstacles and make portability real. This checklist translates Articles 23-30 into concrete controls and evidence. If you're a customer, use it to validate vendors before renewal. If you're a provider, use it to build an audit ready switching posture and to avoid "we support exports" claims that don't survive scrutiny.
A) Contract checklist (Article 25) - must-have clauses and numbers
Start with contracts. If the contract doesn't contain the required rights and obligations, switching becomes a discretionary support request instead of a guaranteed process.
Maintain a clause matrix per service type and publish a customer-facing summary aligned to the contract.
- Switching right: to another provider (same service type) or to on-prem, without undue delay
- Maximum notice period: <= 2 months to initiate the switching process
- Transitional period: mandatory maximum of 30 calendar days (with a limited technical unfeasibility exception)
- Retrieval period: minimum of 30 calendar days after termination
- Assistance + continuity: reasonable assistance, continuity, and security maintained throughout switching
- Exit strategy support: explicit obligation to support the customer's exit strategy with relevant information
- Portability scope: exhaustive list of exportable data + digital assets (per service), including formats and tooling
- Exemptions: internal-functioning data exemptions justified by trade secret risk and must not impede switching
- If 30 days is technically unfeasible: provider notifies within 14 working days and proposes an alternative period <= 7 months
Turn EU Data Act: Fair Access to Connected Product Data and Cloud Switching Cloud Switching Compliance Checklist into an operational assessment
Assessment Autopilot can take EU Data Act: Fair Access to Connected Product Data and Cloud Switching Cloud Switching Compliance Checklist from turning this checklist into an operational workflow to a reusable workflow inside Sorena. Teams working on EU Data Act: Fair Access to Connected Product Data and Cloud Switching can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from EU Data Act: Fair Access to Connected Product Data and Cloud Switching Cloud Switching Compliance Checklist and turn the guidance into owned tasks, evidence requests, and review checkpoints.
Review your current process, evidence gaps, and next steps for EU Data Act: Fair Access to Connected Product Data and Cloud Switching Cloud Switching Compliance Checklist.
B) Process checklist (Articles 23 + 27) - switching workflow and cooperation
A compliant switching posture requires a real workflow: owners, SLAs, and a runbook. Article 27 explicitly requires parties to cooperate in good faith to make switching effective and timely.
Procurement will ask for proof. Build a switching rehearsal program and keep artifacts.
- Published switching procedure: intake, verification, scoping, execution, escalation, and closure
- Operational SLAs: acknowledgement, dataset export, interface availability, cutover support, and closure
- Runbook: security controls, integrity validation, and rollback plan
- Evidence: switching drill report per service type (date, scope, duration, issues, remediation)
C) Article 26 online register - exportable data transparency you can't fake
Article 26 requires an up-to-date online register with the data structures and formats (and relevant standards/open interoperability specifications) used for exportable data.
Treat this as a customer-facing exportability specification and keep a change log.
- Register content: schemas/data structures, formats, and relevant standards/open specs for exportable data
- Accessibility: publicly accessible or easily accessible to customers; referenced in contracts
- Limitations: restrictions and technical limitations documented and kept up to date
- Evidence: snapshots and change history (versioning)
D) Article 28 international access transparency - website disclosures
Providers must publish jurisdiction information and a general description of measures designed to prevent conflicting international governmental access to or transfer of non-personal data held in the Union.
Operationally: keep a dedicated web page per service and reference it in contracts.
- Per-service jurisdiction disclosure for the ICT infrastructure used for data processing
- Measures description (technical/organisational/contractual) published and kept up to date
- Contracts list the website(s) containing Article 28 info
- Evidence: review cadence, approvals, and change log
E) Article 29 switching charges - pricing and billing controls
Switching charges have a hard phase-out: from 12 January 2027, switching charges are prohibited. In the interim period, reduced charges are allowed only if they are cost-based.
Implement billing controls so invoices don't accidentally reintroduce prohibited switching charges.
- Reduced charges only 11 Jan 2024-12 Jan 2027; capped at costs directly linked to switching
- No switching charges from 12 Jan 2027
- Pre-contract disclosure: standard fees, early termination penalties, and reduced switching charges (if any)
- Evidence: price list history and invoice sampling
F) Article 30 technical portability - open interfaces and formats
Article 30 requires open interfaces (free of charge) for portability and interoperability, and compatibility with common specifications or harmonised standards once published in the central repository (with a compliance window after publication).
If standards/specs aren't available yet for a service type, exportable data must still be exportable in structured, commonly used, machine-readable formats on request.
- Open interfaces available to customers and destination providers free of charge (where applicable)
- Documentation sufficient to develop software to communicate with the service for portability/interoperability
- Compatibility plan with common specs/harmonised standards after publication in the central repository
- Fallback export formats when no common specs exist (structured, commonly used, machine-readable)
- Evidence: API specs, interface docs, export samples, and conformance test results
Evidence pack - what procurement and auditors will ask for
Treat Chapter VI as both compliance and sales. Most enterprise buyers will request proof: contract language, registers, drill outcomes, and public disclosures.
Keep a standard evidence pack per service type and keep it current.
- Article 25 clause matrix (per service) + contract excerpts
- Switching runbook + drill reports per service type
- Online register URL + snapshots + change log (Article 26)
- Jurisdiction + measures disclosure pages + change log (Article 28)
- Billing controls evidence + invoice sampling for switching charges (Article 29)