--- title: "Data Act Cloud Switching Fees And Deadlines FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines" author: "Sorena AI" description: "FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "Regulation (EU) 2023/2854" - "cloud switching fees" - "switching charges" - "data egress charges" - "data processing services" - "Article 29" - "cloud switching charges" - "12 January 2027 switching charge ban" --- **[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 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. *FAQ* *EU* *Data Act* ## EU Data Act Cloud Switching Fees And Deadlines FAQ Which cloud switching fees can still be charged, when they must stop, and which switching deadlines belong in contracts and evidence records. Use this FAQ to review data-processing service contracts, billing controls, exit plans, assistance obligations, and retrieval records under Articles 23 to 29 of the EU Data Act. The EU Data Act regulates switching between data processing services, including cloud and edge services. For fees and deadlines, the practical questions are whether a charge is a switching charge, whether it is still permitted during the transition, when it must be removed, and whether the contract gives the customer the required notice, assistance, transition, retrieval, and erasure rights. ## Which cloud services are covered by the switching fee rules under the Data Act? The Data Act switching rules apply to providers of data processing services that provide those services to customers in the Union. The definition covers digital services giving on-demand network access to configurable, scalable, and elastic computing resources, which is why the Commission describes Chapter VI as covering cloud and edge services. The fee review should therefore start with the service catalogue and customer contract, not with a generic cloud label. Identify the source provider, the customer, the service type, any destination provider or on-premises target, and the exportable data and digital assets involved in the switching process. - Check whether the contract is for a data processing service supplied to a customer in the Union. - Map the service type, source provider, customer, destination path, and on-premises alternative where relevant. - Separate Chapter VI switching issues from connected-product data access, B2B data sharing compensation, and public-sector request duties. 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 1 and Article 2 define the provider, customer, data processing service, switching, switching charge, and exportable-data concepts used by this FAQ. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explains Chapter VI as applying to cloud and edge data processing services and describes the commercial switching barriers the Data Act targets. ## What counts as a Data Act switching charge for Cloud Switching Fees And Deadlines implementation evidence? A switching charge is a charge, other than standard service fees or early termination penalties, imposed by a provider on a customer for the actions required by the Data Act to switch to another provider or to on-premises ICT infrastructure. The definition expressly includes data egress charges. This means the billing inventory should not stop at line items called exit fees. It should include data egress, migration assistance fees, export tooling charges, charges for required switching actions, and any renamed or bundled fee that is triggered by the customer's switch. - Tag each billing item as standard service fee, early termination penalty, switching charge, data egress charge, or unrelated professional service. - Treat data egress charges for extracting customer data to another provider or on-premises infrastructure as switching-charge candidates. - Escalate any bundled or renamed fee that is payable because the customer is switching. 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 defines data egress charges and switching charges, including the exclusion for standard service fees and early termination penalties. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission describes high data-egress charges as a switching barrier and states that the Data Act removes switching charges, including data egress charges. ## Which switching charges may be imposed before 12 January 2027 under the Data Act? The Data Act context is the starting point for this answer. From 11 January 2024 to 12 January 2027, providers may impose reduced switching charges. Those reduced charges must not exceed costs incurred by the provider that are directly linked to the switching process concerned. A provider should therefore keep cost support for each reduced charge. A generic fee schedule is weak evidence unless it shows the charge is tied to actual direct switching costs and not to lock-in, margin recovery, ordinary service revenue, or a disguised deterrent. - For each charge before 12 January 2027, record the directly linked switching cost it recovers. - Keep invoices, billing configuration, cost model inputs, and approval records for any reduced switching charge. - Remove or reclassify charges that cannot be tied to costs directly linked to the customer's 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 29 allows reduced switching charges during the transition and limits them to directly linked switching costs. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explains the transition as the first three years after entry into force, from 11 January 2024 to 12 January 2027. ## What changes on 12 January 2027 under the Data Act for Cloud Switching Fees And Deadlines implementation evidence? The Data Act context is the starting point for this answer. From 12 January 2027, providers of data processing services must not impose switching charges on customers for the switching process. The Commission describes this as the complete removal of switching charges, including data egress charges. The practical control is a hard sunset in billing, contract templates, support scripts, renewal packs, procurement responses, and public pricing materials. After that date, a charge triggered by the switching process needs a documented reason why it is not a switching charge. - Set a billing-control stop date of 12 January 2027 for switching charges. - Update contract templates, order forms, pricing pages, and help-center copy before the stop date. - Keep an exception review for any post-12 January 2027 charge that could be confused with a switching charge. 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 29 sets the 12 January 2027 date from which switching charges may no longer be imposed on customers. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission confirms that the Data Act removes switching charges, including charges for data transit, from 12 January 2027. ## Which switching deadlines must appear in the contract under the Data Act? The Data Act context is the starting point for this answer. The contract must set out the customer's switching rights and the provider's switching obligations in writing and be available before signature in a way the customer can store and reproduce. The contract must include a maximum notice period for starting the switching process that does not exceed two months. After that notice period, the contract must allow switching or porting of all exportable data and digital assets without undue delay and not later than the mandatory maximum transitional period of 30 calendar days. During that period, the provider must give reasonable assistance, maintain business continuity, provide clear information about known continuity risks on the provider side, and maintain a high level of security. - Check that the notice period for initiating switching does not exceed two months. - Check that the standard transition commitment is no more than 30 calendar days after the notice period. - Attach assistance, continuity, known-risk, and security commitments to the switching clause, not to a vague support policy. 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 written switching terms, a maximum notice period of two months, and a mandatory maximum transitional period of 30 calendar days. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - The Commission's voluntary Standard Contractual Clauses include cloud switching, termination, security, and business-continuity clauses for contracts. ## Can the 30-day transition period be extended under the Data Act for Cloud Switching Fees And Deadlines implementation evidence? Yes, but the Data Act gives specific conditions. If the mandatory 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. Separately, the contract must give the customer the right to extend the transitional period once for a period the customer considers more appropriate for its own purposes. Providers should distinguish provider-justified technical unfeasibility from a customer-requested extension. - Use a 14-working-day response control when claiming the 30-day transition is technically unfeasible. - Cap provider-proposed alternative transition periods at seven months. - Record whether an extension is provider-justified technical unfeasibility or the customer's one-time extension. 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 sets the technical-unfeasibility notice, justification, seven-month cap, and customer extension rule. ## What retrieval and erasure deadlines apply after switching under the Data Act? The Data Act context is the starting point for this answer. The contract must provide a minimum data retrieval period of at least 30 calendar days. That retrieval period starts after the end of the transitional period agreed between the customer and the provider. The contract must also guarantee full erasure of exportable data and digital assets generated directly by, or relating directly to, the customer after the retrieval period expires, or after a later agreed period, provided the switching process has completed successfully. - Set the retrieval window to at least 30 calendar days after the transition period ends. - Define which exportable data and digital assets are retrievable during that window. - Keep erasure evidence linked to successful switching completion and the expiry of the retrieval or later agreed period. 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 a retrieval period of at least 30 calendar days and an erasure clause after retrieval or a later agreed period. ## What information must providers give before and during switching under the Data Act? The Data Act context is the starting point for this answer. Before entering into a contract, providers must give prospective customers clear information on standard service fees, early termination penalties, and any reduced switching charges that may be imposed during the transition period. Where relevant, providers must also give information on services involving highly complex or costly switching, or where switching is impossible without significant interference in data, digital assets, or service architecture. Providers must also give customers information on available switching and porting procedures, methods, formats, restrictions, and known technical limitations. They must provide a reference to an up-to-date online register with details of data structures, data formats, and relevant standards and open interoperability specifications for exportable data. - Put pre-contract fee disclosures in the contract pack and align them with public pricing materials. - Maintain a switching information page or register that covers procedures, methods, formats, restrictions, and known technical limitations. - Keep the online register current for exportable data structures, formats, standards, and open interoperability specifications. 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 29 require switching-procedure information, an online exportable-data register, and clear pre-contract fee information. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explains that Chapter VI creates minimum cloud contract requirements and greater contractual transparency for public and private customers. ## What evidence should teams keep for a fee or deadline decision under the Data Act? Keep evidence that connects the contract term, billing item, customer request, technical assessment, and outcome to the Data Act rule being applied. The strongest record is a switching-fee and deadline register that can be reviewed without reconstructing decisions from emails or support tickets. For each customer or service, the record should show the charge classification, direct-cost support where reduced charges are used before 12 January 2027, notice-period start and end dates, transition-period dates, any 14-working-day technical-unfeasibility notice, retrieval-window dates, erasure evidence, and the owner who approved the decision. - Maintain a charge register with charge type, amount, cost basis, contract location, customer segment, owner, and removal date. - Maintain a switching request log with request date, notice period, transition period, assistance provided, risks communicated, security controls, and completion status. - Maintain evidence for retrieval and erasure, including exportable-data scope, retrieval-window dates, customer notices, and post-retrieval erasure confirmation. 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 25, 26, and 29 define the contract, information, transition, retrieval, erasure, and fee facts that should be evidenced. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - The voluntary SCCs provide implementation context for contract records covering switching, termination, security, and business continuity. ## What Data Act source evidence should teams keep for the Cloud Switching Fees And Deadlines FAQ decision? Keep the quoted Data Act Article 29 rule, the Commission's cloud-switching explanation, and the contract record together so a reviewer can see why a charge was treated as a switching charge or as a reduced charge before 12 January 2027. The most useful evidence set includes the source URL, the relevant contract clause, the billing item, the customer or service affected, the decision date, the reviewer, and any note explaining why the charge is tied to directly linked switching costs or removed by the 12 January 2027 deadline. - Store the Article 29 citation or source URL with the contract clause it supports. - Keep the billing line, cost support, and removal date in the same record. - Record the review date and reviewer so the deadline decision can be traced later. ## How should teams assign ownership for Data Act Cloud Switching Fees And Deadlines implementation work? Assign one accountable owner for each Data Act switching-control area: contract wording, billing configuration, customer communications, or exit evidence. The owner should be the person who can actually change the process, while legal, finance, procurement, cloud operations, and support are recorded as consulted teams. For Article 29 timing, the billing owner should own the 12 January 2027 stop date and any pre-2027 reduced-charge evidence. For Article 25 timing, the contract owner should own the notice period, 30-day transition, retrieval window, and erasure clause. - Give billing, contract, and support owners separate responsibilities instead of one generic compliance owner. - Link each owner to the specific Article 25 or Article 29 control they maintain. - Record who reviews exceptions for technical unfeasibility or disputed charges. ## Which Data Act implementation evidence makes the Cloud Switching Fees And Deadlines answer usable later? Keep evidence that a later reviewer can use without reconstructing the Data Act answer from scratch: the cited Article 25 or 29 text, the affected contract template, the live billing rule, the customer notice, and the completion record. That package should make it clear when the transition began, when it ended, and whether any charge remained lawful at that point. Useful artifacts include source URLs, versioned contract clauses, fee approvals, implementation tickets, switching logs, and the final erasure or completion confirmation. These records show not only what the rule says, but how the team applied it to the specific service. - Keep versioned contract text and billing rules with the review outcome. - Save the switching log, customer notices, and completion confirmation together. - Use the same evidence pack for later audits or contract renewals. ## 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 cloud switching obligations, switching-charge definitions, the reduced-charge transition, the 12 January 2027 fee ban, contract deadlines, retrieval, erasure, information duties, and provider evidence points. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation of Chapter VI scope, cloud and edge switching barriers, data egress charges, contract transparency, functional equivalence, and the 12 January 2027 charge removal. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission page for voluntary cloud Standard Contractual Clauses covering switching and exit, termination, security, and business continuity. ## 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 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 Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [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 evidence section* ## Data Act Review Cloud Switching Fees And Deadlines Turn Data Act cloud switching fee and deadline rules into contract clauses, billing controls, request logs, and evidence records that legal, cloud, procurement, support, and finance teams can maintain. - [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on cloud switching charges, transition periods, retrieval windows, and adjacent Data Act obligations. - [Discuss Cloud Switching Fees And Deadlines](/contact.md): Review fee inventories, cloud contract terms, exit records, and implementation evidence for Data Act switching workflows. --- [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/cloud-switching-fees-and-deadlines