Migrate from Field Services Workflow and Logistics to Salesforce Sales Cloud

Field Services Workflow and Logistics customer records map 1:1 to Salesforce Accounts. Multi-location customers with site-level records in the FSM become Salesforce Accounts with child Location records or Address records. Parent-account hierarchies in the FSM map to Salesforce ParentId on Account.

Contact records map directly to Salesforce Contacts. Each Contact requires an AccountId — the FSM's customer-to-site relationship resolves to the primary Account. Secondary site contacts attach via Account Contact Relationships or a custom junction object if the FSM supports N:1 contact-to-customer.

Work orders map to Salesforce Cases by default. If the team uses Salesforce Field Service, we map to the ServiceAppointment object instead. The FSM work-order status (Open, In Progress, Completed) translates to Salesforce Case Status pick-list values. Priority and severity fields map to Case Priority and custom SLA fields.

FSM appointments with a scheduled start/end time map to Salesforce Events. Time-blocked work sessions or task-level visits map to Tasks with Type='Field Service'. Original scheduled time, actual arrival, and completion timestamps are preserved as custom datetime fields since Salesforce's standard CreatedDate reflects migration time.

FSM technician records are matched to Salesforce Users by email address. If Salesforce Field Service is enabled, technician records also create ServiceResource entries tied to the User. Unmatched technicians are flagged before migration — the team either invites them to Salesforce first or assigns their open work orders to a fallback owner.

Asset records migrate directly to Salesforce Assets. The FSM's asset-to-customer link becomes Asset.AccountId. Asset hierarchies (parent-child equipment relationships) map to Asset.ParentId, sequenced so parent records migrate before children. Asset Warranty and Asset Downtime Period records migrate as related custom fields.

FSM location records map to Salesforce Locations when the Field Service managed package is present. Without Field Service, locations migrate as custom Location__c records or as Address records on the Account. Location-to-asset links preserve the physical relationship for dispatch routing in Salesforce Field Service.

FSM parts used on work orders do not have a native Salesforce equivalent. We migrate parts as a custom WorkOrderLineItem__c object linked to the Case, or as Opportunity Products if the service operation bills against Opportunities. Part numbers, quantities, and unit costs migrate as custom fields on the line-item object.

Any custom objects in the FSM (e.g., Inspections, Surveys, SafetyChecks) map 1:1 to Salesforce custom objects. Custom object relationships that use FSM's N:N association model need Salesforce junction objects when the relationship is many-to-many — we surface this in the migration plan and create the junction object schema.

File attachments on work orders, assets, or locations re-upload to Salesforce Files and link to the parent record via ContentDocumentLink. File size limits apply (25MB default per file in Salesforce). Inline images in FSM notes are extracted and re-hosted as Salesforce Files with the original upload timestamp preserved.

FSM work-order notes map to Salesforce Case Comments. Status-change history, technician notes, and customer sign-off records migrate as CaseComments or as a custom Case_History__c custom field with rich-text formatting preserved. Original timestamps and author information map to CreatedDate and CreatedById.

FSM SLA definitions have no direct Salesforce equivalent — they do not migrate as configuration. We preserve SLA terms (response time, resolution time, priority tiers) as a custom Entitlement__c object linked to the Account, which can be connected to Cases for SLA tracking if Salesforce Entitlement Management is enabled.