← Back to all briefings
Data Strategy 6 min read Published Updated Credibility 86/100

Data Strategy — Cloud strategy

The EU Data Act's cloud switching requirements are approaching in September 2025. Cloud providers need to enable customers to switch providers without vendor lock-in, support data portability, and eliminate egress fees. If you are running cloud services in the EU, your exit assistance features need to be ready.

Kodi C.

Editor & Research Lead

Editorially reviewed for factual accuracy

Data strategy pillar illustration for Zeph Tech briefings
Data strategy, stewardship, and privacy briefings

Data processing services (cloud, edge, PaaS) face a deadline to comply with Data Act Chapter VI switching obligations. By , programs should be deep in execution: removing switching fees, delivering interoperable export tooling, and documenting customer support procedures that meet Articles 23-26. This countdown represents a critical juncture for cloud providers, as the Data Act's switching provisions fundamentally reshape the competitive dynamics of European cloud markets.

Data Act Cloud Switching Framework

The Data Act's Chapter VI establishes full requirements for data processing service providers to enable customer switching. These provisions address the EU's concern that cloud lock-in inhibits competition and innovation. By mandating switching capabilities, the regulation aims to create a more dynamic and competitive cloud market benefiting European businesses and consumers.

The switching obligations apply broadly to infrastructure-as-a-service, platform-as-a-service, and software-as-a-service providers serving EU customers. Edge computing services and AI platforms also fall within scope. The regulation's extraterritorial application captures non-EU providers serving European markets, creating global compliance implications for international cloud operators.

Switching requirements encompass both technical capabilities and commercial practices. Providers must enable data portability, application migration, and service continuity during transitions. Commercial practices including switching fees, contract terms, and support obligations face detailed regulation. Together, these requirements create a full framework for effective switching.

Technical Switching Capabilities

Articles 23-25 specify technical requirements for enabling customer switching. Providers must offer data export capabilities in structured, commonly used, machine-readable formats. Export functionality must cover all customer data including configurations, metadata, and application state. Performance requirements ensure exports complete within reasonable timeframes without degrading ongoing services.

Interoperability requirements mandate support for open standards and interfaces. Providers must document APIs, data formats, and integration requirements enabling migration to alternative services. Where industry standards exist, providers should support them. Where standards are emerging, providers should participate in standardization efforts and implement evolving specifications.

Migration assistance obligations require providers to support customers during switching processes. Technical staff must be available to answer questions, troubleshoot issues, and guide. Documentation must cover migration procedures, common challenges, and recommended approaches. Providers cannot obstruct or delay switching through technical means.

Commercial Switching Obligations

The Data Act progressively eliminates switching fees that historically deterred customer migration. From January 2027, providers cannot charge fees specifically for switching or data egress during migration. During the transition period, charges must be reduced progressively and disclosed transparently. Cost-based charging may continue for services genuinely required during migration.

Contract terms must support customer switching rights. Provisions that unreasonably restrict switching, impose excessive notice periods, or create other barriers are prohibited. Contracts must disclose switching procedures, timelines, and any applicable charges clearly. Customers must receive reasonable notice of contract changes affecting switching rights.

Transition assistance must continue for a reasonable period after switching initiation. Providers cannot immediately end services or access when customers begin migration processes. Grace periods enable customers to complete migrations without service disruption. Support obligations continue throughout transition periods.

Implementation program Planning

Cloud providers should have full switching compliance programs well underway by mid-May 2025. Program components include technical capability development, contract remediation, operational procedure creation, and staff training. Cross-functional teams spanning engineering, legal, customer success, and compliance should coordinate setup.

Technical workstreams should address data export tools, API documentation, interoperability testing, and migration support capabilities. Engineering investments may be significant for providers whose architectures were not designed with portability in mind. Prioritization should focus on capabilities required for September compliance with improvement roadmaps for future improvements.

Legal and commercial workstreams should address contract updates, pricing model changes, and disclosure requirements. Customer communications should explain upcoming changes and available switching support. Sales and account management teams need training on discussing switching capabilities without creating compliance risk.

Compliance Evidence Development

Providers should build evidence packages demonstrating switching compliance. Documentation should cover technical capabilities, contract terms, operational procedures, and customer communications. Evidence packages support regulatory inquiries, customer due diligence requests, and internal audit verification.

