Migrate from Fieldproxy to Twenty CRM

Fieldproxy customers map directly to Twenty People. Email, phone, address, and job title fields map to their Twenty equivalents. The primary site association migrates as a companyId relation to the mapped Site → Company record. We also ensure that any custom fields attached to the customer record are transferred as custom fields on the Twenty People object, preserving data completeness.

Fieldproxy jobs map to Twenty Opportunities. The job name becomes Opportunity.name; scheduled_date becomes closeDate; total_amount becomes amount. Job status (New, In Progress, Completed, Cancelled, On Hold) requires value-by-value mapping to Twenty opportunity stages. We also map any custom fields on the job to custom Opportunity fields, ensuring that additional details such as service type and assigned technician are preserved.

The assigned_technician email resolves to a Twenty workspace member by email match. Unmatched technicians are flagged before migration; their records get assigned to a fallback owner. This preserves the owner relationship without creating orphaned records. If multiple technicians exist for a single job, we select the primary assignee based on the most recent work order to maintain accuracy.

Twenty sets Opportunity.CreatedDate at migration time. Original Fieldproxy created_at timestamps are preserved as a custom datetime field (originalCreatedAt__c) for historical reporting continuity and audit purposes. We also capture the updated_at timestamp in a separate custom field (originalUpdatedAt__c) so that the full lifecycle of each record is available for reporting after migration.

Fieldproxy job statuses (New, In Progress, Completed, Cancelled, On Hold) map explicitly to Twenty opportunity stages. Each pick-list value from Fieldproxy gets a corresponding stage name and probability in Twenty. Stage-entry timestamps are not natively available and are noted for custom field creation.

Twenty has no native fields for service_type or assigned_technician. These migrate as custom text fields on the Opportunity object. We create these fields before import so the CSV import can populate them without errors. During the pre‑migration field‑creation phase, we also set appropriate field‑level validation rules, such as pick‑list constraints for service_type, to maintain data consistency after import.

Fieldproxy allows multiple work orders per job. We attach work_order_id, work_order_number, and description from the most recent work order as custom Opportunity fields (workOrderId__c, workOrderNumber__c). Work order status merges into the same Opportunity.stage value as job status — teams should decide per-record which status is authoritative.

Fieldproxy sites map to Twenty Companies. The site name becomes Company.name; site URL becomes website. Site address fields (street, city, state, postal_code, country) map directly to their Company equivalents. Sites link to customers via the same companyId relation used by the Customer mapping.

Twenty has no native asset management object. Fieldproxy assets (asset ID, asset name, asset type, company association) migrate as a custom Asset object with custom fields: assetId__c (text), assetName__c (text), assetType__c (select), and companyId (relation to Company). The asset type pick-list values from Fieldproxy carry over as select options.

Fieldproxy invoices map to a custom Invoice object with fields: invoiceId__c, amount__c (currency), invoiceDate__c (date), status__c (select), customerId (relation to People). Invoice status values from Fieldproxy carry over as select options. Each invoice links to the customer it was issued to. All invoice amounts are stored as currency fields, and the original invoice number is retained in a custom field for traceability.

Fieldproxy payments map to a custom Payment object with fields: paymentId__c, amount__c (currency), paymentDate__c (date), paymentMethod__c (select), invoiceId (relation to custom Invoice object), customerId (relation to People). This preserves the invoice-to-payment hierarchy from Fieldproxy.

Fieldproxy notes and attachments migrate as Twenty Notes. Notes attach to the parent record (People, Company, or Opportunity) using Twenty's relation model. File attachments re-upload to Twenty Files. Original note timestamps are preserved. We also map any tags or categories present in Fieldproxy notes to custom tag fields on the Twenty Note, preserving organizational metadata.