Migrate from Exsalerate to Microsoft Dynamics 365 Sales

Exsalerate Accounts map directly to Dynamics 365 Account. The account name, address fields, contact details, owner assignment, and custom properties migrate with field-to-field mapping. Exsalerate does not have a separate Company object—Account is the primary entity. We use Account Name as the dedupe key during import and resolve any duplicate accounts before insert using name and domain matching.

Exsalerate Contacts map to Dynamics 365 Contact with the Account-Contact relationship preserved via the parent AccountId lookup. We run duplicate detection across the Contact set using email address as the primary key and flag any Exsalerate contacts with matching emails for the customer to resolve before import. Job title, phone, email, and custom contact fields migrate with type awareness (picklist normalisation, date format standardisation).

Exsalerate Opportunities map to Dynamics 365 Opportunity with AccountId and OwnerId resolved at migration time. The Exsalerate pipeline stage label maps to a Dynamics 365 Sales Process stage that we configure before migration. Opportunity value, expected close date, and description fields migrate directly. If the customer has imported WorkflowMax quotes as Opportunities, the cross-reference is stored in a custom Opportunity field (wmx_quote_reference__c) that we create during schema setup.

Exsalerate named Pipelines map to Dynamics 365 Record Types on Opportunity. Each Record Type gets a corresponding Sales Process that whitelists the relevant stage values from the source pipeline. Stage order and colour-coding metadata from Exsalerate are noted in the mapping document for the customer's admin to optionally reapply in Dynamics using Power Automate colour tags or a custom field.

Exsalerate pipeline stages (for example, Qualified, Proposal Sent, Negotiation) map to Dynamics 365 Opportunity StageName values within the appropriate Sales Process. Stage probability percentages are mapped to StageProbability. Stage-level automation triggers are not migrated—we document them for the admin to rebuild in Dynamics 365 Flow or Power Automate.

Exsalerate to-do tiles map to Dynamics 365 Task records. Due date, status, and description migrate directly. The colour-coded urgency flag from Exsalerate tiles is stored as a custom field tile_colour__c on Task, since Dynamics 365 does not have a native colour encoding for tasks. We verify the destination Dynamics org allows custom Task fields at the customer's licensing tier before committing this mapping.

Exsalerate email history associated to Accounts and Contacts migrates to Dynamics 365 Task records (the activity timeline entry) with the email content stored in the Task Description field or linked as an EmailMessage record. Subject, timestamp, sender, and recipients migrate. Email threading relationships are not preserved in Dynamics 365 out-of-the-box; we document the thread ID in a custom field for manual reconstruction if needed.

Custom fields on Accounts, Contacts, and Opportunities in Exsalerate are migrated with field-type awareness. Picklist values are mapped to Dynamics 365 picklist or option set values; date formats are normalised to the destination org's locale setting; numeric precision is preserved. Any Exsalerate custom field that has no Dynamics 365 equivalent is stored in a text field and flagged in the handoff document for the customer's admin to refine post-migration.

Exsalerate user accounts map to Dynamics 365 User records by email match. We create a user mapping table during scoping. Inactive Exsalerate users are flagged and their records are assigned to a placeholder owner in Dynamics 365 for review before the final re-assignment. Any Exsalerate user without a matching Dynamics 365 User account goes to a provisioning queue for the customer's admin before record migration resumes.

Where customers have imported WorkflowMax quotes as Exsalerate Opportunities, we preserve the cross-reference in a custom text field wmx_quote_reference__c on the migrated Dynamics 365 Opportunity. The WorkflowMax sync connection itself does not migrate—Dynamics 365 does not have a native WorkflowMax connector. We flag this in the inventory document and note that a Power Automate flow or custom integration would be required to re-establish bi-directional sync with WorkflowMax after cutover.