From 12 January 2027, providers of data processing services may no longer impose switching charges on customers for the switching process. Until then they may charge reduced switching charges that do not exceed their costs directly linked to that process. That is Article 29 of Regulation (EU) 2023/2854, the EU Data Act, which has applied since 12 September 2025.
A cloud exit in 2027 still has plenty of costs attached. Normal usage during the transition, the consequences of ending a contract early, your own migration work, running two platforms in parallel and the destination service are all separate cost blocks. Two things have also moved since the regulation was adopted: the large providers have published their own programmes for data transfer when switching and during parallel use, and a Commission proposal to amend the Data Act is going through the legislative process. FinOps and procurement should pull the cost blocks apart now, rather than filing every amount under "egress fees".
What goes away in 2027, and what does not
Article 2 defines switching charges as charges other than standard service fees or early termination penalties. Article 29 therefore covers only what the source provider charges for the switching process itself. Article 34 deals with a second case: where a service is used in parallel with another, providers may impose data egress charges, but only to pass on the egress costs incurred, without exceeding them.
| Cost block | Position from 12 January 2027 | Evidence to review |
|---|---|---|
| Source-provider switching charge | Must not be imposed for the switching process (Art. 29(1)) | Contract, price list, final invoice |
| Data egress during parallel use | At most the costs incurred (Art. 34(2)), already since the regulation began to apply | Provider programme, request, credit |
| Normal usage during transition | Remains a standard service fee | Usage data and transition schedule |
| Early termination | Not removed by Article 29 | Termination and commitment clauses |
| Customer migration programme | Remains the customer's cost | Delivery plan, internal effort, supplier quotes |
| Destination platform and re-architecture | Remain part of the business case | Target architecture and target rates |
| Parallel running | Remains real duplicate consumption | Cutover plan and technical dependencies |
Article 29 also requires providers to state standard service fees, early termination penalties and any reduced switching charges before the contract is signed, and, where relevant, to tell customers which services are highly complex or costly to switch, making that information public where applicable. Those disclosures are your first piece of evidence. Without this classification there is no way to check later whether a fee was booked correctly, or whether the migration paid off the way the business case assumed.
The deadlines that shape an exit plan
Article 25 sets out which periods a contract for a data processing service must contain. Four timelines matter for the cost plan:
| Period | What Article 25 provides | What it means for the cost plan |
|---|---|---|
| Notice to start switching | At most two months (Art. 25(2)(d)) | Earliest start date; normal fees run until then |
| Transitional period | At most 30 calendar days (Art. 25(2)(a)) | The window in which source and destination costs can overlap |
| Alternative if technically unfeasible | Notice within 14 working days, alternative of at most seven months (Art. 25(4)); separately, the customer may extend the transitional period once (Art. 25(5)) | Model a scenario with longer duplicate running |
| Data retrieval after transition | At least 30 calendar days (Art. 25(2)(g)) | Keep source storage in the plan until erasure is confirmed |
These legal periods are not the same as the overlap engineering needs for a safe cutover, and the two are easy to confuse. Have legal and engineering lay both timelines side by side. Article 31 also exempts certain services from parts of the regime, such as custom-built services not offered at broad commercial scale through the service catalogue (where Article 29, among others, does not apply) and time-limited non-production versions for testing and evaluation. Providers must say before signing which obligations do not apply. Whether a given service falls under that exemption is a question for legal.
What providers already offer
The three hyperscalers have published their own programmes. They are voluntary offers with their own conditions, not interpretations of the regulation, and they can change:
| Provider | Programme | Conditions as stated by the provider |
|---|---|---|
| AWS | Free Data Transfer Out Program for Switching Customers | Moving all data, or all data of one service, off AWS; request through support at least two months before the switch starts; temporary credit for data transfer only; CloudFront, Direct Connect, Snow Family and Global Accelerator excluded; customers eligible for the EU Data Act Addendum or the UK Customer Switching and Portability Addendum can request reduced transfer rates for eligible use cases |
| Microsoft Azure | At-cost data transfer for parallel use | Billing address in the EEA, EFTA or the UK; support request with subscription ID, the external endpoint's ASN and an estimated share of traffic; refund on the next bill; destination must belong to the same organisation; UK customers transferring from UK datacentres also covered over the Microsoft network |
| Google Cloud | Data Transfer Essentials | For customers in the EU and the UK, for parallel processing across providers; opt-in by configuration; qualifying traffic metered separately and billed at zero |
For FinOps this means some transfer cost can come down before 2027, but only on request, with deadlines and with evidence. Miss the request and you will see standard egress rates on the invoice, which are hard to reclassify as switching cost afterwards. UK teams should note that all three programmes name the UK explicitly, although the Data Act is an EU regulation.
What may still change
On 19 November 2025 the Commission adopted the Digital Omnibus proposal COM(2025) 837, which would amend the Data Act among other acts. Its recitals describe lighter regimes for certain services other than IaaS provided under contracts concluded on or before 12 September 2025: services customised to a particular customer, and services from SME and small mid-cap providers, together with a clarification on proportionate early termination penalties in fixed-term contracts. The same recitals say these regimes should not undermine the gradual withdrawal of switching and egress charges. According to the EUR-Lex procedure page, the procedure is still ongoing on 10 October 2026; until anything is adopted, the regulation applies as published.
Separately, the Commission has published non-binding standard contractual clauses for cloud computing contracts, covering switching and exit, termination, and security and business continuity among others. Its page lists them as a draft recommendation of 19 November 2025, last updated 3 March 2026. For procurement they are a benchmark to compare against, not an obligation.
Review the contract before the invoice
Whether and how these rules apply to a particular agreement is for your lawyers. The cost analysis cannot wait for that, so record at least these fields per agreement:
- service, contracting entity and date the contract was concluded;
- notice period, maximum transitional period and data retrieval period;
- standard service fees during transition;
- stated switching charges and their calculation basis;
- commitments, minimum spend and early termination;
- exportable data and digital assets named in the contract;
- applicable provider programmes, request deadline and evidence;
- link to the provider's current information and review date.
The conclusion date is new on the list because the Omnibus proposal hinges on 12 September 2025. Where a line is disputed, legal or procurement check it against the agreement and the regulation; an internal cost-centre label is not enough to call something a switching charge.
Model exit as a separate cost scenario
An exit case becomes useful once it compares three scenarios over the same functional scope and period: continue, switch and renegotiate. Keep one-off costs apart from the run rate. A target platform may be cheaper to run and still take a while to earn back the migration and any stranded commitments. A team may also accept a higher run rate for lower risk or better portability. That is a legitimate choice, as long as it is recorded as a decision and not presented as a saving.
| Model field | What it contains |
|---|---|
| Evaluation period | One common period for all scenarios |
| Source cost | Usage, support and normal fees until the end of data retrieval |
| Switching charges | Only charges attributed to the switching process, dated before or after 12 January 2027 |
| Transfer | Data volume, programme, request status and expected credit |
| Customer programme | Engineering, data validation, testing, security and programme work |
| Parallel run | Duplicate usage, support and licences |
| Residual commitments | Minimum spend or discounts that continue after usage moves |
| Destination cost | Usage, support, operations and new commitments |
| Uncertainty | Named assumptions with owners, not an arbitrary percentage |
If you report in GBP while the provider bills in EUR or USD, fix the exchange-rate method for all three scenarios before comparing them.
Set measurement points before cutover
Without a baseline, every cost change after the migration becomes a debate. Close at least one full billing period first and keep service quantities and the cost definition, actual, amortised and effective cost, open commitments, the data volume to export, and the performance and availability requirements used for comparison. Agree, too, on when the switch counts as finished: with confirmed erasure after the retrieval period, not at cutover.
Reconcile the final invoices
After cutover, reconcile five things:
- The final source bill against usage, contract end and the retrieval period.
- Any switching charge against the agreement and the applicable date.
- Transfer credits against the request and the actual volume.
- Residual commitments against the list recorded before the move.
- The first destination bill against the approved architecture and prices.
Give every variance an owner and a class: quantity, price, architecture, timing, one-off migration or unresolved. The switch then stays visible as a switch in the monthly report.
Checklist before 12 January 2027
- Inventory contracts with their conclusion dates and the providers' pre-contract disclosures.
- Separate switching charges from normal usage, data egress and termination costs.
- Expose commitments that run beyond January 2027.
- For parallel use, check which provider programme applies and file the request.
- Rehearse export of data, formats and dependencies on a limited scope.
- Define the baseline, the completion criterion and the reconciliation.
- Have legal recheck the Omnibus procedure at the next contract renewal.
None of this argues for switching in a hurry. It gives you an exit model someone else can review. A move into a separate sovereign partition raises the same comparability questions; see AWS European Sovereign Cloud: the cost questions before a migration.
What Costfluent covers
Costfluent reads AWS, Azure and Google Cloud billing data. Cost reports grouped by provider, account or service keep source and destination cost comparable across one period before and after cutover when both sides are on those providers, and a budget scoped to the migration's cost segment, set through the Public API or the Terraform provider, compares actual spend with the plan. The docs introduce the reports in the cost reports overview. Costfluent does not review contracts, switching charges or transfer requests. How sovereignty questions translate into cost evidence is covered under sovereignty.
Sources and method
Checked on 2026-10-10. Regulation (EU) 2023/2854, especially Articles 2, 25, 29, 31, 34 and 50; EUR-Lex: procedure 2025/0360 (COD); proposal COM(2025) 837; European Commission: standard contractual clauses for cloud computing contracts; AWS: Global Network FAQ and Amazon EC2 FAQ, Free Data Transfer Out Program for Switching Customers; Microsoft Learn: Azure data transfer fees; Google Cloud: Data Transfer Essentials (10 September 2025). The tables, cost model and checklist are Costfluent recommendations, not legal advice; applicability, contract interpretation and disputes require qualified legal review.



