Migrate from Ascora to Microsoft Dynamics 365 Sales

Direct map. Ascora Customer full name becomes Account Name, primary email becomes Email, primary phone becomes Telephone 1. Multi-site customers spawn one Account with multiple Address records keyed by site location name. The site location name is stored in the Address Name field to provide a human-readable label for each site within the Dynamics 365 Sales Account.

Site is a sub-record of Customer. Maps to Account Address fields (street, city, state, postal code, country) plus a Site_Location__c custom field for the location name. Latitude/longitude store as custom decimal fields. Multi-site customers produce one Account with N Address records or one Account and N Site__c custom table records.

Ascora Jobs have no direct CRM equivalent. A custom Dataverse table (Job__c) is created with fields for Job_Number__c, Job_Title__c, Job_Status__c (custom picklist with original Ascora values), Job_Description__c, Job_Priority__c, Job_Type__c, Estimated_Duration__c, Actual_Start__c, Actual_End__c, Site__c (lookup to Account or Site__c), Technician__c (lookup to User or custom field).

Ascora Quotes merge into two constructs: a custom Quote__c table holding quote number, status, expiry, and total, plus an Opportunity record when the quote represents a billable project. Quote Status (Draft, Sent, Approved, Expired) maps to a custom picklist. Approval timestamps and approver name store as custom datetime and text fields on the Quote__c table.

Quote line items map directly to Opportunity Products (Product Name, Quantity, Unit Price, Manual Discount) when tied to an Opportunity, or to a custom QuoteLineItem__c table when Quote maps to the custom Quote__c table. Each line preserves the original Ascora description and discount amount as custom fields.

Invoices have no native Dynamics 365 Sales equivalent. A custom Invoice__c table is created with Invoice_Number__c, Account__c (lookup), Invoice_Status__c, Amount__c, Due_Date__c, Customer_PO__c, Payment_Terms__c, and Original_Invoice_Number__c. Invoice status values (Paid, Overdue, Void) map to a custom picklist. These fields enable full invoice lifecycle tracking within Dynamics 365 Sales.

Job-related activities — technician notes, site visit logs, status-change events — migrate as Dynamics 365 Sales Tasks with Subject, Description, Actual_Duration__c (custom), Technician__c (User lookup or custom field), and Scheduled_Date__c. Original Ascora activity timestamps and owners are preserved. Each task retains its original creation date for audit compliance.

Ascora Custom Form questions map field-by-field to custom fields on Job__c or a dedicated FormResponse__c custom table linked to Job__c. Form name and question label are preserved as metadata. Multi-question forms generate multiple custom fields with type-aware mapping (text, number, date, picklist).

Ascora user and technician records are resolved by email address match against Dynamics 365 Sales Users. Unmatched technicians are flagged before migration; your team either invites them to Dynamics first or assigns their records to a fallback owner. Job__c records land with the resolved User as Owner.

Ascora file attachments are downloaded and re-uploaded to SharePoint (the native Dynamics 365 Sales document store) or stored as Dataverse Annotations with the ParentObjectId pointing to the parent Job__c or Account record. Original filename preserved as name and the Ascora file URL stored as Ascora_File_URL__c custom field for traceability.