Agent migration

What it is

Companies that built their own studio, catalogue or touring tool rarely leave it because the migration is weeks of work. Aden is already callable end to end, so that work can be done by an agent the company already pays for: Codex, Claude, a ChatGPT agent, Grok.

What was missing was not capability, it was instruction. /migrate.md is the brief: the order of work, the endpoint each step writes, and the rules the agent must not break.

Using it

1. Open /migrate, or the role page (/for/studios), and copy the prompt.
2. Paste it into your agent along with access to your current tool.
3. The agent reads the brief, connects over MCP, and works block by block.
4. Approve each block before it starts the next one.

Order of work

Blocks run in dependency order: a track needs its team, a file needs its version, an invoice line needs the session it bills for. People, catalogue, audio, sessions, events and tours, contacts and deals, splits, money, open work.

The leftovers report

Aden will not have a home for every field a source holds. The brief requires the agent to collect those as leftovers.csv rather than guess a mapping or park the value in a notes field. That file is the honest output of a migration and the best signal we get about what to build next.