CRM migration

Migrate from Dispatch Pro to Nutshell

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

Dispatch Pro logo

Dispatch Pro

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Dispatch Pro and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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 Pro logo

Dispatch Pro

What's pushing teams away

  • Slow support response times frustrate users who encounter issues during critical dispatch periods — one G2 reviewer cited that support tickets take much time to resolve.
  • Major software upgrades in ServiceTitan have been reported to break or change existing dispatch workflows, forcing dispatchers to relearn their tools after each release.
  • Some users feel the platform has more features than they need and at a higher cost than simpler standalone dispatch tools, prompting consideration of alternatives like Housecall Pro or Jobber.
  • Interface responsiveness is a recurring complaint, with reviewers noting process speed lags that become frustrating during high-volume dispatch days.

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 Pro objects map to Nutshell

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)

maps to

Nutshell

Person + Company

1:many
Fully supported

Dispatch 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

maps to

Nutshell

Company Address Fields

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Deal

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Dispatch 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

maps to

Nutshell

User

1:1
Fully supported

Dispatch 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

maps to

Nutshell

Activity (Call, Task, Note)

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Person / Company

1:1
Fully supported

Customer-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

maps to

Nutshell

File

1:1
Fully supported

Job 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

maps to

Nutshell

No Equivalent

1:1
Fully supported

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

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 Pro logo

Dispatch Pro gotchas

High

Dispatch Pro is a ServiceTitan-only licensed module

Medium

Optimization behavior may not carry over after migration

Medium

Slow support response during migration cutover

Low

Eight priority levels may not map 1:1 to destination CRM

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

  • Dispatch Pro job priority buckets have no native Nutshell equivalent

    Dispatch Pro uses up to eight algorithmic priority buckets to rank jobs for optimization. Nutshell has no native job-priority or scheduling-rank field — pipeline stages handle workflow states, not optimization weights. We create a custom pick-list field (Job_Priority__c) on Nutshell Deals and map Dispatch Pro priority values 1:1, but Nutshell's board view cannot automatically sort or reorder deals by these priority values the way Dispatch Pro's dispatch board does. Teams that rely heavily on priority-based dispatching need to either accept manual sorting in Nutshell or adopt a third-party scheduling integration.

  • Technician-to-user email resolution may leave unassigned jobs

    Dispatch Pro technicians do not have corresponding Nutshell user accounts by default. We match technicians to Nutshell users by email address during migration. Any technician whose email does not resolve to an existing Nutshell user creates unassigned Deal records. Your team must either pre-create Nutshell user accounts for all active technicians or designate a fallback Nutshell user to own unassigned deals before the migration runs. Unresolved assignments are flagged in the pre-migration audit report so there are no orphan records after go-live.

  • Dispatch optimization rules and skill-based routing do not migrate

    Dispatch Pro's core value is its algorithmic optimization engine — matching jobs to technicians by skill, license, zone, and priority in real time. Nutshell has no scheduling optimization engine whatsoever. The optimization rules, technician skill tags, zone assignments, and dispatch-board configuration are platform settings, not user data, so FlitStack cannot transfer them. We export the full Dispatch Pro configuration as a structured JSON reference file so your team can manually recreate routing logic in Nutshell automations or a separate scheduling tool.

  • Job-to-Deal parent relationship requires customer records to exist first

    Nutshell requires Company records to exist before Deals can reference them, and requires Person records to be linked to Companies before Deals can attach those People. Dispatch Pro jobs reference customers directly without this hierarchy. We sequence the migration to load all customers first as separate Company and Person records, then create Deals with resolved customer links. Circular references where jobs point to uncreated companies are flagged during the pre-migration audit to prevent foreign-key failures when the migration executes.

  • Nutshell's per-contact pricing tier caps on total contacts, not active deals

    Nutshell pricing is tiered by contact volume — each tier allows a maximum number of total contacts in the account. Dispatch Pro does not have this constraint. If your Dispatch Pro database has a high ratio of historical customers to active opportunities, the total Nutshell contact count may exceed a lower pricing tier. We report the total contact count during the pre-migration audit so you can confirm which Nutshell plan tier your migrated data will occupy.

Migration approach

Six steps for a successful Dispatch Pro to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Dispatch Pro logo

Dispatch Pro

Source

Strengths

  • One-click job assignment with real-time dispatch board updates shared to technician mobile apps.
  • Filtering and search functionality for quickly locating open work orders by zone, priority, or technician.
  • Up to eight configurable priority levels with optimization logic that respects both monetary value and non-monetary urgency like recalls.
  • Skill-based, zone-based, and trade-license-based technician assignment rules built directly into the optimization engine.
  • Scheduled job locking allows dispatchers to reserve time slots and prevent optimization from reshuffling manually confirmed appointments.

Weaknesses

  • Dispatch Pro is a ServiceTitan-only add-on product — organizations not already on ServiceTitan cannot use it, limiting portability.
  • The platform fills underbooked days for best-performing technicians first, which can disadvantage newer technicians and requires careful monitoring of fairness settings.
  • Support response times are reported as slow, which is critical when dispatch issues arise during active service hours.
  • API documentation and bulk export capabilities are not independently published — migrations require working through ServiceTitan's formal export tools or developer support.
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. 1 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 Pro and Nutshell.

  • Object compatibility

    B

    1 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 Pro: Not publicly documented in available research.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Dispatch Pro 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 Pro to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most Dispatch Pro to Nutshell migrations complete within 48–72 hours of clock time for databases under 25,000 records. Larger setups with 250,000+ records or more than 20 custom job properties extend to 5–7 days. The longest phase is typically the pre-migration audit and custom field creation in Nutshell — your admin should complete those steps before the migration run begins. The actual data transfer and delta-pickup window add minimal time to the overall timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dispatch Pro.
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