ChecklistEUData Act

EU Data Act Cloud Switching Compliance Checklist

Check whether a cloud or contract, product page, export route, support process, and evidence pack meet the Data Act switching rules for providers.

Based on Regulation (EU) 2023/2854 and Commission implementation materials. Use it to structure review evidence, not for legal interpretation.

Author
Sorena AI
Published
May 6, 2026
Updated
Jul 24, 2026
Overview

This checklist helps providers of data processing services review Data Act cloud switching readiness. Chapter VI can cover IaaS, PaaS, and SaaS when the offering meets the Article 2(8) definition; a customer merely using a cloud-enabled feature is not necessarily buying a . Review each service separately because infrastructure-only services, other commercial services, qualifying custom-built services, and limited-period non-production testing services do not follow identical rules. The checklist covers switching obstacles, written clauses, customer information, cooperation, charges, technical switching, exceptions, and interoperability evidence.

Section 1

1. Confirm the service is a covered data processing service

Start by naming the source service, service type, customer segment, contract template, regions, and whether the service is offered through a broad commercial catalogue. The Data Act switching rules apply to providers of data processing services, but Article 31 removes only Article 23(d), Article 29, and Article 30(1) and (3) for qualifying custom-built services. It excludes all Chapter VI duties for a non-production testing or evaluation service provided for a limited period.

Record the conclusion before running the rest of the checklist. A provider should not apply the same pass/fail result to infrastructure-only services, software or application services, custom-built services, and temporary test environments without explaining which Article 30 or Article 31 route applies.

  • Identify the service type and whether the customer may switch to another provider, on-premises ICT infrastructure, or parallel use of several providers.
  • Flag infrastructure-only services separately because Article 30(1) uses the route for scalable and elastic computing resources limited to infrastructural elements.
  • For other data processing services, test the open-interface and standards route under Article 30(2) to 30(5).
  • If relying on Article 31, keep the pre-contract notice that identifies the duties that do not apply and the evidence that the service meets every condition for the custom-built or limited-period non-production route.
Section 2

2. Review mandatory switching clauses before contract signature

Article 25 requires the customer rights and provider obligations for switching to be clearly set out in a written contract made available before signature in a storable and reproducible form. The checklist should therefore review the contract text, not only a policy page or support article.

The contract should let the customer request switching to another provider or porting to on-premises ICT infrastructure without undue delay and within the mandatory maximum transitional period, while preserving business continuity, security, and support during the switch.

  • Written contract available before signature in a form the customer can store and reproduce.
  • Customer right to switch provider or port and digital assets to on-premises ICT infrastructure.
  • Maximum notice period for starting the switching process does not exceed two months.
  • Mandatory maximum transitional period of 30 calendar days after the notice period, unless Article 25(4) technical unfeasibility is properly notified and justified.
  • Provider duties during the transitional period: reasonable assistance, due care for business continuity, clear known-continuity-risk information, and high security during transfer and retrieval.
  • Exit-strategy support obligation, termination trigger, retrieval period of at least 30 calendar days, erasure clause after retrieval or later agreed period, and any Article 29 .
Recommended next step

Turn the checklist into a switching evidence pack

Use the checklist to review cloud contract clauses, public switching information, export tests, charges, interface documentation, and remediation evidence with source citations attached.

Section 3

3. Test customer notices and switching choices

The customer must be able to notify the provider what it wants to do at the end of the maximum notice period: switch to another provider, switch to on-premises ICT infrastructure, or erase and digital assets. The operational process should collect enough destination details to act on that notice without making the customer re-negotiate the right.

If the 30 calendar day transitional period is technically unfeasible, the provider must notify the customer within 14 working days of the switching request, justify the technical unfeasibility, and indicate an alternative transitional period that does not exceed seven months. Service continuity still needs to be maintained through that alternative period.

  • Switching intake form captures customer identity, contract, requested action, destination provider or on-premises target, requested start date, and authorised third parties.
  • Support runbook separates ordinary switching from Article 25(4) technical-unfeasibility cases.
  • Technical-unfeasibility notice includes the reason, the alternative transitional period, and continuity arrangements.
  • Customer can extend the transitional period once for a period the customer considers more appropriate for its own purposes.
