By KYN AI Advisory Team — AI implementation specialists, Singapore
You can leave an AI agent vendor cleanly only if four things are settled before you sign: your data exports in a standard format, you own the cloud account the system runs in, you hold rights to the custom code and configuration, and the contract names a handover period. If any of the four is missing, the vendor holds leverage at renewal. Write the exit plan on day one, test the export in the first quarter, and refresh both each year.
Why plan an exit before you start?
Switching cost is the vendor's pricing power. The more of your operation sits in a system you cannot move, the less you can say no at renewal. Vendors are rarely hostile about it. A vendor can close, change its pricing, be acquired or stop supporting the product you rely on. Any of those makes you a leaver, not by choice.
An exit plan costs little when written early. It costs a great deal when written during a dispute.
What are the four assets you must be able to take?
- Data. Records, files, logs, and the history of what the agents did.
- Configuration. Prompts, rules, workflows, templates, thresholds. This is where your business logic lives.
- Code. Custom integrations, scripts, the front end.
- Infrastructure. The cloud account, domain names, API keys, sender identities, phone numbers for messaging.
Most buyers ask about the first and forget the other three. Without the configuration, a data export gives you records and no process. Without the infrastructure, you can read your records and cannot run anything.
Which questions should you ask before signing?
| Area | Question | Acceptable answer | |---|---|---| | Data | What formats can I export, and can I do it myself? | CSV or JSON of every table, plus files, on request or self-service | | Data | Does the export include history, logs and attachments? | Yes, all of them | | Configuration | Is it exportable as readable files? | Yes, prompts, rules and workflows in text form | | Code | Who owns the custom code? | You, on full payment, stated in the contract | | Infrastructure | Whose name is on the cloud account, domain and sender identities? | Yours | | Credentials | Can I rotate every key the vendor holds? | Yes, and the vendor lists them | | Handover | How long and at what rate? | A stated period and day rate or a fixed fee | | Termination | What happens to my data after exit? | Returned, then destroyed, with written confirmation |
If an answer starts with "we can discuss that at the time", record it as no.
What does a clean handover look like?
A handover is a short project with a date. Ask the vendor to commit to this sequence in the contract.
- Notice. A defined period, for example one or two months, which you choose in the contract.
- Inventory. The vendor lists every resource, account, key, domain and third-party service in use.
- Export. Full data and configuration export, checked by you against record counts.
- Parallel run. The new system or team runs beside the old for a set period.
- Cutover. Credentials rotate, the vendor's access is removed, and DNS or sender identities move.
- Destruction. The vendor deletes remaining copies and sends written confirmation.
Test step 3 early. Ask for a trial export in the first quarter and count the rows. A mismatch found in month 3 is cheap to fix. One found at termination is not.
Why does cloud account ownership settle most of this?
When the system runs in a cloud account in your name, the data, files, logs, databases and credentials are already yours. The vendor holds a role you granted, and you can revoke it. The system keeps running when the vendor leaves, because nothing was ever moved into the vendor's account.
When the system runs in the vendor's account, exit is a migration. You depend on their export tooling and their goodwill, and everything must be copied out before access is cut.
Ask this one question first: "If I revoke your access today, does anything stop working?" The right answer is no. See where an agent's data is stored for the data side of the same question.
What about the models and prompts?
Vendors often present prompts and agent logic as proprietary. For you, they are the encoded form of your business rules, and you need them.
- Ask for prompts, rules and workflow definitions as files you can read.
- Ask that they sit in a repository in your account, with history.
- Ask for the test set used to check them. Without it, a replacement team cannot tell if its version behaves the same.
- Confirm that the vendor's own reusable components are licensed to you in perpetuity or are replaceable. A licence that ends at termination turns a feature into a hole.
A model provider is a separate dependency. If the system calls a model through your own account, you keep the account. If it calls through the vendor's account, you will need a new account and new keys at exit.
What should the contract say?
Check eight clauses.
- Ownership of custom code and configuration, effective on full payment.
- Ownership of data, including derived data such as classifications and summaries.
- A named export right in an open format, with a time limit for delivery.
- Handover assistance, with duration and rate.
- Return and destruction of data, with written confirmation.
- Continuity if the vendor ceases trading: source code or access in escrow, or the system already in your account.
- Notice and renewal terms, so a long minimum term does not trap you.
- A list of sub-processors, with notice of changes.
Singapore's PDPC expects organisations to remain responsible for personal data that a vendor processes for them, so keep the destruction confirmation on file.
What should you test each year?
Make the plan a living document.
- Export test. Run the export, count rows, open the files.
- Access list. Who holds credentials, including the vendor's staff? Remove those no longer needed.
- Restore test. Can the data and configuration rebuild a working copy somewhere else?
- Dependency map. Which third-party services, domains and sender identities would you need to move?
An hour a quarter is enough for a small system. The aim is to know, with evidence, how long an exit would take.
What does a vendor-friendly exit cost?
Expect honest vendors to charge for handover time. That is fair. Compare the cost with the alternative: a refusal to export, a forced re-entry of records, or a rebuild from scratch. Ask for the handover rate before you sign, when you have bargaining power.
Where KYN fits
KYN builds every system in a cloud account in the client's name. Rights in the custom code and configuration pass to the client on full payment. The client can revoke KYN's role and everything keeps running. Pricing is a one-off build fee, then a monthly retainer for changes, monitoring and fixes, with a minimum of twelve months, quoted after the review.
For a manufacturer, we moved eleven systems onto three on one AWS account and moved 10,210 vendor quotes into it, so the client holds the records and the infrastructure. The first 14 days are a review of your stack and interviews with your team. A full build ships in under 90 days. See infrastructure and pricing.
Frequently asked questions
Who owns the data an AI agent creates?
It should be you, and the contract should say so, including derived data such as classifications, summaries and drafts. Confirm this in writing. Also confirm that the vendor does not retain copies for its own use after exit.
What if the vendor goes out of business?
If the system runs in your own cloud account, it keeps running and you hire another team to maintain it. If it runs in the vendor's account, you depend on escrow or an export you took earlier. This is the strongest argument for testing an export each year.
How long does a handover take?
It depends on the size of the system, the number of integrations and how clean the export is. A small system with documented configuration can move in weeks. Ask the vendor for an estimate in writing and compare it with your own test.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
