Migrate from Q Dispatch to Twenty CRM

Q Dispatch customers with business names map directly to Twenty Companies. The customer address migrates as the company address fields. If Q Dispatch stores multiple service locations per customer, the primary location becomes the Company record and additional locations require a custom ServiceLocation object in Twenty.

Q Dispatch contact names, emails, and phone numbers migrate to Twenty People records. The companyId field links each Person to the corresponding Company record. Q Dispatch allows multiple contacts per customer — all migrate with the same companyId relationship preserved.

Q Dispatch work orders map to Twenty Opportunities. The work order number becomes the opportunity name. Job status values (Pending, Scheduled, In Progress, Completed) map to Twenty opportunityStage pick-list values that your admin creates before import. Stage-entered timestamps preserve history.

If Q Dispatch stores multiple line items or service types per work order, these merge into a single Opportunity with a description field aggregating the services. For granular tracking, your admin creates a custom ServiceItem object in Twenty before migration.

Q Dispatch technicians map to Twenty Workspace Members by email resolution. Technicians must receive Twenty invitations before migration runs — unmatched technicians are flagged and records assigned to a fallback Workspace Member. Shift and region data from Q Dispatch becomes custom fields on the Workspace Member record.

Q Dispatch service locations attach to customers as separate addresses. When your Q Dispatch setup stores service addresses distinct from the primary customer billing address, both addresses consolidate into the Company record's standard address fields. Any service-location-specific notes or special instructions transfer into a custom addressNote field created on the Company object to preserve important operational details.

Q Dispatch job notes and dispatch communication history migrate as Twenty Notes attached to the corresponding Opportunity. The original timestamps and creating user's email address are preserved on each Note. Notes link to the Opportunity via the relation import method using the Opportunity's id field, ensuring all communication context transfers with the work order record.

Q Dispatch file attachments on work orders re-upload to Twenty's storage during migration. Any inline images embedded in job notes are extracted, downloaded, and rehosted as NoteAttachments linked to the parent Note record. File size restrictions apply based on your Twenty storage configuration, and we validate attachment compatibility before the migration batch commits.

Q Dispatch custom fields on work orders require pre-creation in Twenty's Settings → Data Model before import. Field types map as: text → text, number → number, date → date, picklist → select. If Q Dispatch stores field options not supported by Twenty select, they become text fields with original values preserved.

Q Dispatch custom fields on customers migrate as custom fields on Twenty Company or Person objects based on whether the field applies to the business or the contact. Your admin creates these in Twenty Data Model first. Relationship custom fields (e.g., preferred technician) resolve by email match before migration.

Q Dispatch routing rules, technician-to-job assignment logic, and auto-dispatch automations have no equivalent in Twenty CRM. These must be rebuilt in Twenty's workflow builder using triggers on Opportunity creation and status changes. FlitStack exports your Q Dispatch routing logic as a rebuild reference document.

Q Dispatch reports and dashboards do not migrate. The underlying work order and customer data populates Twenty's standard views and filters after migration. Your team configures new reports in Twenty using the imported Opportunity and Company data as the source.