Migrate to Twenty
Sample report · fictional org
Acme Sandbox · sandbox · Metadata-only assessment
68 / 100
Possible with redesign
Migration complexity: High
Migration is possible with redesign. Expect rework around Apex-heavy automation and formula logic before a clean Twenty cutover.
Org footprint
- Custom objects
- 34
- Custom fields*
- 410
- Active Flows
- 22
- Apex classes
- 142
- Apex triggers
- 19
- Installed packages
- 5
Category scores
- Data model72
- Automations58
- Packages & integrations81
- Security model76
- Platform fit90
Main blockers
142 Apex classes and 19 active triggers
Apex is a weak direct fit; simple triggers may become Logic Functions, complex orchestration will not.
28 formula fields on described objects
Formula fields usually become workflows or server-side logic rather than direct field ports.
This assessment is based on Salesforce metadata and configuration. Record-level data quality, storage volume, and migration volume are not included.