Migrate from FieldEdge to Twenty CRM

FieldEdge customers are individuals with name, email, phone, and address. We map these directly to Twenty's People object. Each FieldEdge customer may have multiple service locations — we link them via the People.companyId relationship. Primary contact per location becomes the primary People record; secondary contacts on the same account become additional People records linked to the same Company.

FieldEdge stores service locations separately from customers, supporting N:1 customer-to-location relationships. In Twenty, we create a Company record per unique service address and link it to the primary Customer as the People.companyId. Multi-location customers with distinct billing or contract entities spawn multiple Company records with a custom 'Parent Location' field maintaining the hierarchy.

FieldEdge work orders contain job type, status (Scheduled, In Progress, Completed, Cancelled), scheduled date, assigned technician, description, line items, and total amount. We map these to Twenty Opportunities with StageName derived from Work Order status: 'Scheduled' and 'In Progress' map to Twenty stage values your admin configures; 'Completed' maps to Closed Won; 'Cancelled' maps to Closed Lost. Original work order amount becomes Opportunity.Amount.

FieldEdge work order status values are mapped one-by-one to Twenty Opportunity stage names your admin defines post-schema-setup. We preserve the original FieldEdge status label as a custom field (Work_Order_Status__c) for reporting continuity. Stage-transition timestamps from FieldEdge's audit log migrate as custom datetime fields on the Opportunity record.

FieldEdge invoices have invoice number, date, line items, tax, total, payment status, and QuickBooks sync status. Twenty has no native invoice object. We create a custom Invoice object in Twenty with fields for invoice number, date, total amount, tax amount, payment status, and a link to the originating Opportunity and Company. Each invoice line item becomes a custom Invoice Line Item field or a child related list.

FieldEdge service agreements cover recurring scopes of work, billing frequency (monthly, annual), start/end dates, and assigned technician rules. We create a custom Service Agreement object in Twenty linked to the Company and the primary People contact. Fields include agreement type, billing frequency, start date, end date, monthly value, scope description, and status (Active, Expired, Cancelled). Recurring revenue figures map to a custom currency field for pipeline reporting.

FieldEdge maintains a visual pricebook with service categories, flat-rate prices, and T&M rates. We create a custom Pricebook Item object in Twenty with fields for item name, category, flat rate, T&M hourly rate, unit of measure, and a relation to the parent Pricebook Category. If FieldEdge uses 'good/better/best' tier pricing, each tier becomes a separate Pricebook Item record with a tier label field.

FieldEdge technicians and office staff have names, email addresses, phone numbers, certifications, and role assignments. We resolve FieldEdge users by email match to Twenty Workspace Members. Unmatched users are flagged before migration — your team invites them to Twenty first or assigns their records to a fallback member. Role information (Technician, Dispatcher, Office Admin) migrates as a custom pick-list field on the Workspace Member.

FieldEdge work order notes, technician comments, customer signature logs, and site photos attach to the work order. We migrate these as Twenty Notes linked to the corresponding Opportunity record. Each note preserves its original timestamp and author. Photos download and re-upload as file attachments linked to the Note record.

FieldEdge payments record the payment method, amount, date, and invoice reference. We migrate these as custom fields on the custom Invoice object: payment date, payment amount, payment method (cash, card, check, ACH), and payment status. QuickBooks payment sync metadata is preserved as a text field for reference but has no active equivalent in Twenty.

FieldEdge supports custom fields on customers, locations, work orders, and invoices. Each custom field requires a corresponding custom field in Twenty on the target object before migration. We audit your FieldEdge custom fields during scoping, create them in Twenty via Settings → Data Model, and then map values during the migration run. Custom field type mapping: text → TEXT, number → NUMBER, picklist → SELECT, date → DATE, checkbox → BOOLEAN.

FieldEdge stores QuickBooks customer ID, invoice ID, payment ID, and sync status for each record. Twenty has no accounting integration. We preserve QuickBooks IDs as custom text fields (QB_Customer_ID__c, QB_Invoice_ID__c) for reference during reconciliation, but the financial linkage must be re-established by your accountant in a new QuickBooks-to-Twenty connection post-migration.