Migrate from Field Harmony to Twenty CRM

Audit Field Harmony data and Twenty workspace setup

FlitStack AI audits your Field Harmony account to document all objects, custom fields, ticket statuses, and asset types. We simultaneously review your Twenty workspace to identify which standard fields are active and which custom objects need creation. This step produces a data inventory, a gap analysis against Twenty's standard model, and a list of custom objects and fields to pre-create in Twenty before any records move.

Create custom objects and fields in Twenty

We create the Asset custom object (with Asset_ID__c, Manufacturer__c, Model__c, Serial_Number__c, Location__c, and CompanyId relation) and all required custom Opportunity fields (Work_Order_Number__c, Ticket_Status__c, Ticket_Priority__c, Service_Scheduled_Date__c, Assigned_Technician_ID__c). Certification and active-status fields are added to the People object. Each field's data type, pick-list options, and default values are configured in Twenty Settings → Data Model before any import begins. All custom fields are configured with appropriate data types, validation rules, and help text to guide users during data entry.

Resolve technician assignments by email match

Field Harmony technician IDs on tickets are matched against Twenty Workspace Members by email. We produce a match report showing all resolved assignments and any unmatched technicians. Your team either invites unmatched technicians to Twenty before migration or decides on a fallback owner for their records. No Opportunity lands with an unresolved or broken technician assignment. If any technician cannot be matched, we record their email in a fallback field and notify your admin so they can decide on an appropriate resolution before go-live.

Export Field Harmony data and transform records

Data is extracted from Field Harmony via API or CSV export (depending on your plan tier). We transform records into Twenty CSV format: parse JSON notes into plain text for the Note object, map ticket statuses to the custom Ticket_Status__c pick-list values, and resolve company lookups so each Person record has a valid companyId. Assets are exported separately and staged for import after their parent Companies exist.

Run sample migration with field-level diff

A representative slice of records — typically 100–500 spanning technicians, customers, tickets, and a few assets — migrates first. We generate a field-level diff comparing the source Field Harmony values against what landed in Twenty so you can verify that ticket metadata, technician assignments, asset relationships, and note content are correct before the full run commits. During this sample pass we also confirm that custom pick-list values match exactly and that any required relationships (such as CompanyId on People) are present, preventing downstream import failures.

Full migration with delta pickup and validation

All remaining records migrate into Twenty following the correct import order (Companies → People → Opportunities → Asset custom object → Notes). A delta-pickup window (typically 24–48 hours) captures any Field Harmony records created or modified during cutover. FlitStack AI produces a final validation report showing record counts, relationship integrity, and any unresolved items. One-click rollback is available if reconciliation reveals unexpected gaps.