Migrate from Dispatch Pro to Freshsales

Dispatch Pro Customer maps directly to Freshsales Contact. Name, email, phone, mobile, job title, and address fields carry over as-is. The Customer's linked Company becomes the Contact's parent Account lookup. If a Dispatch Pro Customer has no linked Company, a default Account record is created. Original create/update timestamps are preserved as custom datetime fields on the Contact record.

If Dispatch Pro records contain leads (prospective customers not yet converted to active service), those route to Freshsales Lead. Freshsales Lead supports custom fields for source system reference, allowing the original Dispatch Pro customer status to be preserved. Existing Contacts are matched by email to prevent duplicate creation.

Dispatch Pro Company maps directly to Freshsales Account. Name, domain/website, industry, number of employees, and annual revenue transfer as standard fields. Parent/child company hierarchies map to Freshsales Parent Account lookup. Billing and shipping addresses transfer to the Account address fields.

Dispatch Pro Job is the primary migration record. Each Job becomes a Freshsales Deal using the default pipeline. Deal Name is constructed from Customer name + Job number. Amount carries over from Job total. Deal Stage maps from Job status: Scheduled → Appointment Scheduled, In Progress → Negotiation, Completed → Closed Won, Cancelled → Closed Lost. Close date maps from Job scheduled date.

Dispatch Pro Priority level (up to 8 buckets) has no native Freshsales equivalent on the Deal object. A custom pick-list field (Priority__c) is created on Deals, preserving all Dispatch Pro priority values. Stage-entered timestamps are mapped to Freshsales Deal custom datetime fields for reporting continuity on when each priority level was assigned.

Dispatch Pro Service Types define the category of work performed (e.g., HVAC Repair, Plumbing, Electrical). Freshsales has no native service-type field on Deals. We create a custom pick-list field (Service_Type__c) on the Deal object, preserving the full set of Dispatch Pro service type values. If Service Types have sub-types, those map to a secondary custom field or are concatenated.

Dispatch Pro line items attached to Jobs (parts, labor rates, flat fees) migrate as Freshsales Deal Products. Product Name, quantity, unit price, and discount carry over. If Dispatch Pro uses a price book, we map to Freshsales Products and link them to the Deal. Standalone estimates without a converted Job become Open Deals with a zero amount flagged for review.

Dispatch Pro Technicians are resolved to Freshsales Users by email address match. Unmatched technicians are flagged before migration — either invited to Freshsales or assigned to a fallback user. The technician's Dispatch Pro ID is stored as a custom field (Source_Technician_ID__c) on the Freshsales User for audit traceability. Technician licensing and skill flags that have no Freshsales equivalent are preserved as custom User fields.

Dispatch Pro Zones map to Freshsales Territories if the account is on Pro tier or above, which includes Territory Management. Zones without a matching Territory are stored as a custom text field (Zone__c) on the Deal. Territory boundaries require manual configuration in Freshsales admin settings post-migration.

If Dispatch Pro uses multiple Business Units, each unit's Jobs can map to separate Freshsales Pipelines (one pipeline per business unit). Each pipeline has its own stage set, giving business-unit-specific reporting. Alternatively, Business Unit is stored as a custom field on Deals for simpler single-pipeline setups. FlitStack surfaces both options during discovery.

Job-level notes, internal comments, and activity history migrate as Freshsales Notes attached to the Deal. Timestamps and author information (technician name) are preserved. If Dispatch Pro records include call logs or SMS threads tied to a Job, those migrate as Freshsales Tasks with Type set to 'Call' or 'SMS'.

File attachments on Dispatch Pro Jobs (photos, signed forms, invoices) are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Deal record. File size limits apply — Freshsales default file upload limit is 25MB per file. Large files or inline images in notes are downloaded and rehosted.

Any custom fields defined in Dispatch Pro on Customer, Company, or Job objects are audited before migration. Each custom field is created as a corresponding custom field in Freshsales on the mapped object (Contact, Account, Deal). Field type mapping: text → text, number → number, pick-list → pick-list, date → date. Custom fields with no valid Freshsales type are stored as text.

Dispatch Pro Invoices tied to completed Jobs have no direct Freshsales equivalent unless the Freshsales billing add-on is active. We link the Invoice reference (number, date, amount, status) as a custom field on the associated Deal (Invoice_Number__c, Invoice_Date__c, Invoice_Status__c). If invoicing is critical, Freshsales billing modules or a third-party integration must be configured post-migration.