How it works · Flow F17

Move your CRM and support history in a weekend, with a way back

Connect the source, approve AI-proposed mappings, dry-run, reconcile, cut over with a final delta sync, and keep a rollback window with export.

What the Switch to One3 in a weekend flow does

For agencies, migration is the sales motion: customers switch when their history, pipelines, conversations and automations move safely.

You connect the source — for example GoHighLevel, HubSpot, Zoho CRM, Freshdesk or CSV. One3 profiles it and proposes field, pipeline, status and user mappings with a confidence score. A human approves the mapping. A dry run writes nothing and reports row counts and errors. You fix and re-run. A reconciliation report compares source and One3 counts, samples and attachments.

At cutover, source writes are frozen and a final delta sync runs. A rollback window with export stays open. After cutover, the Connector Health Center checks connectors and automations. Marketing consent and suppression lists migrate with the data; a contact without consent is flagged "no marketing".

Migration Factory v0 (CSV and HubSpot) is planned for W1; GoHighLevel and Zoho paths for W2. Access to each source is a verify item.

Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.

Switch to One3 in a weekend, step by step

Eight steps, with a weekend playbook for agencies.

1
1. Connect the source
**Platform · Migration Factory · Integration Hub.** GoHighLevel, HubSpot, Zoho CRM, Freshdesk, Pipedrive or CSV/XLSX (verify access per source).
2
2. AI-proposed mapping
**Migration Factory · Mapping Studio.** Field, pipeline, status, tag, owner and custom-field mappings, each with confidence and a reason.
3
3. Human approves the mapping (R2)
**Human gate.** Mappings are never auto-applied.
4
4. Dry run
**Migration Factory.** No writes. Row counts, errors by type, unmapped fields and estimated duration.
5
5. Fixes and re-run
**Agency admin.** Mapping is adjusted until the report is clean.
6
6. Reconciliation report
**Migration Factory.** Counts per object, sums such as deal amounts per stage, a 1% sample diff (minimum 20 records) and orphan checks.
7
7. Cutover
**Migration Factory.** Freeze source writes, run a final delta sync, go live.
8
8. Rollback window and health check
**Connector Health Center.** Export and delete-by-migration-id rollback stay available; connectors and automations are health-checked.

Weekend playbook (template)

When	Step
T–7 days	Discovery: source tools, sub-accounts, integrations, automations
T–5	Connect sources, profile data, build a mapping template on one pilot sub-account
T–3	Dry run on the pilot, fix mapping, reconciliation sign-off
T–2	Rebuild top automations and templates; connect WhatsApp and email; set up white-label
Friday evening	Freeze source changes; migrate all sub-accounts in batches
Saturday	Reconciliation reports per sub-account; fix exceptions
Sunday	Go-live checklist; client portal invitations prepared
Monday	Hypercare through Service Desk with priority SLA

Launch gate

No agency or ICP launch until its top two incumbent migration paths — GoHighLevel and HubSpot for agencies — are tested on realistic data, with a successful rollback test.