Migration · CRM data
Move the Data You Need — Not the Mess You Inherited
Contacts, companies, opportunities, custom fields, tags, notes, activity history, consent status, source attribution and location ownership — each needs a rule before import.
- 01
Extract
- 02
Profile
- 03
Clean
- 04
Deduplicate
- 05
Map
- 06
Transform
- 07
Import
- 08
Validate
Field mapping preview
Every source field gets a target, a transformation and a check.
Illustrative rows. A real mapping sheet covers every field in the source, including the ones that are deliberately dropped.
| Source field | Target field | Transformation | Required? | Validation |
|---|---|---|---|---|
| phone_mobile | Phone | E.164 format | Yes | Valid number |
| lead_source__c | Source | Map to source list | Yes | In allowed values |
| branch_name | Location (owner) | Branch → sub-account | Yes | Location exists |
| opt_in_sms | SMS consent | Boolean + date | Yes | Consent preserved |
| legacy_notes | Notes | Concatenate, dated | No | Sample check |
Data decisions
Five outcomes for every record set.
Dead data, test records and stale leads get archived — exported and kept, but not imported into a clean system.
Keep
Migrate as-is
Clean
Fix, then migrate
Merge
Combine duplicates
Archive
Export, don't import
Do not migrate
Leave behind
Validation after import
The import isn't done until the numbers reconcile.
Source-specific mapping is covered for HubSpot, Salesforce and Zoho. The full sequence is on GoHighLevel migration.
- ✓Record counts
- ✓Duplicate rates
- ✓Required fields
- ✓Opportunity ownership
- ✓Location assignment
- ✓Sample record QA
Next step
Plan your data migration.
Tell us roughly how many records you have, where duplicates come from and how location ownership is recorded today.