Migrate your ServiceMax data

The central object is SVMXC__Service_Order__c. We map standard fields (status, priority, scheduled date, location, assigned technician) and custom SFM Transaction-driven fields. ServiceMax Work Orders support record types per business process (Field Service, Depot Repair, Install). We preserve all child records: Line Items, Attachments, Task dependencies, and historical status changes logged in the Work Order Detail.

Stored as SVMXC__Installed_Product__c. We map the full asset hierarchy including parent-child relationships, current location, customer association, and installed-date history. Technical Attributes attached to assets are migrated as serialized configuration data, and we ensure the destination platform's asset model can represent the same attribute set.

Resources are mapped via SVMXC__Skill__c, SVMXC__Service_Group_Members__c (technician records), and associated Skill Requirements. We preserve skill certifications, work territories, and working hours. Dispatch Console View configurations—custom filter sets and sorting rules—are extracted via the Migration Tool and mapped to equivalent dispatch views in the destination.

PM Processes define scheduled maintenance rules and intervals. They reference Work Order Templates and Counter Rules. We migrate the PM process definitions and their linked templates, but counter-threshold logic and trigger conditions require field-level mapping to the destination's scheduling engine because each FSM platform implements interval-based triggers differently.

Entitlements (SVMXC__Entitlement__c) tie Customers, Assets, and Contracts to Work Orders and determine covered services, response times, and parts coverage. ServiceMax Core and Asset 360 handle entitlement lookups differently. We map the entitlement rules and contract associations, but destination-specific SLA logic may require reconfiguration.

ServiceMax tracks locations (SVMXC__Site__c), sub-locations, and bin-level stock at each location. Parts, tools, and equipment are modeled as Inventory records linked to locations. We migrate the location hierarchy and inventory records, but bin-level precision and multi-location stock-transfer logic often needs adjustment at the destination.

SFM Transactions are custom form layouts built with ServiceMax's Flow designer and drive mobile data capture. They reference object fields, validation rules, and custom actions. We extract these as configuration artifacts via the Migration Tool's JSON bundle export, but rebuilding equivalent form builders in a non-Salesforce destination requires significant reimplementation.

SFM Wizards chain multiple SFM Transactions into guided multi-step workflows used on mobile devices. They include conditional branching, auto-population rules, and completion criteria. We export wizard definitions as configuration, but the wizard-engine logic is ServiceMax-specific and must be recreated in the destination FSM platform.

Technical Attributes model complex product specifications (serialized components, firmware versions, certification dates) and attach to Asset records. Template definitions with picklist values, data types, and display formats are migrated as metadata. The actual attribute values per asset are migrated as structured field data. Destination platforms without a native technical-attribute concept receive these as custom fields on the asset object.

Counter Rules trigger Work Order generation based on asset usage metrics (meter readings, cycle counts, calendar intervals). We export rule definitions and their linked PM templates. Each destination FSM interprets counters differently—some use threshold-based triggers, others use predictive models—so mapping requires aligning rule logic to the destination's scheduling conditions.

Configuration Profiles govern which features, objects, and fields a user role can access within ServiceMax. SFM Mobile Permissions control which transactions and wizards appear on the mobile app per profile. We export these as part of the Migration Tool bundle. In non-Salesforce destinations, these map to role-based access control systems with different permission granularity.

Timesheet configurations and submitted time entries (SVMXC__Timesheet__c and related line items) are migrated as structured records. We preserve technician ID associations, date ranges, hours logged, and billable/non-billable flags.

Spare Parts configurations define which parts are associated with which Asset models, work order types, and inventory locations. We migrate the part-to-asset mapping rules and stocking location assignments, but destination-specific parts-pricing and substitution rules require manual reconciliation.

Work Orders, Assets, and Work Order Line Items can carry file attachments stored in Salesforce Content or Files. We export attachment metadata and binary blobs. Large-volume attachment migration is chunked to avoid Salesforce API limits. Destination platforms may not have the same content-library structure, so we map attachments to equivalent document-management locations.