Migrate from Field Squared to Twenty CRM

Twenty People object lacks standard contact fields — custom fields must be created before CSV import

Unlike Field Squared, which stores email, phone, and address natively on Contact records, Twenty's People object does not include these as standard fields out of the box. The GitHub issue #13953 on Twentyhq/twenty explicitly calls out that new users expect standard fields like emails, phones, and job titles to exist immediately. Migration planning must include a first-pass phase to create every custom field in Twenty's Settings → Data Model before the CSV import step references those columns. If a column in the import file has no corresponding Twenty field, the import will silently drop that column. FlitStack generates a field-creation checklist from the Field Squared schema audit so the Twenty workspace is ready before any data lands.

Import order constraint requires Companies to load before People and Opportunities

Twenty's CSV import documentation explicitly states that the 'one' side of one-to-many relationships must exist before the 'many' side can reference them. Companies must import first (as the parent of People and Opportunities), followed by People (with companyId linking to Companies), then Opportunities (with companyId and personId linking to both). Custom objects with relationships import last. This sequencing is not optional — importing People before Companies will result in orphaned records with no companyId, and Opportunities will fail to link to their account records. FlitStack sequences the migration packages in dependency order and validates the CSV files before each import run.

Twenty API rate limits cap bulk migration throughput on Free and Pro tiers

Twenty's API rate limits are 100 calls per minute on the Free tier and 200 calls per minute on Pro/Organization. Field Squared exports can contain tens of thousands of Work Order and Asset records. A direct API-based migration is rate-limited by these thresholds, extending migration time proportionally. FlitStack uses Twenty's CSV import endpoint as the primary migration path (which bypasses per-call rate limits for data volume) and reserves API calls for field validation and delta-pickup operations. Large datasets exceeding 20,000 records per object are split into multiple CSV batches per Twenty's export limit.

GPS coordinates and service location data require custom field creation in Twenty

Field Squared stores GPS latitude and longitude on Asset and Work Order records for field dispatch and routing. Twenty's Companies and Opportunities objects have no native coordinate fields. These values must be preserved as custom number fields (Latitude__c, Longitude__c) on the relevant objects. The custom field definitions must exist in Twenty before the import references them. If the location data is critical for your service operations workflow, account for the time to configure these fields and any downstream integration (map views, route planning) that will consume them.

Field Squared workflows and dispatch rules have no export path to Twenty

Field Squared's workflow configuration, scheduling rules, GPS routing logic, and dispatch automations are platform-specific constructs with no portable export format documented in Field Squared's API documentation. Twenty's workflow builder operates on CRM-level automation (task creation, field updates, notifications) and does not replicate field-service scheduling patterns. All workflow logic must be rebuilt manually in Twenty's workflow builder or implemented via the Twenty GraphQL API. FlitStack provides a workflow audit export from Field Squared documenting every active workflow, trigger, and action so your Twenty admin has a rebuild reference, but the rebuild itself is a separate configuration effort not included in the data migration fee.