Migrate from eSalesTrack to Microsoft Dynamics 365 Sales

eSalesTrack Lead records map directly to Dynamics 365 Lead. Lead status from eSalesTrack maps to Dynamics 365 Lead Status. Any lead score or source tracking fields in eSalesTrack migrate to custom fields on the Dynamics 365 Lead entity. We resolve the eSalesTrack owner reference to a Dynamics 365 User by email match and set OwnerId at import time.

eSalesTrack Contact records map to Dynamics 365 Contact. The contact's associated Account (Company) resolves to a Dynamics 365 AccountId via the Account mapping phase. Phone, email, address, title, and custom fields on the Contact migrate directly to typed fields on the Dynamics 365 Contact entity. We flag any eSalesTrack Contact that is not linked to an Account for admin review before insert.

eSalesTrack Account records (referred to as Companies in some exports) map to Dynamics 365 Account. Company name maps to Account Name; domain or website maps to Account Website. We use Company Name or Website as the dedupe key during import. Account must be inserted before Contact records so that the AccountId foreign key is satisfied on Contact insert.

eSalesTrack Opportunities map to Dynamics 365 Opportunity. The eSalesTrack deal stage maps to a Microsoft Dynamics 365 Sales Process stage value that we configure in the destination org before migration. Close date, amount, probability, and owner all map directly. We resolve AccountId and OwnerId during the Opportunity phase after Account and User resolution are complete.

Each named stage from the eSalesTrack pipeline becomes a StageName value within a Microsoft Dynamics 365 Sales Process that we pre-configure in the destination org. We set probability percentages per stage to match eSalesTrack values where available. If eSalesTrack has a single pipeline, we use the default Microsoft Dynamics 365 Sales Process. Multiple pipelines require multiple Sales Processes or Record Types in Dynamics 365.

eSalesTrack Products map to Dynamics 365 Product2 records. Product name, SKU, and description migrate directly. We create Standard Pricebook entries for each product during the import phase. If eSalesTrack does not expose a product API, we extract product data from the CSV export and transform it for Dataverse bulk import.

eSalesTrack Line Items attached to Deals map to Dynamics 365 OpportunityLineItem. We resolve the Opportunity (WhatId), Product (PricebookEntry.Product2Id), and Pricebook2 reference at migration time. Quantity, unit price, and total migrate directly. This phase runs after Product2 and PricebookEntry creation are confirmed complete.

eSalesTrack Owner references on Contacts, Accounts, and Opportunities map to Dynamics 365 User by email address. We extract the distinct owner list from the source export and match against the destination org's User table. Any eSalesTrack owner without a matching Dynamics 365 User goes to a reconciliation queue; the customer's admin provisions the missing User before migration resumes.

eSalesTrack custom fields on Contacts, Accounts, and Opportunities require pre-creation in Dynamics 365 before data import. We use the Dynamics 365 user-defined fields feature (directly in the UI) or the Dataverse API to provision custom fields with matching data types. Text fields, number fields, date fields, and picklist fields each have type-specific mapping rules that we document in the pre-migration schema design phase.