Migrate from ServiceMonster to Freshsales

ServiceMonster customers map to Freshsales Leads (pre-conversion) if they are pre-job or prospect records. Active customers with completed jobs map to Contacts in Freshsales. Email uniqueness determines whether records merge or create new entries. Original customer IDs are preserved as Source_System_ID__c on the Freshsales record.

ServiceMonster has no native deal/opportunity object. Jobs are the closest analogue — we transform them into Freshsales Deals within a configured Sales Pipeline. Job status (Scheduled, In Progress, Completed, Cancelled) maps to Freshsales Deal Stage values via value-by-value mapping. Job amount maps to Deal Amount; scheduled date maps to Close Date.

ServiceMonster appointments linked to jobs map to Freshsales Events if they carry a start/end time and assigned technician. Standalone job notes without time windows map to Freshsales Tasks. Original appointment timestamps, technician assignments, and job associations are preserved on the migrated record.

Freshsales has no native invoice object. We map invoice data (invoice number, total amount, payment status, balance due) to custom fields on the associated Deal. Line items from invoices become Freshsales Products linked to the Deal via Deal Products. Paid invoices retain their original status as Deal custom field values for historical reporting.

ServiceMonster price list items map 1:1 to Freshsales Products. Item name maps to Product Name, SKU to SKU, unit price to Product's base price, and item description to Product Description. Product type or category from ServiceMonster maps to a custom product field in Freshsales.

ServiceMonster routes have no native Freshsales equivalent. Route names and assignments are stored as custom fields on Freshsales Deals. Geographic route groupings are surfaced as Territory assignments in Freshsales for territory-based reporting and auto-assignment rules. Route order is preserved in a custom field for dispatch reference.

ServiceMonster technicians map to Freshsales Users by email address match. Technician name and phone number transfer to the Freshsales User profile. Technicians without a registered email are flagged before migration — your team either creates Freshsales users first or assigns their jobs to a fallback user owner.

ServiceMonster custom fields on customers migrate as Freshsales custom fields on Lead and Contact. Data types (text, number, picklist, date, checkbox) are preserved. Multi-select pick-lists in ServiceMonster map to Freshsales multi-select custom fields. Required field constraints are evaluated post-migration — mandatory ServiceMonster fields that have no Freshsales equivalent become custom fields.

ServiceMonster custom fields on jobs migrate as Freshsales custom fields on Deal. Job-specific properties like job_type, is_warranty, lead_source, and service_category are mapped field-by-field. If a ServiceMonster custom field drives a workflow or automation in ServiceMonster, we flag it so your Freshsales admin can rebuild the automation in Freshsales Workflows.

ServiceMonster job notes, technician comments, and logged communications migrate as Freshsales Sales Activities (type: Note) linked to the corresponding Deal. Original timestamps and author information are preserved. Photos attached to job notes are downloaded and re-uploaded as Freshsales attachments. We also map any linked attachments and ensure file metadata such as creation date and file size are retained in Freshsales.

ServiceMonster service catalog items map to Freshsales Products. The item name, SKU, unit price, and description transfer directly. Product categories from ServiceMonster become Freshsales Product Categories. Bundle and package items in ServiceMonster map to Freshsales Product Bundles. If your catalog includes nested bundles or optional add-ons, those relationships are preserved via Freshsales Product Bundles and can be configured in the Product module after migration.

ServiceMonster account-level tags and custom fields migrate as Freshsales Account custom fields. Tags with multiple values per account map to Freshsales multi-select pick-list custom fields. Account type (residential/commercial) becomes a custom field on the Account record. We also preserve any custom date or numeric fields associated with accounts, ensuring historical data such as contract start dates and account health scores are available in Freshsales.

ServiceMonster admin and office staff users map to Freshsales Users by email match. Name, phone, and role information transfer. If ServiceMonster roles (Dispatcher, Admin, Technician) do not map directly to Freshsales roles, they are preserved as a custom field on the User record for your admin to configure Freshsales permission sets.

ServiceMonster routing rules, dispatch automations, and scheduling workflows have no Freshsales equivalent and cannot be migrated. We export your ServiceMonster workflow definitions (trigger conditions, actions, routing logic) as a structured JSON document that your Freshsales admin can use as a rebuild reference in Freshsales Workflows and Auto-assignment Rules.