An exit strategy for AI: how a local authority switches supplier or model without starting over

By · Updated · 3 min read

Short answer

An AI application binds an organisation at four points: the model, the data and sources, the prompts and configuration, and the logs. Whoever does not arrange that up front is stuck after three years with a supplier who sets the price. The Data Act has required cloud services to enable switching since 12 September 2025 and bans switching charges from 12 January 2027. Open-weight models make the exit practical: the model is a file you own.

Where the binding is

ComponentThe bindingWhat you record
ModelA closed model exists only at the provider; if it disappears, the output changesOpen-weight, or at least a replacement plan with a test set
Data and sourcesDocuments, indexes and enrichments in a supplier’s own formatExport in open formats, including metadata, on request and at contract end
Prompts and configurationRoles, instructions, connections and templates that determine behaviourOwned by the authority, exportable as text
LogsThe audit log you need for the AI Act and records lawExport in a readable format, retention independent of the contract
ConnectionsIntegrations with the case system and office softwareOpen standards, documented interfaces

What the Data Act requires

The European Data Act has applied since 12 September 2025. Providers of data processing services, including cloud services, must enable switching to another provider or to on-premises infrastructure, with a transition period and an export obligation. Switching charges may only be cost-based until 12 January 2027 and are banned after that. Contracts must state the exit terms explicitly. That helps, but it does not cover the model itself: a closed model does not come with you.

See Procuring AI as a local authority for the tender and Assessing an AI supplier for the questions to ask.

The exit plan in five points

  1. Test set. A fixed set of questions and documents with approved answers, with which you can assess any replacement model. See Comparing open-weight models.
  2. Annual export drill. Request the export, load it somewhere else and check that everything is there. An exit that has never been rehearsed does not work.
  3. Ownership in the contract. Prompts, configuration, indexes and logs belong to the authority, in open formats, at no cost at contract end.
  4. Transition period. At least six months of continued service after termination, with migration support.
  5. No silent changes. Model changes and changes to terms are notified in advance, with the right to refuse or leave.

How werqly fits in

werqly works with open-weight models: the model is a file on the authority’s node that you take with you. Sources, roles, prompts and the audit log are exportable in open formats. With a node in your own building the hardware is the authority’s; with werqly Cloud the move to your own hardware is a migration, not a rebuild. See AI for local government.

Frequently asked questions

Questions on this topic

What does the Data Act change for AI contracts?

Since 12 September 2025 cloud providers must enable switching and include exit terms in the contract. Switching charges are banned from 12 January 2027. The model itself is not covered: a closed model stays with the provider.

Why do open-weight models make an exit easier?

Because the model is a file you own and can run on other hardware or with another service provider. Your prompts, sources and test set keep working; with a closed model you start again.

What belongs in the contract as a minimum?

Ownership of prompts, configuration, indexes and logs; export in open formats at no cost; a transition period of at least six months; advance notice of model changes and changes to terms; and an annual export drill.

How do you test whether the exit works?

Request the full export every year, load it into a test environment and run the test set. If the answers match and all logs and sources are present, the exit works. Otherwise that is the moment to amend the contract.

Sources

  1. Data Act — Regulation (EU) 2023/2854
  2. European Commission — Data Act explained

This article is general information, not legal advice. Rules and guidance change; check the sources listed or ask your lawyer or DPO if in doubt.

About the author

Tim Hoogstrate

Founder of werqly

Tim Hoogstrate is a software developer and the founder of werqly. He writes the articles in the knowledge base: what the GDPR, the AI Act and sector rules require when you use AI, and how to arrange that in an environment of your own.

Calculate your private AI costs.

Enter your work email and number of employees. We work out four setups for you straight away: in your own server room or in our datacentre, self-managed or with werqly Pro management. werqly is not a cheap AI subscription: you pay for your own hardware and full control.

  1. 1Enter your email and number of employees
  2. 2Compare four proposals
  3. 3Request a quote straight away

We email the calculation to this address and use it only to contact you about your request.

A no-obligation quote for your own AI node, in your inbox within a minute.

Request a quote →