Migrate from Field Force Tracker to Twenty CRM

Field Force Tracker stores customer contacts with business info mixed into the customer record. We split this into Twenty's Person record (name, email, phone) and Company record (business name, industry, website). The primary service address from Field Force Tracker becomes the Company's address field. Multiple service locations per customer create additional address records linked to the Company.

Where Field Force Tracker holds business accounts as a separate entity from contacts, those map directly to Twenty's Company object. Company name, domain, industry, employee count, and annual revenue migrate as standard Company fields. Parent-child company hierarchies map via Twenty's relation fields.

Field Force Tracker work orders are central to the platform but have no native Twenty CRM equivalent. We create a custom Job object in Twenty with fields for job number, description, service type, status, priority, scheduled date, and completion date. Each Job record links to the Company (service location) and Person (customer contact) via Twenty's relation fields. Job status values map via value_mapping to a custom pick-list in Twenty.

Field Force Tracker technicians are staff records with skills, certifications, and availability. We map them as Twenty People records with a custom role field set to 'Technician' and skill certifications stored as custom multi-select fields. Technician email is used to match against Twenty workspace members for owner resolution. Technicians who also appear as customers receive both the technician role and a regular contact record.

Field Force Tracker locations store service addresses linked to customers. Each unique address migrates as address fields on the corresponding Twenty Company record. Multiple locations per customer generate additional address records via Twenty's address handling. GPS coordinates from Field Force Tracker are preserved in custom latitude/longitude fields on the Company.

Field Force Tracker invoices contain line items, amounts, tax, payment status, and links to jobs and customers. We create a custom Invoice object in Twenty with fields for invoice number, date, amount, tax, status, and payment date. Line items are stored as a custom JSON field or as related custom InvoiceLineItem records. Invoice-to-Job relations are preserved via Twenty's relation system.

Field Force Tracker's Asset module tracks equipment at customer locations with serial numbers, make/model, warranty dates, and service history. A custom Asset object in Twenty captures serial number, equipment type, manufacturer, model, warranty expiration, and last service date. Each Asset links to the Company (installed location) and related Job records via Twenty relations.

Field Force Tracker job notes and service history comments migrate as Twenty Notes attached to the corresponding Job custom object. Timestamps and technician author information are preserved. Completed service actions that require follow-up become Twenty Tasks linked to the Job and assigned to the relevant technician Person record.

Field Force Tracker user records are matched to Twenty workspace members by email address. Active technicians and dispatchers who are also Twenty users receive their own Person records. Users without a matching Twenty account are flagged before migration — their records can be assigned to a fallback owner or the account invited before re-running.

Field Force Tracker custom fields per module migrate to matching Twenty standard or custom objects. Field type mapping applies: text → string, number → number, date → date, pick-list → select, multi-select → multi-select. Field Force Tracker lookup fields pointing to related records map as Twenty relation fields once the target objects exist.

Field Force Tracker's dispatch board assigns jobs to technicians on specific dates and territories. Twenty CRM has no scheduling board or dispatch module. We preserve technician-to-job assignments as a custom Assigned Technician field on the Job custom object, but the visual scheduling aspect must be rebuilt using Twenty's workflow triggers or an external scheduling tool.

Field Force Tracker job-triggered notifications, status-change rules, and mobile workflow states have no direct Twenty CRM equivalent. Twenty's workflow builder handles basic record-triggered automations. All Field Force Tracker automation logic is exported as a reference document for your team to rebuild in Twenty or via an external automation platform.