Exactly what the migration tool moves, platform by platform

Migration Studio is the wizard that moves a client from their old CRM into an AgentiCRM workspace. Five steps: Connect, Scan, Map, Import, Verify.

The five steps 1. Connect. You paste the credentials for the source platform and pick the destination workspace. 2. Scan. We count every object in the source so you see the real size of the job before anything moves. 3. Map. Fields are auto matched. Anything without a native match can be created as a custom field, or set to skip. 4. Import. Live progress, batch by batch, with pause, resume and cancel. Safe to close the tab. 5. Verify. A report of imported counts, skipped duplicates and errors, plus a seven day rollback.

What comes across - Contacts, with names, emails, phones, addresses and source - Companies and their links to contacts - Tags and segments - Custom fields, created for you where there is no native match - Opportunities and deals, with pipelines and the correct stage - Pipelines and stage order - Tasks, open and completed - Notes, with their original timestamps - Appointments and calendar history - Conversation history, email and SMS threads, reattached to the right contact - Attachments and files, copied into AgentiCRM storage

What does not come across automatically - Automations, workflows and campaign builders. Every platform stores these in its own private format. We rebuild them, see the automations article. - Funnels, landing pages and websites. We rebuild these in Funnel Studio, usually faster than exporting them. - Call recordings held by the old provider. Your Twilio or provider account keeps those. - Billing, subscriptions and payment tokens. Those live with the payment processor, not the CRM. - Platform specific gadgets that have no AgentiCRM equivalent. We will name them at the scan stage rather than let you find out later.

What we need from you, per platform - GoHighLevel: a Private Integration Token with all scopes ticked, plus the Location ID. - HubSpot: a private app token with CRM read scopes, or an owner login for the OAuth connect. - Zoho CRM: connect the Zoho account through the connector, or a token with CRM read scope on the relevant modules. - Pipedrive: an API token from the account owner and the company domain. Always take these from the account owner, not a limited seat, or objects will silently be missing.

Duplicates and matching We match on contact ID first, then email, then phone. During the import the source platform wins. After the import AgentiCRM wins, so your team can start editing immediately.

Names and formatting Names are corrected to proper casing on the way in, so lower case exports do not land as lower case records.

How long - A small client, under five thousand contacts, is usually done within the hour. - A large client with full conversation history and attachments can run several hours. It runs in the background. - A book of forty clients is normally worked through in batches over two to four weeks, in whatever order you choose.

If something looks wrong Rollback removes every record that run created, and nothing else, for seven days. We stamp every write with the run ID, so a rollback never touches data that was already there. Fix the field map, re run, done.

Keep in sync After a successful import you can turn on keep in sync. New and updated contacts in the old platform flow through to AgentiCRM by webhook until the client fully cuts over.

Who runs it MAP Platform runs migrations for AgentiAce seat holders at our cost. You can also run one yourself from Settings, Migrations, whenever you prefer.