---
title: "Who owns your AI agent | StudioChat"
description: "The five assets of an agent in production and which side of the move each one ends up on if you switch provider. Three switches, no hedging."
url: https://studiochat.io/who-owns-your-agent
locale: en
translations: { es: https://studiochat.io/es/who-owns-your-agent.md, pt: https://studiochat.io/pt/who-owns-your-agent.md }
site: https://studiochat.io
---

Tool

# Moving your agent

The five assets, and the three destinations they can land in when you change provider: it moves whole, it arrives as a dead file, or it stays behind. Flip the three switches and watch them rearrange.

the number is in my nameI have a history exportthe source documents are mine

**1 of 5 move.** Two or more stay behind, and that is the cost of leaving that appears in no contract.

**WhatsApp number:** The account is in the provider's name. The number every one of your customers has been writing to stays with them, and telling everybody about a new number costs more than the rest of the move put together.

**conversation history:** With an export it arrives, but it arrives as a file. A spreadsheet of conversations is not memory: the new agent cannot use it to know what happened to that customer last month without processing all of it again.

**agent instructions:** The content is yours and you take it as text. But it is written against that platform's tools and limits, so on the other side it has to be rewritten. The decision moves, the implementation does not.

**knowledge base:** The source documents are yours, so it moves whole. It is the most portable of the five and the one carrying the most of your own work.

**integrations with your systems:** They never move. They are built against that provider's platform. On the other side they get rebuilt, and that is the real cost of leaving that nobody quotes at signing.

## The model, in the open

The three switches describe configuration decisions rather than contract clauses: which business portfolio holds the WhatsApp account, whether a history export exists, and who owns the source documents. The WhatsApp account rule is the platform's and is documented by Meta; the rest comes from what we see entering and leaving implementations.

## How to read it

* Leave the number on the provider's side, which is the common case, and look at what stays. Telling every customer about a new number costs more than the rest of the move put together.
* Notice that two assets do not move for any switch. The instructions arrive as text that has to be rewritten, and the integrations get rebuilt entirely: that is the cost of leaving nobody quotes at signing.
* The four questions to ask before signing fall out of this on their own, and all four can be answered in one meeting.

This object is the interactive half of an article: [What a company keeps if it switches AI agent providers](/blog/que-se-lleva-la-empresa-si-cambia-de-proveedor)

## The playbook already exists. We multiply it.

[Talk to us now](https://cal.com/studiochat)

[Book a demo](https://cal.com/studiochat) [Or write to hey@studiochat.io](mailto:hey@studiochat.io)