Migration Overview
Successful CRM migration involves:- Planning - Assess what to migrate
- Preparation - Clean and export data
- Mapping - Match fields between systems
- Testing - Import sample data
- Execution - Import full dataset
- Validation - Verify accuracy
- Optimization - Configure Twenty for your workflow
Plan for 2-4 weeks for a full CRM migration, depending on data volume and complexity.
Pre-Migration Planning
What to Migrate
Decide what data to bring:Essential Data
Must migrate:
- Active customers/contacts
- Open opportunities
- Recent activities
- Important notes
Optional Data
Consider:
- Closed/lost deals
- Historical activities >1 year
- Archived records
- Old attachments
Data Audit
Before migrating, audit your current CRM:Map relationships
Document how objects connect:
- Contacts belong to Companies
- Deals link to Companies and Contacts
- Activities link to all above
Migrating from Specific Platforms
Salesforce to Twenty
Export from Salesforce
Use Data Export Service:
- Setup → Data Export
- Select objects: Accounts, Contacts, Opportunities, Activities
- Export to CSV
- Download ZIP file
Prepare data
Salesforce exports need cleanup:
- Remove system fields (OwnerId becomes names)
- Convert picklist values
- Flatten relationship fields
HubSpot to Twenty
Export from HubSpot
- Settings → Data Management → Export
- Select objects and properties
- Export to CSV
- Download files
Pipedrive to Twenty
Other CRMs
For any CRM:- Export to CSV - Most CRMs support CSV export
- Identify equivalent objects - Map their objects to Twenty’s
- Map fields - Match fields between systems
- Import in order - Companies, then People, then everything else
Field Mapping Guide
Creating Custom Fields
For CRM-specific fields:Decide what to migrate
Keep fields that are:
- Actively used
- Contain important data
- Required for workflows
Field Type Conversion
- Picklists → Select
- Multi-Picklists → Multi-Select
- Lookups → Relations
- Formulas → Workflows
Convert dropdown fields:
- Create Select field in Twenty
- Add all options from old CRM
- Values must match exactly for import
Migration Process
Phase 1: Test Migration
Never migrate directly to production:Import sample data
Start with 50-100 records per object:
- Diverse record types
- Records with relationships
- Records with all field types populated
Verify data
Check:
- ☑ All fields mapped correctly
- ☑ Relationships linked
- ☑ Select options match
- ☑ Dates formatted correctly
- ☑ Numbers calculated right
Phase 2: Full Migration
Final data export
Export fresh data from old CRM:
- Include records created/updated since test
- Use same export format as test
Phase 3: Post-Migration
Configure Twenty
Set up:
- Views for team workflows
- Filters and sorting
- Permissions and roles
- Integrations (email, calendar)
Create workflows
Recreate automation from old CRM:
- Assignment rules
- Notifications
- Field updates
- Integrations
Migration Best Practices
Clean before migrating
Clean before migrating
Don’t migrate garbage:
- Remove duplicates
- Delete outdated records
- Fix data quality issues
- Standardize formats
Start fresh with workflows
Start fresh with workflows
Don’t blindly recreate old workflows:
- Review which automation is still needed
- Simplify where possible
- Take advantage of Twenty’s features
- Document new workflows
Import in phases
Import in phases
Consider phased approach:
- Week 1: Core data (Companies, People)
- Week 2: Deals and opportunities
- Week 3: Historical activities
- Week 4: Custom objects
Keep old CRM read-only
Keep old CRM read-only
Don’t delete old CRM immediately:
- Keep read-only for 30-90 days
- Reference for missing data
- Fallback if issues arise
- Export archives before closing
Common Migration Challenges
Challenge: Data Volume
Problem: Millions of records to migrate Solutions:- Migrate in batches
- Use API for large imports
- Consider archiving old data
- Focus on active records
Challenge: Complex Relationships
Problem: Many interconnected objects Solutions:- Map relationships before importing
- Import in correct dependency order
- Use test migration to verify
- Import parent objects first
Challenge: Custom Fields
Problem: Many custom fields to recreate Solutions:- Evaluate which are still needed
- Create fields before importing
- Use consistent field types
- Document field mappings
Challenge: Data Quality
Problem: Messy data in old CRM Solutions:- Clean before migrating
- Use import validation
- Fix errors before retrying
- Consider data cleaning tools
Migration Checklist
Use this checklist for your migration:Next Steps
Importing Data
Detailed import instructions
Exporting Data
Export data from Twenty
