Migrate from Market Maker to Microsoft Dynamics 365 Sales

Market Maker contacts map 1:1 to Dynamics 365 Contact records. The email address is the primary lookup key. Phone, job title, address, and created/modified timestamps carry over as Dataverse column values. Primary company resolves to AccountId before contact creation. Additional fields such as social media handles or custom classification tags are migrated as custom columns, preserving any data formatting present in the source.

Market Maker contacts without a primary company association, or those marked as prospects, route to Dynamics 365 Lead. The Last Name field populates the required Lead.name field; email and phone carry over as contact methods. Your team qualifies leads into Contact records during the sales process.

Market Maker company records map to Dynamics 365 Account. Account name, website, industry, employee count, and annual revenue transfer to corresponding Dataverse columns. Parent-company relationships map to Account.parentaccountid for hierarchical accounts. Multi-company contacts create Account Contact Relationships after the primary Account is set.

Market Maker deals map to Dynamics 365 Opportunity. Deal name becomes Opportunity.name, amount transfers to Opportunity.estimatedvalue, close date maps to Opportunity.closedate, and pipeline stage maps to the active Business Process Flow stage. Owner resolves by email match to Dynamics 365 SystemUser.

Each Market Maker pipeline becomes a Dynamics 365 Business Process Flow attached to the Opportunity table. Stages in Market Maker map to stage names in the BPF. If your Dynamics 365 license is Sales Professional, business process flows are supported but with the 15-table limit counting against custom tables you create.

Stage names in Market Maker map to BPF stage names in Dynamics 365. Each stage's probability and forecast category are applied from Dynamics 365 side configuration. Stage-entered timestamps from Market Maker are stored as custom datetime columns for reporting continuity.

Market Maker activity types map to specific Dataverse activity tables. Calls become PhoneCall, emails become Email, meetings become Appointment, and notes become Annotation. Original timestamps, subject, body, and owner carry over. Activity-party records link activities to Contact or Account. If a source activity references a deleted or missing contact, the activity is flagged as unresolved and stored in a temporary holding table for manual review before final linkage.

Market Maker file attachments re-upload to Dynamics 365 as Annotation records with the file stored in Dataverse or connected SharePoint. File size limits (Dynamics 365 default 128MB per file attachment) apply; larger files are flagged for alternative storage before migration.

Market Maker custom objects become Dataverse custom tables in Dynamics 365. Custom object relationships that use N:N associations map to Dataverse many-to-many relationships. If you are on Sales Professional and already have 15 custom tables, custom objects may need to be stored as custom columns on standard tables.

Market Maker owner IDs resolve to Dynamics 365 SystemUser records by email address match. Unmatched owners are flagged before migration; you either invite them to Dynamics 365 first or reassign their records to a fallback owner. Owner history is preserved as custom columns for audit continuity.