TL;DR: Use a cloud renewal to examine contractual exit terms and operational reversibility. The supplied report places the EU switching-fee change on 12 January 2027, but says proprietary APIs, vendor-specific data formats and identity dependencies may still obstruct a move. Test at least one critical workload and check that its exported data is usable.

  • Review auto-renewal, termination deadlines, egress thresholds and migration-fee clauses; the report says existing contracts do not automatically adopt new terms.
  • Assess APIs, data formats and identity or IAM dependencies alongside fee clauses because technical lock-in may remain.
  • Test a critical workload and check whether its exported data is readable in an open format without tool-specific translation.
  • Distinguish cross-provider switching from transfers between regions or availability zones within one provider, which the report says may remain billable in practice.

A cloud contract renewal can change the terms for leaving without making it possible to leave easily. The supplied report places the EU cloud switching-fee change on 12 January 2027 and says contractual and technical barriers may remain. Use your next renewal to review exit terms and test whether at least one critical workload, its data and its dependencies can move.

Use a cloud renewal to examine contractual exit terms and operational reversibility. The supplied report places the EU switching-fee change on 12 January 2027, but says proprietary APIs, vendor-specific data formats and identity dependencies may still obstruct a move. Test at least one critical workload and check that its exported data is usable.

The report says the change covers IaaS, PaaS and SaaS providers serving EU customers. Verify the timing, scope and current legal wording before relying on them. Removing a fee does not prove that a workload is reversible.

Key takeaways for cloud switching fees

  • The report places the change on 12 January 2027; verify its current status and scope.
  • Existing contracts do not automatically adopt new terms. Review renewal, termination, egress and migration-fee clauses.
  • Proprietary APIs, vendor-specific data formats and identity or IAM dependencies can still obstruct a move.
  • Test at least one critical workload, including whether its exported data is readable in an open format without tool-specific translation.

What does the reported EU cloud switching-fee change cover?

The report says the EU Data Act entered into force in January 2024, most provisions applied from 12 September 2025, and cloud-specific switching rules begin on 12 January 2027. It describes the fee change as applying to IaaS, PaaS and SaaS providers serving EU customers. Confirm these dates and the legal scope before using them to guide a contract decision.

The report treats switching and egress fees as only the most visible form of lock-in. Their removal does not make proprietary APIs, data formats or identity dependencies portable. Fee terms are one part of exit readiness, not evidence that a service can be transferred in practice.

Which contract terms should you review at renewal?

Existing contracts do not automatically change when new switching rules take effect, according to the report. Review the terms that govern how and when you can leave: auto-renewal, contract length, termination deadlines, egress thresholds and migration fees. The legal change does not itself rewrite those clauses.

An adult turns a broad metal clasp on a blank contract folio.AI GENERATED
An adult turns a broad metal clasp on a blank contract folio.

Also check the notice required to terminate and any conditions attached to egress. Plan for egress costs that may still apply under the relevant arrangements. The decision is whether your organization has a clear contractual route to act on its exit rights – not simply whether a fee clause has changed.

Why can a workload remain hard to move without switching fees?

The report identifies proprietary APIs, vendor-specific data formats and identity or IAM binding as potential barriers. IAM means identity and access management: the systems and arrangements that control access to a workload. Moving data alone may not move the service if its dependencies remain tied to the current provider.

An export is not proof of portability if the receiving environment cannot read the data without translation by the original provider’s tools. This matters for SaaS, too: data that can only be read in the original application remains a lock-in concern even if a fee is removed.

How should you test cloud exit readiness?

Test at least one critical workload rather than relying on an exit plan on paper. The report recommends a migration stress test and checking whether exported data can be read in an open format without tool-specific translation. An open-format export is useful evidence, but it does not prove that every workload dependency can move.

An adult frees a root-bound plant from a sculptural pot during a careful transplant.AI GENERATED
An adult frees a root-bound plant from a sculptural pot during a careful transplant.

The report’s proposed actions ahead of the deadline are to:

  • Compile contract terms and review renewal and termination deadlines.
  • Plan for egress costs.
  • Assess APIs, data formats and IAM dependencies for each workload.
  • Test one critical workload and document responsibilities.
    The report recommends testing a workload in 2026. Check that timing against your renewal schedule and the current legal position before acting on it.

The report distinguishes GDPR Article 20, which it describes as addressing data portability, from the Data Act’s focus on cloud switching barriers. It says the Data Act targets moves between providers. Transfers between regions or availability zones within one provider are a different case, described as a grey area that may remain billable in practice. Check the applicable contract and current legal position rather than assuming the same treatment applies.

Frequently asked questions

Do existing cloud contracts automatically change when switching fees are removed?

No. The report says existing contracts do not automatically adopt new terms. Review auto-renewal, termination, egress-threshold and migration-fee clauses, and verify how the current legal wording applies. A fee change does not itself amend your agreement or remove technical barriers.

Are transfers between regions within one provider covered in the same way?

The report describes the Data Act’s switching rules as targeting moves between providers. It treats transfers between regions or availability zones within one provider as a grey area and says they may remain billable in practice. Check the contract and current legal position.

Does an open-format SaaS export prove the data is portable?

No. The data must be readable without tool-specific translation. The report identifies SaaS data that remains readable only in the original application as a lock-in concern, even if a fee is removed. Include the export in a critical-workload stress test.

Key takeaways

  • Review auto-renewal, termination deadlines, egress thresholds and migration-fee clauses; the report says existing contracts do not automatically adopt new terms.
  • Assess APIs, data formats and identity or IAM dependencies alongside fee clauses because technical lock-in may remain.
  • Test a critical workload and check whether its exported data is readable in an open format without tool-specific translation.
  • Distinguish cross-provider switching from transfers between regions or availability zones within one provider, which the report says may remain billable in practice.

Practical tips

  • Review contract terms and notice deadlines ahead of renewal.
  • For the selected workload, document responsibility for assessing APIs, formats, IAM dependencies and exported data.
  • Verify the current legal wording and status of the reported deadline and scope before using them to guide a contract decision.

Use the next renewal as a decision point

Review the exit clauses and select one critical workload for a practical reversibility test before deciding whether to preserve the ability to move, accept continued dependence or schedule remediation.



Related Posts

Contact

Slovak Republic+421911948347

DATATIP, s.r.o.
Alžbetina 30
Košice 040 01
Company ID: 36869112
VAT ID: SK2023131594
IBAN: SK80 8330 0000 0022 0024 5482

Czech Republic+420773926377

DATATIP CZ, s.r.o.
Pelušková 1443
Praha 198 00
Company ID: 24853577
VAT ID: CZ24853577
IBAN: CZ81 2010 0000 0023 0033 8790

Privacy Preference Center