Can your Salesforce org move to Twenty?
Compatibility is not binary. Most orgs have a portable CRM core and a set of Salesforce-specific patterns that need redesign.
Migrate to Twenty scores compatibility across data model, automations, packages, security, and platform fit. The score is deterministic and rules-based — AI may explain findings later, but it does not invent the score.
Usually stronger fits
- Account / Contact / Opportunity–centric CRM usage
- Moderate custom objects with clear ownership
- Simple lookups and picklists
- Record-triggered Flows with limited orchestration
- Light managed-package footprints
Usually weaker fits
- Screen Flow guided experiences
- Complex Apex orchestration and callout frameworks
- Polymorphic relationships and Person Account–heavy models
- Salesforce CPQ, Field Service, Loyalty, OmniStudio
- Experience Cloud as a critical customer portal
How to interpret a score
A mid-range score often means “possible with redesign,” not “impossible.” Review blockers and complexity together. See the methodology for weighting details, or start with a sample report.
FAQ
- What scores well for Twenty compatibility?
- Standard CRM objects, simple custom objects/fields, straightforward lookups, and simple record-triggered Flows generally score better than Apex-heavy or Screen Flow–heavy orgs.
- What are common blockers?
- CPQ/Revenue Cloud, Field Service, Experience Cloud as a critical portal, OmniStudio/Industry packs, extensive Screen Flows, and high Apex dependency.
Get your readiness score
Connect a Salesforce sandbox, scan metadata only, and receive a private compatibility report for Twenty.