Testing evidence should show that switching capabilities work effectively. Migration testing with representative workloads validates export functionality, data integrity, and timeline compliance. Documentation of test procedures, results, and remediation actions shows rigorous validation. Customer pilot programs provide real-world evidence of switching support.

Compliance monitoring should track switching-related metrics including export volumes, migration durations, support ticket resolution, and customer feedback. Dashboard visibility enables leadership oversight and early identification of compliance gaps. Trend analysis supports continuous improvement and early risk management.

Customer Engagement Strategies

preventive customer engagement builds trust and shows commitment to switching rights. Communications should explain available switching capabilities, support resources, and timeline expectations. Transparency about current capabilities and improvement roadmaps shows good faith even where gaps exist.

Customer feedback channels should capture switching-related concerns and requests. Product development should incorporate customer input on export formats, migration tools, and support needs. Customer advisory groups can provide early feedback on planned capabilities and identify priority improvements.

Account management processes should address switching discussions professionally. Representatives should be trained to discuss switching options without creating retention pressure that could constitute obstruction. Competitive positioning should emphasize service value rather than switching barriers.

Competitive Implications

The Data Act's switching provisions reshape cloud competitive dynamics. Providers that historically relied on lock-in effects for customer retention must develop alternative value propositions. Competition will now center on service quality, innovation, performance, and price rather than switching costs.

Market opportunities emerge for providers with strong switching capabilities. Customers exercising Data Act rights may evaluate alternatives more actively. Providers that help easy onboarding from competitors can capture these switching customers. Migration assistance and competitive pricing can accelerate customer acquisition.

Strategic positioning should consider both defensive and offensive implications. Defending existing customer relationships requires demonstrating superior value that justifies continued engagement. Offensive strategies should identify target customers likely to switch and develop compelling migration support and incentives.

Regulatory Enforcement Preparation

National competent authorities will enforce Data Act switching obligations. Providers should understand enforcement approaches in key markets and prepare for regulatory engagement. Relationships with regulators can provide insight into interpretation questions and enforcement priorities.

Complaint handling procedures should address customer concerns about switching obstacles. Documented procedures for investigating and resolving complaints show compliance commitment. Escalation paths enable serious concerns to receive appropriate attention. Response timelines should meet customer expectations and regulatory requirements.

Penalty exposure for non-compliance can be significant. Administrative fines, mandatory compliance orders, and reputational damage all represent potential consequences. Risk assessment should evaluate likelihood and impact of enforcement actions and guide compliance investment prioritization.

You may also find useful

Hand-picked articles on adjacent topics.

Continue in the Data Strategy pillar

Return to the hub for curated research and deep-dive guides.

Visit pillar hub

Latest guides

  • Data Strategy Operating Model Guide

    Design a data strategy operating model that satisfies the EU Data Act, EU Data Governance Act, U.S. Evidence Act, and Singapore Digital Government policies with measurable…

  • Data Interoperability Engineering Guide

    Engineer interoperable data exchanges that satisfy the EU Data Act, Data Governance Act, European Interoperability Framework, and ISO/IEC 19941 portability requirements.

  • Data Stewardship Operating Model Guide

    Establish accountable data stewardship programmes that meet U.S. Evidence Act mandates, Canada’s Directive on Service and Digital, and OECD data governance principles while…

Coverage intelligence

Published
Coverage pillar
Data Strategy
Source credibility
86/100 — high confidence
Topics
Cloud strategy · EU regulation · Data portability
Sources cited
3 sources (eur-lex.europa.eu, digital-strategy.ec.europa.eu, iso.org)
Reading time
6 min

Documentation

  1. Regulation (EU) 2023/2854 (Data Act) — Official Journal of the European Union
  2. Data Act explained: questions and answers — European Commission
  3. ISO 8000-2:2022 — Data Quality Management — International Organization for Standardization
  • Cloud strategy
  • EU regulation
  • Data portability
Back to curated briefings

Comments

Community

We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.

    Share your perspective

    Submissions showing "Awaiting moderation" are in review. Spam, low-effort posts, or unverifiable claims will be rejected. We verify submissions with the email you provide, and we never publish or sell that address.

    Verification

    Complete the CAPTCHA to submit.