Migrate from ServiceMonster to Microsoft Dynamics 365 Sales

ServiceMonster customer records map 1:1 to Dynamics 365 Sales Accounts. The customer name, primary address, phone, and email transfer directly. ServiceMonster allows multiple contacts per customer — secondary contacts become Contacts associated to the Account via Account Customer ID relationship.

Named contacts on ServiceMonster customer records map to Dynamics 365 Contacts. The primary contact email, phone, and job title transfer directly. Contact-to-Account linkage is established via the AccountId lookup after the Account record is created in Dynamics. Secondary contacts are also migrated as separate Contact rows linked to the same Account, preserving name, role, and preferences. Contacts marked inactive in ServiceMonster are imported with an inactive flag for admin review.

ServiceMonster jobs are the primary work record and carry revenue, status, assigned technician, and service type. They map to Dynamics 365 Opportunities with the job name as Opportunity Name, total job amount as Estimated Revenue, and job status mapped to a custom opportunity status field. Service type becomes a custom pick-list field on the Opportunity.

ServiceMonster appointments (scheduled time blocks on jobs) map to Dynamics Activity records — Tasks for general appointments and Phone Calls for technician check-ins. The original appointment start/end time, assigned technician, and GPS check-in flag transfer as custom fields on the Activity record.

ServiceMonster invoices map to Dynamics 365 Sales Invoices directly when the invoice is linked to a closed Opportunity. Line items map to Invoice Details. Unpaid or partially paid invoices carry their payment status as a custom field. Voided invoices are migrated as historical records with void flag set.

ServiceMonster price-list entries (service names and base prices) map to Dynamics Products. The service description, unit of measure, and base price transfer as Product Name, Description, and Base Amount. Pricing tiers per customer type require custom price-list fields on the Product or a separate price-list table in Dynamics.

Individual line items within a ServiceMonster price list (e.g., carpet cleaning per room, per square foot) map to Dynamics Product Price List entries. Unit type (per hour, per square foot, flat rate) is preserved as a custom field on the price list item.

ServiceMonster Routes group appointments by technician and geographic sequence. Routes have no native Dynamics equivalent. We create a Dataverse custom table (Route__c) storing route name, assigned technician (linked to User), route date, and ordered list of linked Job IDs. Route sequence order is preserved as an integer field on each Job-Activity link.

ServiceMonster records GPS coordinates when a technician checks in or out of an appointment. These coordinates transfer as custom decimal fields (CheckIn_Latitude__c, CheckIn_Longitude__c, CheckOut_Latitude__c, CheckOut_Longitude__c) on the corresponding Task or Phone Call record. Check-in and check-out timestamps also transfer as custom datetime fields.

ServiceMonster technicians map to Dynamics 365 Users by email match. Active technicians receive User records in Dynamics with the same name and email. Inactive or archived technicians are flagged for your admin to decide whether to create User records or leave them as historical owner references only.

ServiceMonster custom fields on any object migrate to Dataverse custom fields on the equivalent Dynamics entity. Custom fields on Job records that have no matching Dynamics Opportunity field become custom fields on the Opportunity. Complex custom objects (N:N relationships between Jobs and Customers) require Dataverse custom tables with N:N relationship tables.