CRM migration
Field-level mapping, validation, and rollback between Dispatch and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Dispatch
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Dispatch and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Teams migrate from Dispatch to Nutshell when they need a CRM that is built for sales pipeline management rather than field service scheduling. Dispatch stores operational records — customers, drivers, jobs, routes, service status — but its data model is flat: contacts and companies live in one object graph without a distinction between leads and customers. Nutshell splits People and Leads into separate objects and models business development as Accounts and Opportunities. The migration carries over everything Dispatch stores natively: accounts, people, deals (migrated as Opportunities with custom fields for Dispatch-specific attributes like technician and vehicle assignment), activities, and any custom fields. The harder problems are deciding which operational records to migrate as Opportunities, mapping Dispatch job status into Nutshell Opportunity Stage values, and creating the custom fields Nutshell requires for technician assignment, vehicle ID, and service-type attributes that have no native equivalent in a sales CRM. We also preserve original create dates and job status history, ensuring your sales team sees the full context of each customer relationship from the first point of contact.
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 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
Customer
Nutshell
Account
1:1Dispatch customers map directly to Nutshell Accounts. Address, phone, website, and industry fields migrate as Account fields. Nutshell requires that each Person have a primary AccountId; customers without an associated company land as standalone Person records. We preserve the original customer create date as a custom field for audit purposes.
Dispatch
Contact
Nutshell
Person
1:1Dispatch contacts map to Nutshell People. Name, email, phone, title, and address fields transfer directly. Nutshell People support custom fields for Dispatch-specific attributes like driver ID or customer tier that do not have native equivalents. These custom fields ensure data continuity after migration.
Dispatch
Lead
Nutshell
Lead
1:1If Dispatch tracks prospective customers separately, those records migrate to Nutshell Leads with status, source, and any assigned owner. Nutshell's Lead object supports custom fields for stage and qualification notes from Dispatch. We also preserve any lead scoring data in custom fields.
Dispatch
Job / Work Order
Nutshell
Opportunity (with custom fields)
1:1Dispatch jobs do not have a native equivalent in Nutshell. FlitStack migrates each job as a Nutshell Opportunity, using custom fields — Dispatch_Job_Number__c, Dispatch_Status__c, Technician__c, Vehicle_ID__c, and Service_Type__c — to carry Dispatch-specific attributes. Opportunity Stage is mapped from Dispatch job status.
Dispatch
Job Status
Nutshell
Opportunity Stage
1:1Dispatch job statuses (Open, Scheduled, In Progress, Completed, Cancelled) map to Nutshell Opportunity Stage values. We apply a value-by-value mapping with your team confirming stage names before the migration runs. Each status becomes a stage in Nutshell so the pipeline view reflects the full job lifecycle.
Dispatch
Address / Location
Nutshell
Account address fields / Person address fields
1:1Dispatch address fields migrate to Account billing and shipping address on the company record. If a Dispatch location is associated with a specific person rather than a company, the address migrates to the Person record. Multi-stop routing data does not have an equivalent in Nutshell and is preserved as a reference note.
Dispatch
Activity (call, email, note)
Nutshell
Activity (call, email, note)
1:1Dispatch call logs, emails, and notes migrate as Nutshell Activities linked to the corresponding Account or Person record. Original timestamps and activity owners are preserved. Activity type maps to Nutshell's activity type field (Call, Email, Note). for complete historical context.
Dispatch
Custom Field (Dispatch)
Nutshell
Custom Field (Nutshell)
1:1Nutshell supports custom fields on Company, Person, and Lead objects. Dispatch custom fields on customers and jobs migrate as Nutshell custom fields. Fields that apply to Dispatch jobs attach to Opportunities in Nutshell. Nutshell's custom field creation interface handles field type selection (text, number, date, pick-list) based on the source data type.
Dispatch
User / Owner
Nutshell
User
1:1Dispatch users are matched to Nutshell users by email address. Unmatched owners are flagged before migration so your team can create Nutshell users or assign Dispatch records to a fallback owner. Ownership assignments on jobs and contacts transfer as OwnerId in Nutshell.
Dispatch
Attachment / File
Nutshell
File (linked to Account or Person)
1:1Dispatch file attachments associated with customers or jobs re-upload to Nutshell as linked Files. Nutshell's file size limits apply. We re-upload files and link them to the corresponding Account or Person record, preserving the original filename and any description from Dispatch.
| Dispatch | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Account1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Job / Work Order | Opportunity (with custom fields)1:1 | Fully supported | |
| Job Status | Opportunity Stage1:1 | Fully supported | |
| Address / Location | Account address fields / Person address fields1:1 | Fully supported | |
| Activity (call, email, note) | Activity (call, email, note)1:1 | Fully supported | |
| Custom Field (Dispatch) | Custom Field (Nutshell)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Attachment / File | File (linked to Account or Person)1: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 gotchas
API export endpoints gated by Dispatch360 tier
Work Order history split across open and closed states
Custom fields require discovery mapping before import
Attachment extraction requires separate file-store access
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
Export and profile Dispatch data
We connect to Dispatch via your API credentials and extract all accounts, people, jobs, activities, and custom field definitions. The export is profiled to surface record counts, null-field rates, duplicate candidates, and any custom field types that require special handling during mapping. This profile drives the migration plan and identifies any records that need deduplication or cleanup before they land in Nutshell.
Design Nutshell custom fields and Opportunity stage mapping
Based on the Dispatch data profile, we create the custom fields Nutshell requires for job records — Dispatch_Job_Number__c, Dispatch_Status__c, Technician__c, Vehicle_ID__c, Service_Type__c — and map Dispatch job status values to Nutshell Opportunity Stage values. You confirm stage names and any value mappings before data is written. This step runs in your Nutshell environment using your admin credentials for a smooth transition.
Resolve Dispatch users to Nutshell users by email
Dispatch owner and user IDs are matched against Nutshell user email addresses. Unmatched owners are flagged with the records they own so your team can create Nutshell users, invite them to the workspace, or reassign their Dispatch records to a designated fallback owner. No record migrates without a resolved or flagged owner. This ensures accountability and accurate reporting across the new CRM.
Migrate accounts, people, then jobs as Opportunities
We sequence the load to respect Nutshell's foreign-key constraints: Accounts first, then People linked to those Accounts, then Opportunities linked to Accounts and People. Activities load last, linked to their parent records. Each batch is validated against Dispatch source counts before the next batch starts. Job data loads as Opportunities using the custom fields and stage mapping established in step 2.
Run a sample migration with reconciliation report
A representative slice — typically 100–300 records covering accounts, people, jobs, and activities — migrates first. We generate a field-level reconciliation report comparing source values against destination values so you can verify name formatting, address handling, stage mapping, and technician assignment before the full run commits. You sign off on the sample before the full migration begins and approval for final go-ahead.
Execute full migration with delta pickup window
The full dataset migrates into Nutshell. A delta-pickup window of 24–48 hours captures any records created or modified in Dispatch during the cutover. All migration operations are logged to an audit trail. If reconciliation fails — record counts do not match or custom field values are missing — one-click rollback reverts the Nutshell environment to its pre-migration state so the issue can be diagnosed and the migration rerun.
Platform deep dives
Dispatch
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 and Nutshell.
Object compatibility
2 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: Not publicly documented.
Data volume sensitivity
Dispatch 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 to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Dispatch 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
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.