Migrate from Field Pros to Twenty CRM

Twenty's import order requirement blocks records with unresolved foreign keys

Twenty's CSV import enforces referential integrity: Companies must be imported before People, and People before Opportunities. If a People record references a companyId that does not yet exist in Twenty, the import fails silently or creates an orphan. FlitStack AI sequences the migration with an explicit dependency chain — Companies first, then People with companyId resolution, then Opportunities with companyId and personId resolution — and validates foreign key integrity before each batch commits. This prevents orphaned records that would be invisible in Twenty's pipeline view.

Custom fields must exist in Twenty before CSV import — they do not auto-create

Twenty's CSV import creates records but not fields. If you attempt to import a column that maps to a custom field that has not been created in Settings → Data Model, Twenty ignores the column silently. Field Pros custom fields with no direct Twenty equivalent (lifecycle stage, lead score, custom deal properties) must be pre-created as custom fields before the migration runs. FlitStack AI delivers a custom field creation checklist as part of the migration plan, so Twenty's Data Model is ready before data lands. Skipping this step results in data that exists in Field Pros but is absent from Twenty after import.

Twenty API rate limits cap batch migration throughput for large datasets

Twenty's Pro tier allows 50 API calls per minute; Organization tier allows 100. Field Pros setups with more than 100,000 records hitting Twenty's API in rapid succession will encounter 429 rate limit responses. FlitStack AI implements exponential backoff with jitter when rate limits are hit, and chunks large record sets into batches that respect the per-minute ceiling. For datasets exceeding 500,000 records, we prefer Twenty's CSV import endpoint (which is not subject to the same per-minute rate limit) over the REST API, reserving API calls for custom field creation and owner resolution only.

Twenty's People object does not support multi-company associations natively

Field Pros may allow a contact to associate with multiple companies (N:N relationship). Twenty's People object has a single companyId field, storing one primary company. Secondary company associations from Field Pros are preserved as a custom Multi_Company_Associations__c field in JSON format, or we create a custom junction object if the relationship carries additional attributes (role, start date). Your admin decides whether to expand to the junction object or accept the flattened reference.

Twelve's built-in workflow builder lacks native sequence automation for multi-step outreach

Twenty's workflow builder handles internal automations (field updates, notifications, task creation) but does not ship a native sequence or cadence engine for time-delayed multi-step outreach campaigns. Field Pros sequences (manual trigger → wait → email → wait → call) must be rebuilt using Twenty's workflow builder combined with a third-party sequencing tool or a custom workflow chain. FlitStack exports your Field Pros sequence definitions as a step-by-step rebuild reference so your RevOps team can reconstruct the logic in Twenty or an attached sequencing platform.