Migrate from Salesforce Field Service to Freshsales

Direct 1:1 map. Salesforce Accounts migrate to Freshsales Accounts with name, industry, website, and billing address preserved. Parent-child account hierarchies transfer via Freshsales parent_account_id lookup. Multi-address accounts use the primary billing address as the default. During migration, we preserve any custom account types and territory associations as custom fields to maintain reporting continuity after go‑live.

Direct map. Salesforce Contacts move to Freshsales Contacts with all standard fields. Owner resolution matches Contact owner email against Freshsales user email — unmatched owners flagged for fallback assignment before migration commits. Custom contact roles, such as primary technician or site manager, are stored in a custom picklist field to replicate Salesforce contact‑type behavior.

Direct map. Salesforce Leads (for prospects not yet assigned to field technicians) migrate to Freshsales Leads. Lead status pick-list values are mapped value-by-value to Freshsales lead_status field options. Any custom lead sources or industry‑specific classifications are transferred as custom picklist fields to preserve segmentation logic after migration.

Salesforce Opportunities map to Freshsales Deals. Pipeline stage names are mapped value-by-value to Freshsales deal stage options. Close date, amount, probability, and owner transfer directly. Record type context from Salesforce requires pre-mapping if multiple sales processes exist. Opportunity products and line items are represented as custom deal fields or related custom objects, ensuring that complex pricing structures are not lost during the transition.

Salesforce Work Order has no native Freshsales equivalent. We create a custom Work_Order__c object in Freshsales with custom fields for Subject, Description, Status, Priority, Service Type, Billing Type, Scheduled Start, Scheduled End, and Work Order Number. The Salesforce Work Order ID is preserved as Source_System_ID__c for delta-run de-duplication.

Work Order Line Items map to a custom Work_Order_Line_Item__c object with a lookup relationship to Work_Order__c. Each line item carries its own description, quantity, unit price, and line item type from the source. Line item sequence and sort order are preserved as custom number fields.

Service Appointments carry scheduling data (earliest start, due date, travel time, actual duration) that does not fit cleanly into Freshsales Tasks. We map Subject, Status, Scheduled Start/End, and actual start/end timestamps to Freshsales Tasks. Scheduling optimization data (Gantt position, travel estimates) is written to custom fields since no native equivalent exists.

Salesforce Skill objects define technician certifications and competency levels. We create a custom Skill__c object in Freshsales and link it to Contact records via a many-to-many junction object (Contact_Skill__c) to preserve the proficiency rating and certification expiry date from the source.

Skill Requirements on Work Orders specify required skills for a job. These map to a custom Skill_Requirement__c object with a lookup to both Work_Order__c and Skill__c. Skill level required and whether it is mandatory or preferred transfers as custom pick-list and checkbox fields.

Salesforce Service Territory defines geographic dispatch zones with operating hours. We create a custom Service_Territory__c object and store the operating hours as a custom JSON or multi-line text field since Freshsales does not have a native scheduling calendar object. Territory members (technicians assigned to the territory) link via a junction object.

Salesforce Assets track customer equipment under service contracts. We map them to a custom Asset__c object with fields for Name, Product, Serial Number, Status, Install Date, and Account lookup. Asset Relationships (replacements and upgrades) migrate as separate custom records with a parent-child lookup.

Entitlements define service contract terms and SLA levels. We create a custom Entitlement__c object linked to both Account and Asset, storing Service Contract name, start/end dates, and SLA terms as custom fields. Contract Line Items from Salesforce map to a related custom object for line-level billing terms.

Standard Salesforce Tasks and Events (not Service Appointments) map directly to Freshsales Tasks and Events with subject, status, due date, and owner preserved. Recurring task patterns are not carried — those must be rebuilt in Freshsales. If your organization uses custom task types or priority flags, we store these as custom fields on the Freshsales Task object to retain classification after migration.

Salesforce Files and Attachments on Work Orders, Accounts, and Contacts are downloaded and re-uploaded to Freshsales as file attachments linked to the corresponding migrated records. File size limits of Freshsales per plan apply. During the upload process, we preserve original file metadata such as created date and author, and we flag any files that exceed the target plan's size cap for manual handling.

Salesforce Flow Builder automations and Assignment Rules govern technician dispatch and routing logic. These have no Freshsales equivalent and must be rebuilt manually using Freshsales workflow rules or an external scheduling tool. We export Flow definitions as JSON for the rebuild reference.