Section 4

4. Publish switching information and the online register

Article 26 requires providers to give customers information on available procedures for switching and porting, including methods, formats, restrictions, and known technical limitations. It also requires a reference to an up-to-date provider-hosted online register for data structures, data formats, relevant standards, and open interoperability specifications for .

Article 28 adds public website transparency for the jurisdiction of ICT infrastructure used for individual services and for measures that prevent international governmental access to or transfer of non-personal data held in the Union where such access or transfer would conflict with Union or Member State law. Contracts for data processing services must list those websites.

  • Customer-facing switching page describes available switching and porting methods, formats, restrictions, and known technical limitations.
  • Online register lists structures, data formats, relevant standards, and open interoperability specifications for the service.
  • Contracts link to the Article 28 website pages for infrastructure jurisdiction and international governmental access or transfer safeguards.
  • Evidence includes dated screenshots or archived versions of the switching page, online register, and Article 28 transparency pages.
Section 5

5. Verify exportable data, formats, and excluded internal data

The contract must exhaustively specify all categories of data and digital assets that can be ported during the switching process, including at least all . It must also specify categories of provider-internal data excluded from exportable data where a trade-secret risk exists, but those exemptions must not impede or delay the switching process.

Where same-service-type interoperability standards or common specifications have not yet been published in the central Union standards repository, Article 30(5) requires export of all , at the customer's request, in a structured, commonly used, and machine-readable format.

  • Checklist names each category, digital asset category, schema, format, metadata set, API or bulk-export route, retention limit, and validation method.
  • Excluded internal-functioning data categories are specific, tied to trade-secret risk, and checked so they do not block or delay switching.
  • Export test proves the customer can retrieve the listed data and digital assets using the documented route.
  • When no applicable Article 30(3) standard or common specification is available, export evidence shows a structured, commonly used, machine-readable format.
Section 6

6. Check switching charges, service fees, and public pricing disclosures

Article 29 allowed reduced from 11 January 2024 through 11 January 2027 and capped them at costs directly linked to the switching process. Because the Regulation generally applies from 12 September 2025, providers implementing the rule before the ban begins must apply that cap. From 12 January 2027, providers must not impose switching charges on the customer for the switching process.

Before entering into a contract, providers must give prospective customers clear information on standard service fees, early termination penalties, and reduced that might be imposed during the phase-out period. Where relevant, providers must also inform customers about services with highly complex or costly switching or switching that is impossible without significant interference in data, digital assets, or service architecture.

  • Pricing page and order forms distinguish standard service fees, early termination penalties, , and any data egress charges for parallel use.
  • Reduced switching-charge calculations are limited to costs directly linked to the switching process during the phase-out period.
  • No switching-charge clause or invoice line remains for customer switching after 12 January 2027.
  • Dedicated public or easily accessible page explains highly complex, costly, or significantly disruptive switching where Article 29(5) is relevant.
Section 7

7. Test technical switching, open interfaces, and interoperability

For infrastructure-only data processing services, the source provider must take reasonable measures to help the customer achieve after switching to a destination service of the same service type. That support includes capabilities, adequate information, documentation, technical support, and, where appropriate, tools.

For other data processing services, providers must make open interfaces available free of charge and equally to all customers and concerned destination providers. Those interfaces must include enough information about the service to allow software development for data portability and interoperability. Compatibility with common specifications or harmonised standards becomes required at least 12 months after the relevant references are published in the central Union standards repository following the implementing-act process.

  • Infrastructure-only checklist verifies support, documentation, technical support channels, migration tooling, and known gaps.
  • Non-infrastructure checklist verifies open interfaces, API documentation, authentication, schema documentation, rate limits, test credentials, and destination-provider access.
  • Standards tracker records whether relevant common specifications or harmonised standards have been published in the central Union standards repository and when the 12-month compatibility clock starts.
  • Security review confirms switching does not require disclosure of protected digital assets, trade secrets, or actions that compromise customer or provider service security and integrity.
Section 8

8. Capture cooperation duties and verification evidence

