Migrate from Service Suite FSM to Freshsales

Service Suite FSM contact records migrate to Freshsales Leads if they represent prospects awaiting conversion, or to Freshsales Contacts if they have already engaged in service. The split decision uses FSM contact status and last-activity date as routing criteria. During migration, FlitStack AI also checks for duplicate email addresses and maps the original FSM contact ID to a custom field for future reconciliation.

FSM customer records map directly to Freshsales Accounts. The customer name becomes Account Name, billing address maps to the account address fields, and the customer type field maps to Freshsales Account Type via value mapping. If a customer has multiple FSM sites, each site can be represented as a separate Freshsales Account or linked via the Account hierarchy, depending on your team's structure.

FSM work orders do not have a direct Freshsales equivalent. Open FSM work orders migrate as Freshsales Deals with the work order title as Deal Name, estimated service value as Deal Amount, and work order status mapped to a Freshsales Deal stage via value mapping. Service notes attach as Sales Activities.

FSM asset records — including serial number, product type, warranty end date, and service history — map to Freshsales Products with the asset serial number stored in the product description or a custom field. Freshsales has no native asset-management module, so ongoing maintenance tracking must be handled via Freshsales custom objects or a companion tool.

FSM technician and resource records resolve to Freshsales users by email address match. Unmatched technicians are flagged as inactive users and assigned a placeholder owner pending your admin's decision to invite them to Freshsales. FlitStack AI also maps the technician's FSM role and skill tags to Freshsales user custom fields, ensuring that scheduling permissions and capabilities are preserved in the new system.

FSM service reports and customer signatures migrate as Freshsales Notes attached to the corresponding Deal or Contact record. Files re-upload to Freshsales Files storage under the attached record. Large signature images compress to reduce Freshsales file-size overhead. If the original report includes linked work order references, FlitStack AI adds those as custom note fields for traceability.

FSM scheduled appointments map to Freshsales Sales Activities with Type='Meeting'. Original start/end timestamps, assigned technician (mapped to Freshsales User), and linked customer (mapped to Account) are preserved on the activity record. If an appointment includes a service type or priority flag, FlitStack AI maps those to custom Sales Activity fields, allowing your team to filter and prioritize meetings in the Freshsales calendar view.

Service Suite FSM extended properties on any entity migrate as Freshsales custom fields on the corresponding object. If FSM custom objects represent complex nested data, Freshsales Enterprise custom modules handle the relationship mapping — your admin defines the schema before migration data lands.

FSM technician skill tags and work-order category tags migrate as Freshsales Tags on the corresponding record (Contact, Account, or Deal). Tags are non-hierarchical in Freshsales, so FSM skill hierarchies collapse to a flat tag list. During migration, FlitStack AI preserves the original FSM tag names and adds a prefix (e.g., 'FSM_Skill_') to avoid naming collisions with existing Freshsales tags.