Migrate from Service Autopilot to Microsoft Dynamics 365 Sales

Service Autopilot clients are person-level records with name, email, phone, address, and client-specific notes. They map 1:1 to Dynamics 365 Sales Contact records. Multiple phone numbers (home, mobile, work) on a client collapse to Phone and MobilePhone; extra numbers migrate as custom fields on Contact.

Service Autopilot records that have Lead status in the source (unconverted prospects) route to Dynamics 365 Sales Lead. Active clients (those with at least one completed or scheduled job) route to Contact. The split is determined by job-history presence before migration.

Service Autopilot allows a client to be attached to a company name. That company name maps to Account.Name in Dynamics 365 Sales. When a client has no company, a default 'Individual Client' account is created so Contact.AccountId is never null.

Service Autopilot's Property entity stores the service-site address, GPS coordinates, property measurements, access notes, and photos. Dynamics 365 Sales has no native property entity. We create a Service_Property__c custom table with a lookup to Account. Photos migrate as file attachments on the property record.

Jobs in Service Autopilot represent a scheduled service at a property, linked to a client and assigned employee. They map to a custom Job__c table linked to Service_Property__c and Contact. If the business uses deals to track revenue tied to jobs, Opportunity is used for that purpose with a custom lookup back to Job__c.

Service Autopilot invoices carry the job reference, line items, totals, payment status, and payment method. In Dynamics 365 Sales, invoices are created from Order records. We create Invoice_Number__c, Payment_Status__c, and Original_Job_ID__c custom fields on the Order entity so the full billing context is preserved.

Service Autopilot employees (field crews and office staff) map to Dynamics 365 Sales SystemUser records. Resolution happens by email match — the employee's email in Service Autopilot is matched to a User's email in Dynamics. Unmatched employees are flagged for the admin to provision or assign to a fallback user.

Service Autopilot services (mowing, landscaping, cleaning) and products map directly to Dynamics 365 Sales Product2 records. Each service or product carries a unit price, cost, and service-duration field that translates cleanly to Dynamics Price List items. Bundle services, where multiple service types are packaged together, collapse to a Product Bundle entity in Dynamics to maintain pricing accuracy and simplify order management.

Service Autopilot's scheduled start/end times, assigned route, and employee assignment on a job are captured as custom fields on the Job__c table (Scheduled_Start__c, Route__c, Assigned_Employee__c). Dynamics 365 Sales has no native scheduling entity — these values are searchable but not visualized on a calendar without Field Service or a third-party scheduling app.

Service Autopilot Automations (trigger → condition → email/SMS/task sequences) have no equivalent in Dynamics 365 Sales. We export the automation definitions as a reference document listing each sequence's trigger, conditions, and actions. Your Dynamics admin rebuilds them in Power Automate or Dynamics workflows.

Client notes in Service Autopilot migrate as Dynamics 365 Sales Annotations attached to the Contact record. The original create timestamp, last-modified date, and note author are all preserved in the annotation metadata. Rich-text formatting in notes is converted to plain text for full compatibility with Dataverse annotation storage, ensuring that no note content is lost or displays incorrectly in the target system.

Payment transactions in Service Autopilot (amount, method, date, status) are stored as custom fields on the associated Order record (Last_Payment_Date__c, Payment_Method__c, Amount_Paid__c). Dynamics 365 Sales does not have a native payment sub-entity — payment history is preserved as audit fields rather than transactional records.