Article 27 requires all parties involved, including destination providers, to cooperate in good faith so the switching process is effective, data is transferred on time, and service continuity is maintained. A provider checklist should therefore keep evidence of the handoffs, not only the final export file.

The review output should be a service-level evidence pack that a legal, product, security, support, or engineering reviewer can retest. Each checklist item should show the source article, owner, result, evidence artifact, remediation status, and next review trigger.

  • Contract evidence: signed template version, Article 25 clause mapping, customer notice procedure, retrieval and erasure terms, and any exception notice.
  • Disclosure evidence: switching page, online register, Article 28 website pages, pricing disclosures, and complex-switching notices.
  • Technical evidence: export sample, machine-readable format proof, interface documentation, destination-provider test notes, security review, and switch rehearsal report.
  • Operational evidence: support tickets, customer notifications, continuity-risk notices, incident notes during switching, remediation tickets, approval owner, and review date.
Primary sources

References and citations

eur-lex.europa.eu9 citations
Referenced sections
  • Binding source for Data Act Chapter VI provider obligations on switching between data processing services, plus Articles 34 and 35 on parallel use and interoperability standards.
  • Supports the service-scope check, including Article 23 switching routes, Article 30 technical routes, and Article 31 exclusions for certain custom-built and limited-period non-production services.
  • Article 25 is the binding source for pre-signature contract availability, mandatory switching clauses, notice period, transition period, retrieval period, erasure, support, continuity, security, and switching-charge clauses.
Show 6 more
  • Article 25(3) to 25(5) supports the customer-choice, technical-unfeasibility notice, seven-month alternative period, service-continuity, and one-time customer extension checks.
  • Articles 26 and 28 are the binding sources for switching information, the provider-hosted online register, public infrastructure-jurisdiction transparency, and contract links to those websites.
  • Article 25(2)(e) and 25(2)(f) support the data-category and excluded-internal-data checks; Article 30(5) supports the structured, commonly used, machine-readable export check.
  • Article 29 supports the switching-charge phase-out, directly linked cost cap, pre-contract pricing information, complex-switching disclosures, and public availability checks.
  • Article 30 supports the technical switching checks for functional equivalence, open interfaces, standards compatibility, machine-readable export, and security and trade-secret limits.
  • Article 27 supports the good-faith cooperation and continuity evidence checks; Articles 25, 26, 28, 29, and 30 support the contract, disclosure, charge, and technical evidence categories.
digital-strategy.ec.europa.eu3 citations
Referenced sections
  • Commission implementation source for voluntary model contractual terms and standard contractual clauses related to cloud switching, termination, security, and business continuity.
  • Commission implementation source explaining that cloud SCCs translate Chapter VI into optional contract clauses for switching, termination, security, and business continuity.
  • Commission source for optional SCC topics that can help structure evidence for switching, termination, security, business continuity, non-amendment, non-dispersion, and liability clauses.
cencenelec.eu2 citations
Referenced sections
  • External source for Data Act-related European standardisation work on data governance, interoperability, portability, and switchability.
  • Standardisation source showing Data Act-related European standardisation work on interoperability, portability, and switchability that may feed future implementation evidence.
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission explainer for the Data Act's cloud-market context, application status, and implementation overview.
  • Commission explainer confirms the Data Act cloud-market policy context and the phase-out of switching and data egress charges.
Show all related guides (61)

Data Act Unfair Contractual Terms | Article 13 B2B Contract Review

Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation.

Data Act Vehicle Data Guidance

Commission-cited guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries.

Data Act vs GDPR: connected-product data access

Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts.

EU Data Act Applicability Test

Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act.

EU Data Act Article 3 Pre-Contract Information

What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence.

EU Data Act Checklist for Product, Cloud, and Contract Teams

A cited EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners.

EU Data Act Cloud Switching and Exit Plans

A cited EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records.

EU Data Act Compliance Program

Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership.

EU Data Act Connected Product Scope and Data Types

Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs.

EU Data Act Data Processing Service Switching

A cited EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure.

EU Data Act deadlines and compliance calendar

A cited calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records.

EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates

EU Data Act FAQ index covering connected-product access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, and application dates.

EU Data Act Penalties and Enforcement

Guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary.

EU Data Act Requirements by Workstream

EU Data Act requirements for connected-product access, B2B terms, B2G exceptional need, cloud switching, smart contracts, interoperability, GDPR boundaries, and records.

EU Data Act User Access and Portability Rights

Practical guide to EU Data Act user access, connected-product data portability, third-party sharing, trade secret safeguards, and the GDPR boundary.

EU Data Act vs Data Governance Act

Compare the EU Data Act with the Data Governance Act: connected-product access, cloud switching, B2B/B2G duties, protected public-sector reuse, intermediaries, altruism, governance, and enforcement.

Data Act and Data Governance Act Overlap FAQ

FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows.

Data Act Audit Evidence and Request Logs FAQ

FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries.

Data Act Cloud Switching Contract Terms FAQ

FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records.

Data Act Cloud Switching Fees and Deadlines FAQ

FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records.

Data Act Complaints and Dispute Settlement FAQ

FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records.

Data Act Exportable Data and Metadata FAQ

FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded.

Data Act FAQ for Aftermarket Repair and Mobility Services

FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services.

Data Act SME Exceptions and Startups FAQ

FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms.

Data Act Trade Secret Technical Protection Measures FAQ

FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence.

EU Data Act and Common European Data Spaces FAQ

FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation.

EU Data Act and GDPR: Personal Data Overlap FAQ

FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing.

EU Data Act Application Dates and Transition FAQ

FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain.

EU Data Act Article 32: Foreign Government Access FAQ

FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers.

EU Data Act Article 36 Smart Contract Controls FAQ

FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires.

EU Data Act B2B Data Sharing Compensation FAQ

FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards.

EU Data Act B2G Compensation and Costs FAQ

FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep.

EU Data Act B2G Exceptional Need FAQ

When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence.

EU Data Act Cloud Switching Procurement FAQ

Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence.

EU Data Act Connected Product Scope FAQ

FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope.

EU Data Act data spaces interoperability FAQ

FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence.

EU Data Act Direct Access by Design FAQ

FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act.

EU Data Act Enforcement and Competent Authorities FAQ

FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible.

EU Data Act Functional Equivalence: IaaS Switching FAQ

FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence.

EU Data Act Indirect Access Request Workflow FAQ

FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited.

EU Data Act Interoperability Standards: Articles 33-36

FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614.

EU Data Act Model Terms and Cloud Clauses FAQ

FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence.

EU Data Act Non-Emergency Public-Sector Request FAQ

FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence.

EU Data Act Pre-Contractual Information FAQ

FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries.

EU Data Act Product Data vs Related-Service Data

FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs.

EU Data Act Public Emergency Request FAQ

FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records.

EU Data Act Readily Available Data FAQ

FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics.

EU Data Act Related Services FAQ

FAQ explaining when software is a Data Act related service, how it links to connected products, which product and service data are in scope, and what exclusions apply.

EU Data Act Smart Contracts for Data Sharing FAQ

Answers on Article 36 Data Act smart-contract requirements for data sharing: scope, robustness, access control, termination, archiving, conformity assessment, contract terms, and standards status.

EU Data Act Third-Party Data Sharing FAQ

FAQ on user-directed third-party data sharing under the EU Data Act, covering data holder duties, recipient limits, trade secrets, security, GDPR, and gatekeepers.

EU Data Act Trade Secret Safeguards FAQ

FAQ on protecting trade secrets when handling EU Data Act user and third-party data access requests, including safeguards, withholding, suspension, refusal, notices, and records.

EU Data Act Unfair Contractual Terms FAQ

FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence.

EU Data Act Users, Data Holders, and Recipients FAQ

FAQ explaining Data Act users, data holders, data recipients, connected products, related services, user access, third-party limits, and GDPR boundaries.

EU Data Act Vehicle Data Guidance FAQ

FAQ on EU Data Act vehicle data guidance for connected vehicles, aftermarket repair, mobility services, third-party access, trade secrets, security, and GDPR boundaries.

EU Data Act: Non-Personal Data and Mixed Datasets

FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records.