CRM migration
Field-level mapping, validation, and rollback between Dispatch Pro and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Dispatch Pro
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Dispatch Pro and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Dispatch Pro is a field-service dispatching platform built around jobs, technicians, and location-based scheduling. Nutshell is a standard small-to-mid-market CRM organized around People, Companies, Leads, Deals, and Activities. The core migration challenge is that Dispatch Pro's job-centric data model does not map 1:1 to Nutshell's contact-and-opportunity model — jobs become Deals, customers become linked People and Company records, and technician assignments require user resolution by email against Nutshell's user list. We extract Dispatch Pro data via the ServiceTitan API (contacts, companies, jobs, activities, custom properties) and load into Nutshell via its JSON-RPC API and bulk import endpoints. Workflows, dispatch optimization rules, and technician scheduling logic do not transfer — those must be rebuilt in Nutshell or documented for manual recreation. Attachments and files are re-uploaded to Nutshell's file storage. A 24–48 hour delta-pickup window captures any records modified during the cutover window so the final Nutshell state matches Dispatch Pro's go-live snapshot.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Dispatch Pro object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dispatch Pro
Customer (Contact/Company hybrid)
Nutshell
Person + Company
1:manyDispatch Pro stores customer data as a combined record with both person and company attributes. We split this into a Nutshell Person record (name, email, phone) and a Nutshell Company record (company name, address, industry). The link between them is preserved as a Nutshell Person-Company association.
Dispatch Pro
Location / Service Address
Nutshell
Company Address Fields
1:1Dispatch Pro locations include address details, latitude/longitude coordinates, site access notes, and location-specific tags. These migrate as standard address fields on the Nutshell Company record. Access instructions and site tags are stored as custom text fields on the Company record since Nutshell lacks a native location-notes object for site-specific details.
Dispatch Pro
Job
Nutshell
Deal
1:1Dispatch Pro jobs map directly to Nutshell Deals. Job name becomes Deal name, job amount becomes Deal value, and job status maps to a Nutshell pipeline stage. Each job carries a customer link and a technician assignment — both resolved during migration.
Dispatch Pro
Job Priority / Priority Bucket
Nutshell
Custom Field on Deal
1:1Dispatch Pro supports up to eight priority buckets for algorithmic optimization. Nutshell has no native job-priority field. We create a custom pick-list field (Job_Priority__c) on Nutshell Deals and map Dispatch Pro priority values value-by-value so managers can filter by priority in Nutshell's list and board views.
Dispatch Pro
Technician / Technician Group
Nutshell
User
1:1Dispatch Pro technicians are matched to Nutshell users by email address. If a technician email does not match an existing Nutshell user, we flag the record for your admin to create the user or assign a fallback. Technician groups (teams, zones, trade licenses) are stored as custom fields on the Nutshell User record.
Dispatch Pro
Job Activity / Status Log
Nutshell
Activity (Call, Task, Note)
1:1Dispatch Pro logs job status changes, technician check-ins, and work completion events with timestamps and the acting technician. These migrate as Nutshell Activities — status transitions become Note records with the original timestamp and technician as owner. Job completion events become completed Task records.
Dispatch Pro
Custom Property (Job-level)
Nutshell
Custom Field on Deal
1:1Dispatch Pro custom properties on jobs (e.g., equipment model, warranty type, service contract ID) map to Nutshell custom fields on the Deal object. We create each custom field in Nutshell before migration, inferring the field type (text, number, date, pick-list) from Dispatch Pro's property definition.
Dispatch Pro
Custom Property (Customer-level)
Nutshell
Custom Field on Person / Company
1:1Customer-level custom properties in Dispatch Pro — such as customer tier classifications, billing preference settings, and contract expiry dates — migrate as Nutshell custom fields on either the Person or Company object, depending on whether the property applies to the individual contact or the organization as a whole.
Dispatch Pro
Attachment / Photo / Document
Nutshell
File
1:1Job photos, attached documents, and signed forms from Dispatch Pro are downloaded and re-uploaded to Nutshell Files, linked to the corresponding Deal record. File size limits apply (Nutshell's default upload ceiling per file). Inline images in notes are extracted and rehosted.
Dispatch Pro
Dispatch Pro Settings / Optimization Rules
Nutshell
No Equivalent
1:1Dispatch Pro's priority buckets, technician skill mappings, zone assignments, and algorithmic optimization settings are platform configuration — not user data. These have no Nutshell equivalent and cannot be migrated. We export the full configuration as a JSON reference file for your team to manually recreate routing logic in Nutshell or a third-party scheduling tool.
| Dispatch Pro | Nutshell | Compatibility | |
|---|---|---|---|
| Customer (Contact/Company hybrid) | Person + Company1:many | Fully supported | |
| Location / Service Address | Company Address Fields1:1 | Fully supported | |
| Job | Deal1:1 | Fully supported | |
| Job Priority / Priority Bucket | Custom Field on Deal1:1 | Fully supported | |
| Technician / Technician Group | User1:1 | Fully supported | |
| Job Activity / Status Log | Activity (Call, Task, Note)1:1 | Fully supported | |
| Custom Property (Job-level) | Custom Field on Deal1:1 | Fully supported | |
| Custom Property (Customer-level) | Custom Field on Person / Company1:1 | Fully supported | |
| Attachment / Photo / Document | File1:1 | Fully supported | |
| Dispatch Pro Settings / Optimization Rules | No Equivalent1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Dispatch Pro gotchas
Dispatch Pro is a ServiceTitan-only licensed module
Optimization behavior may not carry over after migration
Slow support response during migration cutover
Eight priority levels may not map 1:1 to destination CRM
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit Dispatch Pro data export and map to Nutshell schema
FlitStack connects to the ServiceTitan API and extracts all accessible records: customers, companies, jobs, activities, custom properties, and attachments. We generate a pre-migration audit report showing record counts per object, custom property definitions, technician email list, and any data-quality issues (missing emails, invalid dates, orphaned jobs). This report determines the exact Nutshell custom fields needed and flags technician accounts that need pre-creation.
Create Nutshell custom fields and user accounts
Before data moves, FlitStack creates the custom fields identified in the audit — including Job_Priority__c, Job_Type__c, Technician_Group__c, Trade_License__c, Original_Create_Date__c, and any customer-level custom fields — on the appropriate Nutshell objects (Deal, Person, Company, User). Your admin must pre-create Nutshell user accounts for technicians whose emails did not resolve to an existing user, or designate a fallback owner. We deliver a setup checklist documenting every required field and account so nothing is missed before validation runs.
Resolve technician emails and job-customer links
FlitStack runs the technician email resolution step, matching Dispatch Pro technician IDs to Nutshell user IDs by email. Any unmatched technician is flagged with a recommendation (create user or assign fallback). Simultaneously, we validate that all jobs reference an existing customer, flagging any job with a missing or invalid customer link so those records can be corrected or excluded before the migration commits.
Run sample migration with field-level diff
A representative sample — typically 100–500 records spanning customers, companies, jobs, and activities — migrates first. FlitStack generates a field-level diff comparing source Dispatch Pro values against the resulting Nutshell record so you can verify priority-bucket mapping, pipeline stage assignment, technician resolution, and activity log completeness before the full migration run. You approve the sample output or request mapping adjustments before we proceed.
Execute full migration with delta-pickup window
The full data export loads into Nutshell. A 24–48 hour delta-pickup window runs simultaneously, capturing any Dispatch Pro records modified or created during the cutover. Audit logs record every operation. One-click rollback is available if reconciliation identifies a mismatch. After delta pickup closes, FlitStack delivers a final reconciliation report showing record counts, error log, and any unmapped fields for manual review.
Platform deep dives
Dispatch Pro
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dispatch Pro and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Dispatch Pro: Not publicly documented in available research.
Data volume sensitivity
Dispatch Pro doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Dispatch Pro to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Dispatch Pro to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Dispatch Pro
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.