Migrate from ServiceMax to Freshsales

ServiceMax stores customer organizations as Salesforce Accounts. FlitStack maps these directly to Freshsales Accounts, preserving Account Name, Industry, Website, and Address fields. Parent Account hierarchies in ServiceMax map to Freshsales Account hierarchy where supported — parent must migrate before child to resolve the reference correctly.

ServiceMax stores technician and customer contact records as Salesforce Contacts. These map directly to Freshsales Contacts with first name, last name, email, phone, title, and address fields preserved. ServiceMax contact roles (technician, dispatcher, customer) are flagged in a custom Contact field since Freshsales has no native role-per-contact model.

Work orders map to Freshsales Tasks for individual activity records (what was done, when, by whom). The full work order header (WO number, priority, status, scheduled date, actual duration, skill required, service type) migrates to a custom object called Service_History__c linked to the Contact. This preserves the FSM context that a standard Task cannot hold.

ServiceMax IB tracks serialized equipment, location, warranty status, and technical attributes per installed unit. Freshsales has no native asset object. FlitStack creates an Asset__c custom object and maps IB fields including Serial Number, Product Name, Location, Installation Date, and Warranty End Date. Technical attributes stored as IB custom fields map to custom fields on Asset__c.

ServiceMax stores entitlement rules and service contract terms on the IB or Account object. Freshsales has no native contract object. FlitStack maps contract start/end dates, contract type, and coverage level to a custom object linked to the Account and Asset. SLA terms are preserved as text fields for reference.

ServiceMax tracks work order stage transitions (Dispatched, In Progress, On Hold, Completed) with timestamps and assigned technician. Freshsales Tasks have a single status field. FlitStack preserves the full status transition log as a custom multi-line text field (JSON-formatted) on the Service_History__c custom object so nothing is lost.

ServiceMax technicians are Salesforce users with ServiceMax permission sets. FlitStack resolves ServiceMax user emails against Freshsales users by email match. Skills, certifications, and service territories stored on the ServiceMax user record map to custom fields on the Freshsales User object (or contact) — your admin configures which technician attributes to surface in Freshsales.

ServiceMax PM processes define frequency-based or meter-triggered maintenance schedules on IB records. Freshsales has no scheduling or preventive maintenance module. FlitStack exports PM process definitions (frequency, trigger type, IB targets) as a JSON reference file your Freshsales admin uses to rebuild maintenance reminders as Freshsales workflows or tasks.

ServiceMax SFM (Service Flow Management) Transactions and Wizards define the mobile UI screens technicians see in the field. These are Salesforce Visualforce/LWC configurations with no Freshsales equivalent. FlitStack exports SFM Transaction definitions as a rebuild reference — Freshsales mobile workflows or custom app development would replace this layer.

ServiceMax inventory products and parts tracked in stock locations map to Freshsales Products. Product Name, SKU, Unit Price, and Product Description transfer directly. ServiceMax stock quantity fields are not native Freshsales fields — these are flagged as custom fields on the Product object or noted for a separate inventory management tool.

ServiceMax files attached to work orders, assets, or IB records (photos, PDFs, signatures) are downloaded and re-uploaded to Freshsales Attachments on the corresponding Service_History__c or Asset__c record. File size limits apply (Freshsales caps at 25MB per file for most plans). Inline images in work order notes are extracted and rehosted as standalone attachments.

ServiceMax counters track usage meters on assets (page counts, cycle counts) that drive PM triggers and service alerts. Freshsales has no counter or usage-metering concept. FlitStack exports the counter rule definitions as a structured reference document. If meter-based PM logic is critical, it needs a custom application or third-party scheduling tool post-migration.