How to migrate Salesforce to Twenty
A practical migration sequence that starts with metadata readiness, not a big-bang cutover.
1. Establish readiness
Run a metadata-only readiness scan to inventory objects, fields, automations, packages, and security complexity. Use the report to separate direct-conversion candidates from redesign work.
2. Decide what Twenty should own
Twenty is strongest as a modern CRM core. Salesforce-specific platforms — CPQ, Field Service, Experience Cloud portals, OmniStudio — often stay outside the first migration wave or move to specialized tools.
3. Redesign before you copy
- Map Account/Contact/Opportunity patterns to Twenty Company/Person/Opportunity models
- Replace fragile formula/rollup logic with explicit workflows
- Rewrite Apex that encodes revenue-critical rules
- Retire unused objects and packages instead of porting them blindly
4. Pilot a bounded slice
Migrate one team or one process end-to-end. Validate data quality, permissions, and integrations before expanding scope.
5. Cut over with an integration plan
Named credentials, remote sites, and marketing connectors usually need rewiring. Plan those jobs alongside the CRM object migration, not after go-live.
Next reading
FAQ
- Can Salesforce metadata migrate 1:1 into Twenty?
- Usually no. Simple CRM objects and some automations map well; screen Flows, heavy Apex, and Salesforce platform products typically need redesign.
- Should we migrate everything at once?
- Rarely. Most teams should pilot a revenue-critical slice first, then expand once the data model and workflow patterns are proven in Twenty.
Get your readiness score
Connect a Salesforce sandbox, scan metadata only, and receive a private compatibility report for Twenty.