CRM migration

Migrate from Dispatch to Nutshell

Field-level mapping, validation, and rollback between Dispatch and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Dispatch logo

Dispatch

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Dispatch and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Dispatch logo

Dispatch

What's pushing teams away

  • Software upgrades and major feature changes have caused disruptions to existing workflows, with some users reporting that new versions alter functions they rely on daily.
  • Customers note that Dispatch costs more than they expected given the feature set, particularly when they need capabilities available only in higher tiers.
  • Some users report that Dispatch lacks the depth to function as a true CRM, making it difficult to capture and manage comprehensive customer relationship data over time.
  • The platform does not integrate natively with some third-party tools that businesses already use, leading teams to maintain duplicate records or manual workarounds.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Dispatch objects map to Nutshell

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

maps to

Nutshell

Account

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Person

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Lead

1:1
Fully supported

If 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

maps to

Nutshell

Opportunity (with custom fields)

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Opportunity Stage

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Account address fields / Person address fields

1:1
Fully supported

Dispatch 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)

maps to

Nutshell

Activity (call, email, note)

1:1
Fully supported

Dispatch 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)

maps to

Nutshell

Custom Field (Nutshell)

1:1
Fully supported

Nutshell 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

maps to

Nutshell

User

1:1
Fully supported

Dispatch 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

maps to

Nutshell

File (linked to Account or Person)

1:1
Fully supported

Dispatch 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.

Gotchas + challenges

What specifically takes care here

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 logo

Dispatch gotchas

High

API export endpoints gated by Dispatch360 tier

Medium

Work Order history split across open and closed states

Medium

Custom fields require discovery mapping before import

Low

Attachment extraction requires separate file-store access

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Nutshell has no native job or service-ticket object

    Dispatch stores work orders, service tickets, and routing records as primary objects. Nutshell's data model has Accounts, People, Leads, and Opportunities — there is no native job or service ticket object. Any operational records you want to preserve must become Opportunities in Nutshell, with Dispatch-specific attributes stored in custom fields. This means Nutshell's pipeline view will show job records as Opportunities, which works for reporting but requires setup of custom fields for technician, vehicle, and service-type data before migration data lands. We surface this as a pre-migration checklist item and can create the custom fields in Nutshell on your behalf.

  • Nutshell API uses JSON-RPC over HTTPS with basic auth and per-key rate limits

    Nutshell's API is JSON-RPC over HTTPS and uses HTTP Basic authentication with an API token. This differs from OAuth 2.0 flows used by some CRMs. API keys are scoped per user, and impersonation can be enabled per key so changes log as the impersonated user. Rate limits are enforced per key — the Nutshell API returns 429 responses when limits are exceeded, requiring backoff logic during migration. We build retry logic with exponential backoff into the migration pipeline to handle this without data loss or duplicate records.

  • Routing and dispatch automation do not migrate

    Dispatch's automated routing, driver assignment, and scheduling logic are operational constructs with no equivalent in Nutshell's sales CRM model. Nutshell does not have a routing engine, driver management module, or service scheduling calendar. Automated dispatch sequences cannot be exported from Dispatch and rebuilt in Nutshell — they require a different tool category (dedicated field service software or scheduling platform). We export Dispatch workflow definitions as a reference document for rebuilding in your chosen scheduling tool, but the logic itself does not transfer.

  • Custom field limits vary by Nutshell plan tier

    Nutshell supports custom fields on Company, Person, and Lead objects, but the number of custom fields allowed per object varies by plan tier. Dispatch setups with many custom fields on jobs, customers, or drivers may exceed Nutshell's lower-tier limits. We audit your Dispatch custom field count before migration and flag any that require a plan upgrade or consolidation. Fields that cannot be created in Nutshell are preserved as reference data in a custom object or attached note.

  • People must link to an Account in Nutshell's data model

    Nutshell's Person records are strongly associated with Account records. A Person without a linked Account is valid but limits reporting and activity tracking. Dispatch contacts that have no associated company will land as standalone Person records in Nutshell, which is acceptable but reduces the ability to run company-level reports. We flag standalone Person records before the migration runs and let you decide whether to create placeholder Account records or accept the standalone setup.

Migration approach

Six steps for a successful Dispatch to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Dispatch logo

Dispatch

Source

Strengths

  • Visual drag-and-drop dispatch board for real-time job scheduling and technician assignment.
  • Automated customer notifications for appointment confirmations, reminders, and technician ETA updates.
  • Integrated asset and equipment tracking linked directly to work orders for field visibility.
  • Real-time technician status updates and GPS-based routing for service dispatch.
  • Tiered pricing from Starter to Enterprise accommodates growing field service businesses.

Weaknesses

  • API access and bulk data export capabilities are tier-gated, making large-scale migrations dependent on the customer's plan level.
  • Customers report that software upgrades occasionally disrupt established workflows and require relearning.
  • Cost increases at higher tiers for advanced features make the platform less competitive for small businesses on a budget.
  • Limited native CRM depth — Dispatch does not function well as a standalone customer relationship management tool.
  • Attachment storage and management on jobs has size and format restrictions that can complicate data export.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Dispatch and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Dispatch: Not publicly documented.

  • Data volume sensitivity

    B

    Dispatch doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Dispatch to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Dispatch to Nutshell data migrations

Answers to the questions buyers ask most during Dispatch to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Dispatch to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Dispatch-to-Nutshell migrations complete in 24–72 hours of clock time for under 5,000 total records. The longest planning step is designing the custom fields for job data and confirming the Opportunity stage mapping with your team. Larger migrations with over 50,000 records or complex job-to-Opportunity transformations extend to 3–7 days. A sample migration with reconciliation report typically runs within 4–8 hours of the migration starting.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dispatch.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day