Migrating from Merge
How Merge Agent Handler's connectors and linked accounts map to Arc0, whether tokens can move, and the free migration offer.
Merge Agent Handler and Arc0 both give agents authenticated access to the apps your users have connected. If you also use Merge's Unified API for normalized HR, recruiting or accounting data, that's a separate product from Agent Handler and can stay exactly where it is — this page is about moving agent connections, not data sync.
How the concepts map
| Merge Agent Handler | Arc0 |
|---|---|
| Connector | App |
| Linked account | Connection |
| End user | Connected user |
A Merge connector and an Arc0 app both stand for the third-party service — Gmail, Salesforce, Zendesk. A linked account is one end user's authorized account under a connector, which is what Arc0 calls a connection; the end user is who you identify that account as in your own system. Merge's own connectors, plus the vendor MCP servers it lists alongside them, map to apps in Arc0's catalog the same way — one app, whichever service is behind it.
Can you move your tokens?
If your Merge connectors use your own OAuth apps and Merge's API can export the underlying tokens for a linked account, those connections can move into Arc0 without a reconnect. Otherwise, your users reconnect once, through Arc0 Connect, which carries your brand and, on paid plans, your own domain.
Staging the reconnect
Point new users at Arc0 Connect from the start, and prompt existing users to reconnect the next time their agent needs that app, rather than all at once. Reconnecting is also the moment to move a linked account off a Merge-managed OAuth app and onto your own, if you want the provider's consent screen to name you going forward. An engineer helps set this up as part of the free migration — see Migrating to Arc0.
Swapping your agent's calls
Point your MCP client at your Arc0 MCP endpoint, https://mcp.arc0.ai/u/{user}, or swap the SDK
call that runs an action for arc0.actions.run('salesforce.update_record', { user, input }).
Actions are named app.action, each carrying a read, write or destructive scope for your
policies. See Arc0 MCP and SDK.
The offer
Every Arc0 plan includes a free, engineer-led migration, covering the mapping above and the staged reconnect.
Contact us to start your migration.
Next
Migrating from Composio
How Composio's toolkits, auth configs and connected accounts map to Arc0, whether tokens can move, and the free migration offer.
Migrating from Pipedream Connect
How Pipedream Connect's external users and connected accounts map to Arc0, whether tokens can move, and the free migration offer.