Migrate from Dispatch to Twenty CRM

Dispatch customers map directly to Twenty People records. Email, phone, name, and address fields transfer 1:1. Each customer must be linked to a Company record (the service location) using the companyId relation field. We also preserve the original customer ID as a custom field for future data reconciliation and delta imports.

Dispatch stores service addresses on work orders and customer records. These become Twenty Company records with domain (extracted from address if available), name, industry, and address fields. Parent-child location hierarchies in Dispatch map to Twenty's parentCompanyId field, ensuring consistent location hierarchy in Twenty.

Dispatch work orders become Twenty Opportunities. Work order number becomes Opportunity name. Service type, priority, and status map to custom fields on Opportunity. StageName is derived from Dispatch status: 'Scheduled' → 'Prospecting', 'In Progress' → 'Value Proposition', 'Completed' → 'Closed Won', 'Cancelled' → 'Closed Lost'.

Each scheduled dispatch in Dispatch creates a Twenty Task record linked to the corresponding Opportunity (work order) and assigned to the matched technician. Task subject carries the work order number; due date maps from the scheduled date; status reflects Dispatch completion status.

Dispatch technicians are both contacts and system users. They migrate as Twenty People records with a custom pick-list field (Technician_Role__c) set to 'Technician'. Owner/assignment fields on related Opportunities and Tasks reference these People records. Email match resolves to Twenty Workspace Members for Task assignment.

If Dispatch Enterprise is in use and a custom Vehicle object exists, it maps 1:1 to a Twenty custom object named 'Vehicle'. Fields include make, model, year, license plate, and current technician assignment (relation to People). N:N driver-vehicle assignments use a junction object.

Dispatch equipment or asset records used in preventive-maintenance workflows map to a Twenty custom object. Linked to Company (customer site) and Vehicle if applicable. Service history attached as Notes or Tasks on the Equipment record. We also preserve original equipment IDs and maintenance intervals for reference.

Dispatch work order notes, status-change logs, and technician comments become Twenty Notes attached to the corresponding Opportunity. Timestamps and author names are preserved as Note metadata. High-priority flags migrate as a custom boolean field on the Note, ensuring audit trail continuity for each work order.

Dispatch file attachments on work orders are downloaded and re-uploaded to Twenty as Files linked to the corresponding Opportunity. File size limits depend on Twenty hosting configuration. Inline images in notes are extracted and rehosted as separate attachments. We also log the original file names and checksums for verification.

Dispatch's automatic PM drops based on service intervals have no native equivalent in Twenty. We export PM configuration (interval, service type, asset) as a reference document. Twenty's workflow builder can recreate trigger logic after migration, including interval type, trigger conditions, and associated assets.

Dispatch user roles and permission sets do not map to Twenty's permission groups. We export the role structure as a setup reference. Twenty workspace members must be invited before migration; owner/technician references resolve by email match, ensuring correct access control and reporting visibility in Twenty.

Dispatch integrations with GPS tracking, accounting software, or payment processors must be rebuilt separately. We document the connected systems and their purpose so your team can re-establish integrations in Twenty or through middleware, including connection credentials, API endpoints, and data flow descriptions for each integration.