Twenty CRM migration checklist
Use this checklist to keep a Salesforce → Twenty project honest about scope, risk, and sequencing.
Discovery
- Complete a metadata readiness scan
- List top blockers and must-keep integrations
- Identify unused objects/automations to leave behind
- Confirm sandbox vs production scan assumptions
Design
- Define the Twenty object model for the pilot scope
- Decide formula/rollup replacements
- Classify Flows as convert / rewrite / retire
- Plan package replacements or temporary dual-running
Build
- Migrate/seed pilot data with explicit quality checks
- Rebuild critical automations in Twenty primitives
- Reconnect email, calendar, and key webhooks
- Set permissions intentionally — don’t clone Salesforce sprawl
Launch
- Train one pilot team end-to-end
- Define cutover and rollback criteria
- Monitor failed syncs and missing fields for the first weeks
- Expand scope only after the pilot is operationally boring
Start the checklist with a real report: run the readiness scan or review the sample output.
Get your readiness score
Connect a Salesforce sandbox, scan metadata only, and receive a private compatibility report for Twenty.