What changes in January 2027, and why it is a staffing question
This section is on no competing page, and it carries a date about fifteen weeks out.
Article 29 of the EU Data Act states that from 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process. Between 11 January 2024 and that date, providers may impose reduced charges, capped at the costs directly linked to the switching process.
Read as a technical brief rather than a legal one, that puts four things in your backlog.
An exit plan that exists as a document, naming what moves, in what order, and how long it takes.
A data extraction path that has been tested, not assumed, including the large datasets everybody forgets.
Infrastructure as code that is genuinely portable, which usually means knowing precisely where you depend on one provider and having decided that on purpose.
Contract terms that match the new position, which is a conversation for your legal team rather than this page.
None of that is free, and all of it is engineering work. If you are in the EU, this is the clearest new source of cloud engineering demand between now and next spring. If you are not, the same four items are what you will want the first time your provider changes its pricing, so the deadline gives you a reason to do work that was always sensible. Our comparison of cloud versus on-premises infrastructure covers the related question of what should move back.
This is not legal advice. Check your own contracts and take advice for each market.
Case study slot — not for publication yet
Recommended Action is a niche cloud talent augmentation piece. I have shipped the guide without a client story rather than invent one, and held the slot open here. It goes after the access H2 and before the January 2027 section, 250 to 350 words, under an H2 such as What a cloud engagement looks like in practice.
This page is the one where a measured number would be worth most. The Flexera figure gives readers a benchmark, so a real cost reduction stated as a percentage of monthly spend, with no client name and no absolute figure, is both credible and safe to publish.
Six sentences from you and I will write it: sector, cloud platform, the roles and mix placed, engagement length, what the access model was, and the measurable outcome. Labelled as a typical engagement, no invented numbers.
