Migrate from Market Leader to Microsoft Dynamics 365 Sales

Market Leader contacts map directly to Dynamics 365 Contact records. The Contact table in Dataverse holds name, email, phone, address, and job title. FlitStack maps firstname, lastname, email, phone, mobilephone, and jobtitle to their Dataverse equivalents. Contacts without a primary company in Market Leader land with no AccountId set; FlitStack flags these for admin review before committing the full migration.

Market Leader contacts that have not transacted may not yet be qualified clients. FlitStack applies a status-based split: contacts with a Market Leader status of 'Lead' route to a Dynamics 365 Lead record, while active clients with a status of 'Customer' route to Contact. The split rule is configurable — your team defines which Market Leader status values map to Lead versus Contact before the migration runs.

Market Leader company records map 1:1 to Dynamics 365 Account. Account is the parent entity for Contact in Dataverse — most Market Leader contacts carry a company name or association that becomes AccountId on the Contact record. Parent-company hierarchies in Market Leader map to the ParentAccountId field in Dynamics 365.

Market Leader leads that have not yet become contacts map directly to Dynamics 365 Lead. Lead has a separate lifecycle from Contact in Dataverse — leads qualify and convert to Contact + Account via the built-in Lead Qualification process. Original Market Leader lead scores migrate to a custom field on Lead for rep prioritization after conversion.

Market Leader stores transaction details — listing ID, property address, commission percentage, closing date — as custom properties on the contact or company. FlitStack creates corresponding custom fields in Dataverse on the Opportunity table (new_ListingID__c, new_CommissionSplit__c, new_ClosingDate__c) so transaction history attaches to the deal record rather than the contact. Dynamics 365 Sales Enterprise supports unlimited custom fields; Sales Professional limits custom tables to 15, which may require an upgrade if your transaction property count is high.

Market Leader drip campaign membership has no native equivalent in Dynamics 365 — Dynamics 365 Sales has no built-in drip sequencing tool. FlitStack preserves drip campaign enrollment as a custom text field on Contact (new_DripCampaignEnrollment__c) listing the campaign names each contact was enrolled in. Campaign sequence logic and timing must be rebuilt in Power Automate post-migration using exported campaign definitions.

Market Leader stores call logs, email history, and meeting records as activities on contacts. FlitStack maps these to Dynamics 365 Task (Phone Call, Email), and Appointment (Meeting) activity records. Each activity preserves its original timestamp, owner (mapped by email to a Dynamics 365 user), and the regarding contact or account lookup.

Market Leader agents are internal users who own leads and contacts. Dynamics 365 assigns records to SystemUser via OwnerId. FlitStack resolves each Market Leader agent email against your Dynamics 365 user list — matched users receive record ownership; unmatched agents are flagged as a pre-migration task so their records can be assigned to a fallback owner before the full load.

Market Leader files attached to contacts or companies — property images, contracts, forms — are downloaded and re-uploaded to SharePoint Online (the native document storage for Dynamics 365 Sales when integrated with Microsoft 365). FlitStack re-links the file URL as a Note or SharePoint document attachment on the corresponding Dynamics 365 record after load.

Market Leader billing records — agent seat counts, contract renewal dates, and cancellation windows — are stored outside the CRM data export and do not appear in the contact or company export. These must be managed in Microsoft 365 admin center post-migration. FlitStack flags the absence of billing-model data in the migration scope during discovery so your team can set up licensing independently.