--- title: "Data Act Functional Equivalence FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/functional-equivalence" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/functional-equivalence" author: "Sorena AI" description: "FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "functional equivalence" - "cloud switching" - "data processing services" - "IaaS" - "interoperability" - "Regulation (EU) 2023/2854" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # Data Act Functional Equivalence FAQ FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. *FAQ* *EU* *Data Act* ## EU Data Act Functional Equivalence FAQ Functional equivalence is a Data Act cloud-switching concept, not a promise that two services will behave identically. Use this FAQ to separate IaaS functional-equivalence support from broader PaaS, SaaS, export, interface, interoperability, contract, and evidence duties. This FAQ explains how functional equivalence works in the EU Data Act rules on switching data processing services. It focuses on customer outcomes after switching, what source providers must support, what customers and destination providers still need to do, and where the Data Act sets limits. ## What does functional equivalence actually mean under the EU Data Act cloud-switching rules? Under the Data Act, functional equivalence means re-establishing a minimum level of functionality after a customer switches to a new data processing service of the same service type. The comparison is based on the customer's exportable data and digital assets, and it looks at whether the destination service delivers a materially comparable outcome for the same input and for shared contractual features. That is narrower than identical performance, identical configuration, or a full replica of the old environment. Teams should frame functional equivalence as a switching outcome to facilitate, not as a warranty that every workload, integration, latency profile, or provider-specific feature will carry across unchanged. - Compare the source and destination services only for the same service type and shared features supplied under the contract. - Base the assessment on exportable data and digital assets, not on provider-owned assets, protected trade secrets, or destination-provider architecture. - Avoid customer-facing promises such as seamless identical operation unless the specific migration plan and service pair support that claim. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(37) defines functional equivalence by reference to minimum functionality, exportable data, digital assets, same service type, and materially comparable outcomes. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer describes functional equivalence as comparable outcomes for shared IaaS features after switching. ## Which cloud services have the functional-equivalence duty under the Data Act? The Data Act context is the starting point for this answer. The functional-equivalence obligation in Article 30(1) is aimed at providers of data processing services limited to infrastructural elements such as servers, networks, and virtual resources. In practical cloud terms, the Commission FAQ describes this as applying to source providers of Infrastructure as a Service. PaaS and SaaS providers are still covered by Chapter VI when their services meet the Data Act definition of data processing services, but their Article 30 duties are different. They must make open interfaces available, support data portability and interoperability, and comply with applicable interoperability specifications or standards when those references are published as required by the Data Act. - Treat functional equivalence as an IaaS switching issue unless the grounding source for the service says otherwise. - For PaaS or SaaS, focus the page, contract, and support workflow on open interfaces, machine-readable exports, and standards compatibility rather than functional-equivalence guarantees. - Check whether a custom-built service or limited testing service falls under the specific regime in Article 31 before applying the full Chapter VI workflow. Sources for this answer: - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - FAQ 58a states that functional equivalence in Article 30(1) applies to IaaS, while PaaS and SaaS have open-interface and standards duties. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 30 separates IaaS functional-equivalence facilitation from the open-interface, standards, and export obligations for other data processing services. ## What result should a customer be able to expect after switching under the Data Act? For an in-scope IaaS switch, the customer should be supported toward using a destination service of the same service type with materially comparable outcomes for shared features. The Data Act does not say the source provider must make the destination service identical, rebuild the workload for the customer, or control the destination provider's environment. A useful switching plan therefore states the target outcome in operational terms: which workloads, configurations, data categories, access rights, security settings, machine images, containers, or other digital assets will be exported or documented; which destination features are shared; and which differences remain outside the source provider's control. - Define acceptance criteria around shared features and comparable outcomes, not around perfect parity. - Identify customer tasks and destination-provider tasks separately from source-provider tasks. - Document known risks to business continuity and any technical limitations before the transition starts. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 25 requires reasonable assistance, due care for business continuity, information on known continuity risks, and security during switching. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - FAQ 58b explains that the source provider is not responsible for rebuilding the customer's service in the destination provider's ecosystem. ## What must the source provider provide to facilitate functional equivalence under the Data Act? The Data Act context is the starting point for this answer. For IaaS functional equivalence, the source provider must take reasonable measures within its power. Article 30 describes the facilitation package as capabilities, adequate information, documentation, technical support, and, where appropriate, necessary tools. The provider's switching contract and public information should also tell customers how switching and porting work, which methods and formats are available, what restrictions or technical limitations are known, and where to find the provider's register of data structures, formats, standards, and open interoperability specifications for exportable data. - Maintain a switching runbook that lists export methods, supported formats, known limitations, support channels, and escalation routes. - Keep an online register for exportable-data structures, formats, relevant standards, and open interoperability specifications. - Make clear which support is included in the Data Act switching obligation and which additional transition services are separately requested by the customer. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 26 and 30 ground the provider information, register, documentation, technical support, and tooling needed for switching. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - FAQ 53 explains digital assets as elements customers need to use their data in the new provider environment, such as configuration, security, access, virtual machines, and containers. ## What data and digital assets matter for the assessment under the Data Act? The switching file should distinguish exportable data from digital assets and from material that the Data Act does not require the provider to disclose or transfer. Exportable data covers input and output data, including metadata generated or co-generated by the customer's use of the service, but excludes provider or third-party intellectual property and trade secrets. Digital assets are broader practical enablers for using the customer's data in a new environment. The Commission FAQ gives examples such as configuration settings, security and access-control metadata, applications, virtual machines, and containers where the customer has an independent right to use them. - List exportable data separately from provider-owned assets, third-party assets, trade secrets, and security-sensitive material. - List digital assets needed for the new environment, including configuration, access-control, virtualisation, and workload packaging items where applicable. - For each exclusion, record why the exclusion does not impede or delay the switching process. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(38) and Article 25 ground the exportable-data category and the contract specification of portable data and digital assets. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - FAQ 53 explains the difference between exportable data and digital assets for switching data processing services. ## How do interoperability duties connect to functional equivalence under the Data Act? Interoperability is the technical and organisational foundation that makes switching realistic. For PaaS and SaaS, the Data Act focuses on open interfaces, sufficient service information for software communication, compatibility with published common specifications or harmonised standards, and structured, commonly used, machine-readable exports where standards have not yet been published. For IaaS, interoperability standards and open specifications can also help customers reach functional equivalence, but they do not turn the source provider into the operator of the destination environment. The standardisation route should be tracked as a dependency because the Data Act ties some compatibility duties to publication in the central Union standards repository. - Track whether relevant common specifications or harmonised standards have been published for the service type. - For non-IaaS services, align interfaces, export formats, and register entries with the applicable standards timeline. - For IaaS, use interoperability work to support comparable outcomes while preserving the limits on source-provider responsibility. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 30 and 35 connect switching, open interfaces, export formats, common specifications, harmonised standards, and functional equivalence. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer states that interoperability between data processing services is essential for customers to benefit from easier switching. ## What limits should contracts and help-center copy state clearly under the Data Act? Functional-equivalence wording should not imply unlimited responsibility. The Data Act limits the source provider's technical obligations to the services, contracts, and commercial practices it provides. It also says providers are not required to develop new technologies or services, disclose or transfer protected intellectual property or trade secrets, or compromise security and service integrity. The customer-facing explanation should also separate included switching assistance from optional additional services. A customer may request additional support beyond the provider's Data Act switching obligations, but that should be described and priced as an additional service agreed in advance rather than hidden inside the mandatory switching process. - State that functional equivalence is limited to the source provider's own service environment and reasonable measures within its power. - Do not promise transfer of protected intellectual property, trade secrets, or security-sensitive assets. - Separate mandatory switching support from separately requested migration, re-architecture, optimisation, or managed transition work. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 24, 29, and 30 limit source-provider responsibility, protect IP, trade secrets, security, and distinguish additional services from switching obligations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - FAQ 58b explains that source providers are not responsible for rebuilding the service in the destination ecosystem. ## Which records should teams keep to justify an EU Data Act functional-equivalence decision later? For functional equivalence, the Data Act record should identify the source clause, Commission guidance, actor role, dataset, request or contract trigger, and the owner who approved the interpretation. Keep the cited external URL, decision date, reviewer, unresolved assumptions, and implementation artifact together so the answer remains auditable. - Map the decision to the Data Act provision or Commission guidance relied on for the switching assessment. - Record the service type, shared features, exportable data, digital assets, and any excluded items that affect the outcome. - Store the approval trail, implementation artifact, and review trigger in one evidence file so the decision can be revisited if the service or standards change. ## Who should own EU Data Act functional-equivalence work and the related follow-up actions? For functional equivalence, the Data Act workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process. For functional equivalence, use one accountable owner per action, then record consulted teams and evidence dependencies separately. - Assign one accountable owner for the switching decision, and name the operational owner who can execute the export, support, or migration steps. - Record the teams consulted on legal scope, technical feasibility, security, and customer communications instead of spreading responsibility across everyone. - Set a review trigger for service changes, new standards, or new destination-provider capabilities so the decision can be refreshed when needed. ## How does the EU Data Act distinguish functional equivalence for IaaS from a plain export for SaaS? Under the Data Act, the functional-equivalence duty centres on IaaS, where the source provider must take reasonable measures so the customer can re-establish a minimum level of functionality on a same-type destination service. For PaaS and SaaS the duty is lighter: export the exportable data and digital assets in a structured, commonly used, machine-readable format. Teams should classify the service before promising an outcome, because expecting functional equivalence from a SaaS provider, or accepting only a raw export from an IaaS provider, both misread the Regulation. - Apply the functional-equivalence duty to IaaS and the structured-export duty to PaaS and SaaS. - Classify the service type before setting customer expectations about the switching outcome. ## What reasonable measures must a source provider take to facilitate EU Data Act functional equivalence? Under the Data Act, the source provider must offer reasonable assistance, exercise due care to maintain business continuity, provide capabilities and information to support the switch, and keep a high level of security during transfer and retrieval. The duty is about enabling the customer to reach a comparable outcome, not rebuilding the destination environment. The measures should be scoped to the provider's own service and contractual features, with any work beyond that treated as a separately agreed additional service rather than part of the mandatory switching support. - Provide assistance, continuity care, and security during the transfer and retrieval window. - Scope the duty to the provider's own service and price anything beyond it as an additional service. ## When can a source provider decline a functional-equivalence request under the EU Data Act limits? Under the Data Act, a source provider is not required to develop new technologies or services, disclose or transfer protected intellectual property or third-party trade secrets, or compromise the security and integrity of its service to deliver functional equivalence. These are genuine limits rather than excuses to avoid the switching duty. A defensible decline points to one of those specific limits for the requested step, while still delivering the export, assistance, and continuity measures the Regulation requires for everything else. - Decline only where a request would require new development, IP or trade-secret transfer, or a security compromise. - Still deliver the export, assistance, and continuity duties for the parts of the switch not affected by the limit. ## Primary sources - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for Chapter VI switching duties, Article 2 definitions, Article 23 obstacle removal, Article 25 contract terms, Article 26 information duties, Article 29 switching charges, Article 30 technical switching duties, and Article 35 interoperability. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission fact page explaining cloud switching, data egress, PaaS and SaaS open interfaces, IaaS functional equivalence, and interoperability context. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ context for service scope, exportable data, digital assets, switching charges, notice and transition periods, interoperability repository, and the limits of source-provider responsibility. ## Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): 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 and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): 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. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): 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 B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): 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](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): 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](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md): 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](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): 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](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): 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. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): 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](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): 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](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded 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](/artifacts/eu/data-act/data-act-vs-gdpr.md): 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 and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): 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 Applicability Test](/artifacts/eu/data-act/applicability-test.md): 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 Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): 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 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): 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 Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): 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](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): 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](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): 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](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): 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 Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded 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](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): 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 Compliance Program](/artifacts/eu/data-act/compliance.md): 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](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): 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 Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md): 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 deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked 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 Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md): 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](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md): 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 FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. - [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md): 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 Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md): 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. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md): 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](/artifacts/eu/data-act/faq/product-data-and-service-data.md): 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 Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md): 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](/artifacts/eu/data-act/faq/related-services.md): 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 requirements](/artifacts/eu/data-act/requirements.md): Source-grounded EU Data Act requirements for connected-product data access, B2B sharing terms, B2G exceptional needs, cloud switching, smart contracts, interoperability, GDPR boundaries, and records. - [EU Data Act Smart Contracts for Data Sharing FAQ](/artifacts/eu/data-act/faq/smart-contracts-for-data-sharing.md): 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](/artifacts/eu/data-act/faq/third-party-data-sharing.md): 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](/artifacts/eu/data-act/faq/trade-secrets-safeguards.md): 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](/artifacts/eu/data-act/faq/unfair-contractual-terms.md): 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 User Access and Portability Rights](/artifacts/eu/data-act/access-rights-and-portability.md): 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 Users, Data Holders, and Recipients FAQ](/artifacts/eu/data-act/faq/users-data-holders-and-recipients.md): 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](/artifacts/eu/data-act/faq/vehicle-data-guidance.md): 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 vs Data Governance Act](/artifacts/eu/data-act/data-act-vs-data-governance-act.md): 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. *Recommended next step* *Placement: after implementation section* ## Data Act Review Cloud Switching Claims Check whether your Data Act cloud-switching materials distinguish IaaS functional-equivalence support from PaaS, SaaS, export, interface, interoperability, charge, and evidence duties. - [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act cloud switching, exportable data, digital assets, and functional-equivalence limits. - [Discuss Cloud Switching](/contact.md): Review Data Act implementation impacts across contracts, support workflows, export registers, interoperability evidence, and customer communications. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/faq/functional-equivalence