Migrate from FieldFX to Twenty CRM

Audit FieldFX Salesforce org and generate migration sequence map

FlitStack AI connects to your Salesforce org via scoped read credentials and inventories every object — standard (Account, Contact, Opportunity) and FieldFX package objects (FX5__Work_Order__c, FX5__Ticket__c, FX5__Service_Appointment__c, FX5__Timecard__c, FX5__Dispatcher__c, and their children). We capture record counts, custom field definitions (including namespace prefixes), pick-list values, and foreign-key relationships. From this inventory we generate the migration sequence map: a strict ordering that respects parent-before-child dependencies (Accounts → Contacts → Opportunities → custom objects). This map is delivered as a planning document for your review before any data moves.

Create Twenty custom objects and fields before migration

Before migration data lands in Twenty, your team (or our team with admin credentials) creates the custom objects required for FieldFX field-service data: Work Order, Work Order Line Item, Ticket, Service Appointment, Dispatcher Assignment, and Timecard. For each object we deliver a schema specification listing every custom field to create in Settings → Data Model, including field type, pick-list values, and whether the field should be required. This step is a prerequisite — Twenty's import will reject records referencing an object or field that does not yet exist. We coordinate this phase so it runs in parallel with data extraction planning.

Extract Salesforce data via REST/Bulk API with batch management

FlitStack AI extracts data from your Salesforce org using the REST API for standard objects and the Bulk API for objects with more than 10,000 records. Batch sizes are managed to stay within your org's daily REST API limit and the per-user Batch API limit used by FieldFX Mobile. We export records in migration-sequence order: Accounts, then Contacts, then Opportunities, then each FieldFX package object in parent-before-child order. Salesforce Owner IDs are captured for email-based user resolution. All timestamps, custom field values, and pick-list values are included in the export. On 429 (rate limit) responses, we apply exponential backoff and retry.

Resolve owners by email and build Source_System_ID cross-reference table

Salesforce User records (OwnerId on every object) are matched against Twenty Workspace Members by email address. This creates the Owner-to-Workspace-Member mapping that allows opportunity and task ownership to transfer correctly. Unmatched owners are flagged in a pre-flight report — your team either invites them to Twenty first or assigns their records to a fallback owner. Simultaneously, we build the Source_System_ID cross-reference table that maps every Salesforce record ID to its migrated Twenty id. This table is the backbone of child-record linking: Work Order Line Items use it to find their parent Work Order; Tickets use it to find their parent Account and Contact.

Run sample migration with field-level diff and verification

A representative sample — typically 200–500 records spanning Accounts, Contacts, Opportunities, and at least one FieldFX custom object — is migrated first. We generate a field-level diff report comparing source Salesforce values against the Twenty destination values for every mapped field. This report surfaces pick-list mismatches, date-format discrepancies, truncated text fields, and foreign-key resolution failures before the full migration commits. You review the diff, approve the mapping, and FlitStack AI proceeds to the full run. For FieldFX Work Orders and Tickets, the sample diff verifies that the custom object and field setup in Twenty was done correctly.

Execute full migration with delta-pickup window and post-migration audit

The full migration runs against Twenty using the verified mapping from the sample phase. A delta-pickup window (24–48 hours after the main run completes) captures any records created or modified in Salesforce during the cutover period — typically records your team is still working on in FieldFX while the migration runs. FlitStack AI generates a post-migration audit log listing every record migrated, every record skipped (with reason), and every owner that required fallback assignment. Record counts are reconciled against the source org. One-click rollback is available within the delta window if reconciliation reveals data integrity issues. After rollback eligibility expires, your team begins the workflow-rebuild phase using the exported FieldFX workflow definitions.