Migrating to Arc0
What Arc0's free, engineer-led migration covers, the generic steps to move from another platform, and the Composio switching offer.
Moving an agent's connections between platforms is usually the hard part of switching, not the agent code itself. Every Arc0 plan, including Build, includes a free migration run by an Arc0 engineer, so you're not doing the mapping and staging alone.
What's included
- Mapping apps and actions — turning your current platform's apps and tool calls into Arc0
apps and
app.actioncalls, e.g.gmail.send_email,salesforce.delete_record. - OAuth apps — setting up your own OAuth apps with providers, if you want the provider's consent screen to name your product from day one instead of Arc0's.
- Branded Connect — configuring Arc0 Connect with your logo, colors and, on paid plans, your own domain, so the flow your users see doesn't change.
- Token import — where your current platform's API can export the underlying tokens, moving them directly into Arc0 so connected users don't have to reconnect.
- Staged reconnects — for everything that can't be imported, a plan for prompting users to reconnect in-product rather than all at once.
How it works
Tell us your setup
Contact us with which platform you're on, roughly how many connected users and apps you have, and any OAuth apps you already own.
We map your apps and actions
An engineer matches your current apps and calls to Arc0 apps and actions, and flags anything that doesn't have a direct match.
Set up Connect and OAuth apps
We configure Arc0 Connect with your branding and, if you want them, your own OAuth apps, so providers show your name on the consent screen from the first connection.
Import tokens where we can
If your current platform's API returns tokens, we import them directly — no reconnect needed for those users.
Stage the reconnect for everyone else
New users connect through Arc0 from the start. Existing users who can't be imported are prompted to reconnect the next time their agent needs that app, instead of a single mass-reconnect email.
Checklist
Before you talk to an engineer, it helps to have:
- The list of apps and actions your agent uses today.
- Any OAuth apps you already own, and which providers they're registered with.
- Whether your current platform's API can export tokens, or whether users will need to reconnect.
- The read, write and destructive rules you want live on day one — see Policies.
- A rough plan for telling users why they're being asked to reconnect an app.
Switching from Composio
Composio's plans for customers who signed up before 15 August 2026 reprice on 31 December 2026. Teams moving from Composio get their first 3 months of Launch free, on top of the standard migration above. See From Composio for how the concepts map and what moving looks like.
Ready to start? Contact us and we'll schedule the engineer who runs your migration.
Next
Security and compliance
How Arc0 stores and encrypts credentials, what data it does and doesn't keep, its compliance posture, and where to report a vulnerability.
Migrating from Composio
How Composio's toolkits, auth configs and connected accounts map to Arc0, whether tokens can move, and the free migration offer.