The European Commission adopted model contractual terms on 29 October 2026 to help put data-sharing and cloud-switching rights into agreements. Published in the Official Journal on 6 November, the recommendation offers voluntary cloud clauses that parties can adapt while remaining subject to mandatory EU and national law.2
The clauses distinguish switching costs from ordinary service fees and possible early-termination penalties. They also address assistance, business continuity, security and the timetable for moving a workload. Their commercial purpose is to express the parties' responsibilities before an exit is attempted. The models do not certify that a particular customer has completed a migration successfully.2
France separates switching from parallel cloud use
France's communications regulator, Arcep, adopted guidance on 2 July 2026 separating costs associated with switching from data-transfer costs when customers use multiple clouds simultaneously. Its stated objective is:3
une plus grande liberté de choix de services cloud.
Greater freedom to choose cloud services.3
Arcep separately records France's earlier decision to set the maximum charge for data transfer during a provider change at zero. It distinguishes that charge from other switching costs and from transfers between clouds used in parallel. Consequently, a customer comparing contracts needs to identify which activity is being charged, rather than treating every transfer as the same service.3
Google separates the stages of an exit
Google Cloud's current service terms illustrate how a provider translates the framework into a process. Its EU Data Act section applies to specified data-processing services where the customer's billing address is in the European Economic Area. Customers must submit an exit notice through the prescribed form and supply relevant destination-provider information.4
The terms distinguish intake, initiation, migration and data-recovery stages. Google may extend the migration period where it explains technical infeasibility within the required notice process, and the customer can also request a longer period. The terms cover both another provider and the customer's own infrastructure. They are contractual provisions, rather than a regulator's finding that every migration satisfies the law.4
Databricks ties termination to completion notices
Databricks' published addendum uses a written switching notice and requires customers to identify their chosen destination or request erasure. It commits the supplier to reasonable assistance, business continuity and maintaining agreed data security. Customers remain responsible for importing their data into the destination environment.1
The addendum also requires notification when switching succeeds. If the customer fails to initiate the switch or report completion within the relevant period, it treats the notice as withdrawn and keeps the agreement in force. Separate payment provisions preserve obligations concerning service fees and early termination. These terms illustrate why a legal right to switch still requires attention to notices, completion and the treatment of outstanding commitments.1