Migrate from Q Dispatch to Nutshell

Q Dispatch customer records map directly to Nutshell People. Name, phone, email, and address fields migrate as-is. Primary service address becomes a custom address field if the customer's location differs from billing. Original Q Dispatch customer ID is stored as a custom field for traceability.

Q Dispatch company records (if separate from customer) map to Nutshell Companies. Company name, domain, industry, and billing address translate directly. If Q Dispatch stores customer business information on the customer record rather than a separate company, FlitStack creates a Nutshell Company from that data to maintain CRM hygiene.

Q Dispatch work orders become Nutshell Deals. The work order number becomes the Deal name. Work order status (Requested, Dispatched, In Progress, Completed) maps to Nutshell Pipeline stages — you define the stage mapping during planning. Amount or service fee from the work order migrates as the Deal value.

Each Q Dispatch work order status (e.g., Open, Scheduled, In Progress, On Hold, Completed, Cancelled) requires value-by-value mapping to Nutshell Pipeline stages. FlitStack surfaces your status list during planning and proposes a stage mapping aligned with your Nutshell pipeline configuration.

Q Dispatch technician records map to Nutshell Users by email match. Active technicians become active Nutshell users with full platform access. Technicians without email addresses are flagged for manual user creation or assignment to a fallback owner before migration begins. FlitStack generates a technician-to-user resolution report during planning to identify any email mismatches that need team review.

Q Dispatch work order assignments (which technician is assigned) translate to Nutshell Deal owner assignment. The matched Nutshell User becomes the Deal owner. If multiple technicians were historically assigned to a job, the primary assignee becomes the owner and others surface as Deal collaborators.

Q Dispatch service categories (e.g., HVAC Repair, Electrical, Plumbing) do not have a native Nutshell equivalent. These migrate as a custom pick-list field (Service_Category__c) on the Deal object, populated per work order during migration. Your Nutshell admin configures the pick-list values before the full run.

Q Dispatch work order notes, technician comments, and parts used records migrate as Nutshell Notes attached to the corresponding Deal. Original timestamps and author information are preserved. If notes contain structured data (parts lists), that content migrates as-is within the Note body.

Q Dispatch activity log entries — including status changes, assignment events, dispatch actions, and completion records — migrate as Nutshell Tasks with Type='Logged Activity' on the Deal record. Original timestamps, associated technician names, and event descriptions are all preserved for full audit continuity and historical reference in the new CRM system.

Q Dispatch parts used on work orders have no direct Nutshell equivalent. FlitStack creates a custom text area field (Parts_Used__c) on the Deal to capture the parts list. For invoiced amounts, a separate custom currency field (Parts_Value__c) captures the parts total if separate from the service fee.

Q Dispatch service address (where the job was performed) differs from the customer's billing address in many field-service records. FlitStack creates Service_Address__c and Service_City__c custom fields on the Nutshell Person record to preserve location data without overwriting the standard address fields.

Q Dispatch custom fields on work orders (priority level, billing code, work order source, PO number) map to custom fields on Nutshell Deals. Each custom field requires a matching Nutshell custom field created before migration — FlitStack provides a field creation checklist as part of the migration plan.

Q Dispatch routing rules, automatic assignment logic, and schedule-based triggers do not have an equivalent in Nutshell. FlitStack exports the automation definitions as a configuration reference document for your Nutshell admin to rebuild manually in Nutshell's workflow builder after migration.