Migrate from Fieldmagic to Twenty CRM

Fieldmagic's Customer object (name, phone, email, billing address) maps directly to Twenty's Companies object. The domain/website field on Fieldmagic Customer migrates to the Website field on Company. Since Twenty does not have a native Site sub-entity, the primary service address is stored as a custom Address__c text field on the Company record for reference.

Fieldmagic Contacts map 1:1 to Twenty People. Each Contact's email, phone, job title, and name fields migrate to the corresponding People fields. The link to the parent Customer migrates as a CompanyId relation pointing to the mapped Company record — this requires the Company import to complete before Contact import per Twenty's dependency order.

Fieldmagic's Site object (service locations with address, GPS coordinates, site name) has no native equivalent in Twenty CRM. We create a custom Site__c object in Twenty, add custom fields for address components, GPS latitude/longitude, and a CompanyId relation back to the parent Company. Site-to-Contact N:1 relationships are preserved via a contactId custom field on Site__c.

Fieldmagic's Job entity (scheduled work linked to a Site, assigned to a technician, with status, priority, and description) requires a custom Job__c object in Twenty. Custom fields include jobStatus (select), priority (select), scheduledDate (date), assignedTechnician (relation to Person), siteId (relation to Site__c), and originalCreateDate (datetime for audit continuity). Job history and checklist data are stored as JSON in a long-text custom field.

Fieldmagic Quotes — proposals sent to customers with estimated amounts and expiry dates — map to Twenty Opportunities. The quote estimated amount migrates to the Opportunity amount field, expiry date maps to the expected close date, and the quote status (Draft, Sent, Accepted, Lost) maps to a custom OpportunityStage__c pick-list so reporting continuity is preserved.

Fieldmagic Assets (equipment tracked at Sites with serial number, manufacturer, status) have no native Twenty equivalent. We create a custom Asset__c object with custom fields for serialNumber, manufacturer, model, assetStatus, and a siteId relation to Site__c. Asset-to-Job relationships are preserved as a custom jobId relation on Asset__c so maintenance history is queryable.

Fieldmagic Tasks (to-dos linked to Jobs or Contacts) map directly to Twenty's native Task object. Task subject, body text, due date, assignee, and completion status transfer directly. Category distinctions in Fieldmagic (e.g., Call, Email, Follow-up) are preserved as a custom taskCategory__c select field since Twenty Tasks do not have a native type taxonomy.

Fieldmagic office users and technicians are resolved against Twenty Workspace Members by email address. Unmatched owners are flagged before migration — your admin creates the corresponding Twenty user first or assigns their records to a fallback owner. This step is required before any record with an ownerId can be imported, per Twenty's user-existence prerequisite.

Fieldmagic tags applied to Customers, Contacts, Jobs, and Assets migrate as a custom Tags__c text field on each respective object, with comma-separated values preserved. If tags follow a consistent taxonomy (e.g., service type, priority tier), we can instead create a custom select field with the applicable options for cleaner filtering in Twenty views.

Fieldmagic file attachments (photos, documents, signed forms on Jobs or Assets) are re-uploaded to Twenty via the REST API. Files are associated to their parent record using the Twenty object ID generated during migration. Maximum file size follows Twenty's upload limits; large files are flagged for manual review if they exceed those thresholds.