CRM migration
Field-level mapping, validation, and rollback between Dispatch and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Dispatch
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between Dispatch and Freshsales.
Complexity
BStandard
Timeline
24–72 hours
Overview
Dispatch stores field-service records — customers requesting work, jobs with addresses and time windows, assigned drivers, and service notes. Freshsales CRM uses a structured sales-object model: Leads and Contacts (person records), Accounts (company records), and Deals (opportunity records with pipeline stages). The migration translates Dispatch's customer records into Freshsales Contacts or Accounts depending on whether they represent businesses or individuals, and converts work orders into Deals with custom fields capturing Dispatch job numbers, service types, and priority levels. Driver assignments that exist in Dispatch as user records map to Freshsales Users via email matching, or preserve as custom fields on the deal for audit continuity. Service notes and timestamps migrate as Freshsales Notes and custom datetime fields. Workflows, route-optimization rules, and driver-dispatch algorithms in Dispatch have no Freshsales equivalent — those must be redesigned in Freshsales Workflows or Freshsales Sequences post-migration. FlitStack reads Dispatch via API using scoped read access, sequences the migration so foreign keys resolve correctly, and runs a delta pickup window (24–48 hours) to capture any records modified during cutover.
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 Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dispatch
Customer
Freshsales
Contact
1:1Dispatch customer records (name, email, phone, address) map directly to Freshsales Contact. Business-type customers with a company name map to Contact with Account lookup instead of a standalone contact.
Dispatch
Customer (business type)
Freshsales
Account
1:1When Dispatch customer type is 'Business' or 'Company', the record maps to Freshsales Account. Account.Name pulls from the Dispatch company name field; industry and employee count map as custom fields or use Freshsales standard Industry pick-list.
Dispatch
Work Order
Freshsales
Deal
1:1Dispatch work orders become Freshsales Deals. The job number, service type, and priority level migrate as custom fields on the Deal. Deal.Name is generated from the Dispatch job description or job number for traceability.
Dispatch
Work Order Status
Freshsales
Deal Stage
1:1Dispatch work-order statuses (Pending, Scheduled, In Progress, Completed, Cancelled) map to Freshsales deal stage values. Each status maps to the corresponding stage name in your Freshsales pipeline; probability values are applied per stage from the Freshsales stage configuration.
Dispatch
Work Order Amount
Freshsales
Deal Amount
1:1If Dispatch tracks a service fee or quoted amount on the work order, that value maps directly to Freshsales Deal.Amount. If no amount exists, the field is left blank.
Dispatch
Service Address
Freshsales
Custom Address Field on Deal
1:1Dispatch jobs carry a service location address that may differ from the customer primary address. Freshsales Deal object does not have a native service-address field — we create a custom multi-line address field on the Deal and populate it from Dispatch's job address data.
Dispatch
Driver
Freshsales
Freshsales User
1:1Dispatch drivers are internal users who complete jobs. If the same people appear as sales reps in Freshsales, FlitStack resolves them by email match to the Freshsales user record. Unmatched drivers preserve as a custom Driver_Assigned__c pick-list on the Deal.
Dispatch
Job Notes
Freshsales
Note
1:1Dispatch job notes migrate as Freshsales Note records, linked to the parent Deal or Contact. Original timestamps are preserved as a custom datetime field since Freshsales Note does not track creation date separately from system CreatedDate.
Dispatch
Work Order Timestamps
Freshsales
Custom Datetime Fields on Deal
1:1Dispatch captures scheduled date, start time, and completion time per job. Freshsales Deal has a CloseDate field only. We create Scheduled_Date__c, Start_Time__c, and Completed_Time__c custom datetime fields on Deal to preserve the full service timeline.
Dispatch
Service Type
Freshsales
Custom Field on Deal
1:1Dispatch job types (repair, installation, inspection, delivery) do not have a Freshsales standard equivalent. A custom pick-list field Service_Type__c is created on Deal, and Dispatch type values are mapped one-to-one into the pick-list options.
Dispatch
Priority
Freshsales
Custom Field on Deal
1:1Dispatch priority levels (Low, Medium, High, Urgent) map to a Freshsales custom pick-list Priority__c on the Deal object. Freshsales does not have a native priority concept on deals.
Dispatch
Attachments
Freshsales
Files
1:1Dispatch files attached to jobs are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Deal or Contact record. File size limits from Freshsales apply — files over 25MB are flagged for manual handling.
| Dispatch | Freshsales | Compatibility | |
|---|---|---|---|
| Customer | Contact1:1 | Fully supported | |
| Customer (business type) | Account1:1 | Fully supported | |
| Work Order | Deal1:1 | Fully supported | |
| Work Order Status | Deal Stage1:1 | Fully supported | |
| Work Order Amount | Deal Amount1:1 | Fully supported | |
| Service Address | Custom Address Field on Deal1:1 | Fully supported | |
| Driver | Freshsales User1:1 | Fully supported | |
| Job Notes | Note1:1 | Fully supported | |
| Work Order Timestamps | Custom Datetime Fields on Deal1:1 | Fully supported | |
| Service Type | Custom Field on Deal1:1 | Fully supported | |
| Priority | Custom Field on Deal1:1 | Fully supported | |
| Attachments | Files1:1 | Mapping required |
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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Dispatch data and design Freshsales schema
FlitStack connects to Dispatch via scoped read access and exports the full record inventory: customer count, work order volume, active driver count, attachment count, and custom fields in use. We then deliver a Freshsales schema design document specifying which custom fields to create (Job_Number__c, Service_Type__c, Priority__c, Scheduled_Date__c, Driver_Assigned__c, Service_Address__c), which pipeline and deal stages to configure, and whether your Freshsales plan supports the field types required.
Resolve Dispatch drivers to Freshsales users by email
FlitStack extracts the driver email list from Dispatch and compares it against Freshsales user emails. Matched drivers become Deal owners in Freshsales. Unmatched drivers are reported with the driver name, Dispatch ID, and last assignment date — your team either creates Freshsales users for them before migration or accepts the Driver_Assigned__c custom-field fallback.
Migrate accounts and contacts first, then work orders as deals
Freshsales requires Accounts before Contacts (for AccountId lookups) and Contacts before Deals (for ContactId on opportunity contact roles). FlitStack sequences the migration: Account records from Dispatch customers (business type), then Contact records from Dispatch customers (individual type), then Deals from Dispatch work orders with ContactId and custom fields populated. This ordering ensures foreign keys resolve on the first pass.
Run a sample migration with field-level diff
A representative slice of 100–300 records migrates first — spanning contacts, accounts, deals, and attached notes. FlitStack generates a field-level diff report comparing source Dispatch values against the Freshsales destination fields. You verify that service types, priority levels, job numbers, scheduled dates, and driver assignments landed correctly before the full run commits.
Cut over with delta-pickup window for in-flight records
The full migration loads all Dispatch records into Freshsales. A 24–48 hour delta-pickup window runs concurrently, capturing any work orders modified or created in Dispatch during the cutover period. Audit log records every operation. If reconciliation finds missing or mismatched records, one-click rollback reverts the Freshsales state to the pre-migration snapshot so the run can be corrected and repeated.
Platform deep dives
Dispatch
Source
Strengths
Weaknesses
Freshsales
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 Freshsales.
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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Dispatch to Freshsales 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 Freshsales
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.