Migrate from Affinity Fieldreach to Twenty CRM

Affinity Person records map directly to Twenty People. Each Affinity person carries a name, email, phone, and optional custom fields. Twenty's People object is the primary contact entity and supports relation links to Companies. Primary email is used as the unique identifier for deduplication during import.

Affinity Organization records (the company entity linked to Persons) translate directly to Twenty Companies. Name, domain, industry, employee count, address, and phone map to their Twenty counterparts, while any custom fields are created in Settings → Data Model before import. Parent‑child hierarchies in Affinity become Twenty's Parent Company relation where applicable.

Affinity Work Orders map to Twenty Tasks with field-level translation: status maps to Task status, scheduled date to due date, assigned employee to assignee. Work Order description and completion notes combine into the Task body. Affinity's multi-step work order history is flattened into a single Task record with a custom long-text field preserving the sequence.

If your Affinity Work Orders use custom fields beyond status and assignee — parts used, travel time, signature capture — we recommend a Twenty custom WorkOrder object. We create the custom object via Settings → Data Model, define the fields matching Affinity's schema, and import Work Orders as records of that type with a relation link to the relevant People or Company.

Affinity Assets (equipment, locations, or inventory items) have no native Twenty equivalent. We create an Asset custom object in Twenty with fields for asset name, type, location, parent-asset relationship, and maintenance history pulled from Affinity's linked records. The asset-to-work-order relationship is preserved as a relation field on the WorkOrder custom object.

Affinity Employees who are also CRM users map to Twenty Workspace Members. We extract the employee email and name, invite them to the Twenty workspace before migration, and link their People record (if they appear as a contact in Affinity) to their Workspace Member account via email match.

Affinity Work Order attachments (photos, signatures, PDF documents) are exported from the source environment and re‑uploaded into Twenty, where each file is linked to the matching Task or custom WorkOrder record via the UI or API. File size constraints and format conversions (such as image compression) are applied during upload, and original timestamps are preserved in Twenty's file metadata.

Affinity Person custom fields (beyond name, email, and phone) are migrated as Twenty custom fields on the People object. Each field is first created in Settings → Data Model, where we match the Affinity field type (text, number, select, multi‑select) and recreate pick‑list options. Validation rules or dependencies are noted in the pre‑migration checklist, and the field definitions are exported as JSON for reference before the import runs.

Affinity Work Order custom fields (such as service type, customer sign‑off, parts cost, and warranty flag) are recreated as custom fields on the Twenty object chosen for Work Order mapping. For each field we match the data type, recreate pick‑list values as select options, and preserve default values. The field schema is exported from Affinity and used to create Twenty custom fields via Settings → Data Model before the import.

Affinity notes attached to Persons, Organizations, or Work Orders become Twenty Notes linked to the matching People, Company, or Task record. The note body, any embedded attachments, timestamps, and author details are transferred, preserving the original creation date and the author's name or email. If a parent record cannot be resolved, the note is flagged for manual review before import.

Affinity location data on Assets or Organizations is translated to Twenty's address fields on the Company object, with multi‑line addresses parsed into street, city, state, country, and postal code components. If Affinity stores location in a custom field, that field is recreated as a custom address field in Twenty, and any missing components are flagged for manual correction before the final import.