Migrate from Dispatch Pro to Twenty CRM

Twenty has no native dispatch or job object — custom object required for job records

Dispatch Pro models its entire data structure around Jobs, Technicians, and Service Locations. Twenty CRM has no built-in job or service-visit object — its standard model is People, Companies, Opportunities, Notes, Tasks. We create a Service Job custom object with fields for job type, status, priority, arrival window, zone, and technician assignment. This works correctly in Twenty's API, workflow builder, and views, but it means job records live in a custom object rather than a standard one. Twenty's workflow builder can trigger on Service Job field changes, send notifications, and update related records — so dispatch automation logic can be rebuilt there. The key constraint is that all custom fields must exist in Twenty's data model before import runs; the CSV import process creates records but not fields.

Dispatch Pro technician records must be invited to Twenty as Workspace Members before import

Twenty's import system enforces referential integrity — any relation field (e.g., assignedTechnicianId pointing to a People record) requires the target record to exist at import time. If a Dispatch Pro technician has no corresponding Twenty user, their job assignments cannot be linked during import and will land without an assigned technician. We flag all unmatched technician emails before migration begins. Your team must invite those technicians to Twenty and wait for account acceptance before we run the full import. Dispatch Pro technician skill sets and trade licenses migrate as custom multi-select fields on the People record rather than as native Twenty fields, since Twenty has no built-in skill-license model.

Dispatch Pro workflow logic — auto-dispatch rules, priority optimization, route optimization — has no Twenty equivalent and must be rebuilt

Dispatch Pro's core value is its optimization engine: route-based scheduling, skill-matching, priority bucket weighting, and zone routing. Twenty's workflow builder handles conditional field updates and notifications — it can update a Service Job's status when a technician marks a task complete, or send an email when a job is created. However, Twenty does not have a native route-optimization algorithm, dynamic priority re-weighting based on monetary value, or skill-vs-zone matching logic. Any Dispatch Pro rules that govern how jobs are automatically assigned or reshuffled must be rebuilt in Twenty's workflow builder or via the Twenty API. We export your Dispatch Pro rule definitions as a structured reference document to support the rebuild effort.

Twenty's CSV import has a 20,000-record per-export cap — large job archives require API-based migration

Twenty's UI-based CSV import caps exports at 20,000 records per file. Dispatch Pro setups with multi-year job histories, large customer bases, or multiple business units routinely exceed this. We handle oversized migrations by using Twenty's REST and GraphQL API for batch record creation, bypassing the UI export limit entirely. The API path also gives us fine-grained control over field-level validation and allows us to import in the correct dependency order (Companies → People → Service Locations → Service Jobs) without the manual chunking that CSV-only migrations require.

Dispatch Pro's pricing model (per Managed Technician) does not translate to Twenty's per-seat model

Dispatch Pro bills on the number of managed technicians — the software cost scales with dispatch capacity rather than user count. Twenty bills per active workspace member, regardless of whether that member is a technician, dispatcher, or admin. For teams where not all ServiceTitan users are technicians, the per-seat model can reduce costs. For teams where the technician-to-admin ratio is 1:1, costs may be comparable. We provide a pre-migration cost comparison based on your current Dispatch Pro/ServiceTitan headcount versus Twenty's Cloud Pro ($9/user/month) or self-hosted infrastructure costs, so the financial model is clear before migration begins.