Migrate from ServiceMax to Microsoft Dynamics 365 Sales

ServiceMax Accounts map directly to Dynamics 365 Accounts. Address fields, phone, industry classification, and annual revenue transfer as standard D365 Account fields. Parent-account hierarchies in ServiceMax map to the D365 Parent Account lookup — the parent must be migrated first and circular references are flagged.

ServiceMax Contacts map 1:1 to D365 Contacts. Name, email, phone, mobile phone, title, and address fields transfer directly. Contacts without a primary Account in ServiceMax are attached to a placeholder 'Unassigned Account' in D365 so every Contact has an AccountId lookup.

ServiceMax Product records (part numbers, descriptions, pricing, and unit of measure) migrate to D365 Product table entries. Product structures — bundles and individual items — map to D365 Product Type fields. Field Service Product types (billable vs. non-billable) are preserved as a custom field on the Product record.

ServiceMax Installed Base records carry the equipment hierarchy, technical attributes, serial numbers, and installation dates. These map to the D365 Field Service Asset table if the Field Service add-on is licensed, or to a custom Dataverse InstalledBase table when only Sales is deployed. Parent-child IB relationships become Asset Parent serial numbers in D365.

ServiceMax Work Orders have no direct D365 Sales equivalent. We map them to a custom Dataverse WorkOrder table with fields for WO number, status, priority, scheduled date, actual start/end times, labor hours, and the linked Account and Asset lookups. Work order line items (tasks, parts used) become WorkOrderDetail child records in the custom table.

ServiceMax logs all work order status transitions, technician check-ins, and field notes as history entries. These migrate as datetime-stamped entries in the custom WorkOrder table's history section, linked by the source Work Order ID so D365 users can audit the full service record from the Account.

ServiceMax Entitlements define SLA terms, covered assets, and service level timers against the Installed Base. Since D365 Sales has no native entitlement object, we create a custom Dataverse Entitlement table with fields for entitlement name, SLA tier, start/end dates, covered asset reference, and service type. The Account record links to its active entitlements.

ServiceMax Preventive Maintenance (PM) processes and Service Contracts define recurring service schedules tied to assets. These migrate as custom Dataverse Contract records with frequency, interval, next due date, and linked Asset references. Recurrence rules are preserved as text fields for the D365 admin to rebuild in Power Automate.

ServiceMax Technician records carry skills, certifications, work zone, and working hours. If Dynamics 365 Field Service is licensed, Technicians map to Bookable Resources. If only Sales is licensed, we create a custom Dataverse Technician table and preserve skills as a multi-select pick-list so the implementation team can build routing automations in Power Automate.

ServiceMax parts and inventory locations (stockrooms, trucks) describe on-hand quantities and bin locations. These migrate to a custom Dataverse InventoryLocation table linked to Products, with quantity and bin address preserved as reference data — not as transactional inventory management, since D365 Sales has no native inventory ledger.

ServiceMax file attachments on work orders and assets (photos, PDFs, signatures) are downloaded and re-uploaded to the linked D365 Account or custom WorkOrder record's SharePoint document library. The original file name and upload date are preserved in the document metadata.

ServiceMax dispatch console configurations, skill-routing rules, and scheduling constraints are configuration items, not data. These cannot be migrated. We export them as JSON configuration files from the ServiceMax Migration Tool so your implementation team can reference the routing logic when building Power Automate or Field Service scheduling automations in D365.