Platform · Migration
Switch to One3 in a weekend, with every record accounted for
The Migration Factory is designed to move contacts, pipelines, conversations, files and custom fields from your current tools, with a dry run, a reconciliation report and a rollback before you go live.
Why migration comes first
For agencies and growing businesses, migration is the sales motion. Teams switch tools when their contacts, pipelines, conversations, automations, files and reports move safely. They do not switch for a vision alone.
One3 treats migration as a product, not a services project. The Migration Factory is planned as a standard, repeatable pipeline with the same steps for every source:
- Connect the source or upload a file.
- Profile the data and map it, with AI suggestions a person approves.
- Test with a dry run that writes nothing.
- Execute in batches, then reconcile source against One3.
- Sign off, or roll back.
The Migration Factory works with the Connector Health Center, which checks connectors and automations after cutover.
Planned sources and waves
| Priority | Source | Data scope | Planned wave |
|---|---|---|---|
| P0 | CSV, XLSX, Google Sheets | Any object | W1 |
| P0 | HubSpot | Contacts, companies, deals, pipelines, activities, notes, owners, custom properties, attachments where the API allows | W1 |
| P0 | GoHighLevel | Contacts, opportunities, pipelines, conversations where exportable, calendars, custom fields, sub-accounts | W2 |
| P1 | Zoho CRM | Leads, contacts, accounts, deals, activities, custom modules | W2 |
| P1 | Freshdesk | Tickets, conversations, contacts, companies, knowledge base articles | W2 |
| P1 | Pipedrive | Deals, persons, organisations, activities | W2 |
| P2 | Mailchimp and other email tools | Lists, segments, templates, unsubscribes (suppression lists are mandatory) | Year 2 |
| P2 | Tally | Ledgers, vouchers, parties, items | Year 2, with Accounts |
Access to each source is being verified
Each source's API scopes, rate limits and export limits are tracked as facts to verify with the provider before the connector is built. For example, whether a source's API is available on your plan can change what can be moved automatically.
How a migration runs
Every migration is designed to follow the same pipeline, with a person approving at each gate.
- 1
Connect or upload
Connect the source system or upload a file.
- 2
Profile the source
See which objects exist, how many records each has, and which custom fields are in use.
- 3
Map in the Mapping Studio
AI suggests a mapping for fields, pipelines, stages, statuses, tags, owners and custom fields, with a confidence score and a reason for each.
- 4
Approve the mapping
A person reviews and approves the mapping. Suggestions are never applied automatically.
- 5
Dry run
Full validation with no writes. The report shows rows per object, errors by type, duplicates, unmapped fields and estimated duration.
- 6
Fix and re-run
Adjust the mapping and run the dry run again until the report is clean.
- 7
Execute in batches
Records move in batches with checkpoints. A failed run resumes where it stopped, and re-running does not create duplicates.
- 8
Reconcile and sign off
A reconciliation report compares counts, sums and sample records. The tenant accepts and goes live, or rejects and rolls back.
What the Migration Factory is designed to do
The plan lists these capabilities as required for the first version.
Mapping Studio
Map fields, pipelines, stages, statuses, tags, owners and custom fields, with value transforms. Save mapping templates per source and reuse them across agency sub-accounts.
Dedupe with merge proposals
Matching rules find likely duplicates and propose merges. There are no silent merges.
Files and attachments
Files move with size limits and virus scanning. Any failures are listed.
Reconciliation
Counts per object, sums such as deal amounts per stage, a 1% sample diff with a minimum of 20 records, and an orphan-relation check.
Full audit trail
Every migrated record is stamped with the migration ID, source system, source ID and time of migration.
Rollback
Delete a migrated batch by its migration ID within a retention window, with an export of what was imported.
Consent carry-over
Marketing consent and unsubscribe status must migrate. A contact with missing consent is flagged as no marketing.
Automation inventory
Source automations are listed with suggested One3 equivalents. A person rebuilds or approves each one.
Live progress
Progress shows in the tenant's workspace, and agencies get one view across all sub-accounts.
AI suggests, people decide
AI-assisted mapping is an R2 Action: it always needs human approval and is never auto-applied. Duplicate merges are proposed, never silent. Automations are rebuilt or approved by a person. Consent and suppression status are always carried over, so a contact who opted out stays opted out.
The "switch in one weekend" agency playbook
| When | Step | Owner |
|---|---|---|
| T–7 days | Discovery call: source tools, sub-accounts, integrations and an automations inventory | One3 onboarding + agency |
| T–5 | Connect sources, profile data and build a mapping template on one pilot sub-account | Agency admin + Migration Factory |
| T–3 | Dry run on the pilot, fix the mapping, reconciliation sign-off | Agency |
| T–2 | Rebuild top automations and templates, connect WhatsApp and email, set up white-label | Agency + One3 |
| Friday evening | Freeze source changes (guidance) and run the migration for all sub-accounts in batches | Migration Factory |
| Saturday | Reconciliation reports per sub-account; fix exceptions | Agency + One3 |
| Sunday | Go-live checklist; client portal invitations prepared | Agency |
| Monday | Hypercare: migration issues handled through Desk with a priority SLA | One3 support |
Cutover and the days after
At cutover, source writes are frozen and a final delta sync picks up any last changes. A rollback window with export stays open after go-live, so a batch can still be removed if something is wrong.
After cutover, a health check runs on connectors and automations through the Connector Health Center. The plan tracks four measures for every migration: migration duration, reconciliation mismatch rate, rollbacks, and time to first value after cutover.
Exit gate: tested before launch
The plan sets a firm rule. No customer segment launches until its top two incumbent migration paths are tested on realistic data, meaning anonymised or synthetic data with realistic volume and mess. For agencies, that means GoHighLevel and HubSpot, with reconciliation reports reviewed and a successful rollback test.
The Migration Factory in plan numbers
- sources in the plan, from spreadsheets to Tally
- 8
- P0 and P1 sources planned within Year 1 (W1–W2)
- 6
- steps in the weekend agency playbook
- 8
- incumbent paths tested before each segment launches
- 2
- sample diff in reconciliation, minimum 20 records
- 1%
Questions about migration
Which tools can I migrate from?
Spreadsheets and HubSpot are planned for W1. GoHighLevel, Zoho CRM, Freshdesk and Pipedrive are planned for W2. Mailchimp and Tally are planned for Year 2. Each source's API access is being verified with the provider.
Will AI change my data without asking?
No. AI suggests mappings with a confidence score and a reason, but a person must approve every mapping. Merges are proposed, never silent.
What if the migration goes wrong?
You review a dry run before anything is written and a reconciliation report before sign-off. If you reject, the migrated batch is deleted by its migration ID and you get an export of what was imported.
Do my unsubscribes and consent records come across?
Yes, that is mandatory in the design. Marketing consent and suppression status must migrate. Contacts with missing consent are flagged as no marketing.
Are my automations moved automatically?
Not automatically. The Migration Factory lists your source automations and suggests One3 equivalents. Your team or One3 rebuilds them, and a person approves each one.
Can an agency migrate many sub-accounts at once?
That is what the playbook is designed for. Mapping templates are reused across sub-accounts, batches run per sub-account, and the agency sees progress for all of them in one view.
Plan your switch with us
Tell us which tools you use today. We will walk you through how the Migration Factory is planned to move your data, and what can be tested first.