Migrate from matrix to Microsoft Dynamics 365 Sales

Matrix contacts map directly to Dynamics 365 Contact records. The primary email address becomes the Email field; phone numbers map to Phone and MobilePhone. Owner resolution uses email matching against Dynamics 365 users. Unmatched owners receive a fallback assignment or are flagged for admin review before the migration run commits.

Matrix contacts that have never converted to a customer can be routed to the Lead table in Dynamics 365. The lead_status property from Matrix maps to the Lead Status option set, preserving the original status label as a custom field for reporting continuity. Once a Lead converts to a Contact, Dynamics 365's native conversion process creates the Account and Opportunity links.

Matrix companies map to Dynamics 365 Accounts. The company name becomes Account Name; website URL maps to Website. Industry values from Matrix require value mapping against the Industry picklist in Dynamics 365 — unmapped values land as a custom field. Parent-company relationships from Matrix map to the Parent Account lookup, requiring sequence validation to resolve circular references.

Matrix deals map to Dynamics 365 Opportunities. The deal name becomes Opportunity Name; amount maps to Estimated Revenue. Pipeline stages from Matrix require value-by-value mapping to the StageName option set — each Matrix pipeline stage value must be created as a corresponding opportunity stage before mapping. Close dates map directly to Estimated Close Date.

Matrix activities split into Dynamics 365 activity types: calls become Tasks with Type='Phone Call', emails become Emails, meetings become Appointments, and standalone notes become Notes. Original timestamps, activity descriptions, and owner assignments are preserved. The regarding_objectid links each activity to its parent Contact, Account, or Opportunity record.

Matrix custom fields require pre-creation in Dynamics 365 as custom columns. Text fields become Single-Line Text or Multi-Line Text depending on length. Numeric Matrix properties with decimal values map to Decimal or Currency fields. Picklist values from Matrix must be created as Option Set values in Dynamics 365 before the migration runs — we generate the field-creation manifest as part of the pre-migration schema plan.

Matrix file attachments download and re-upload to Dynamics 365 Notes as file attachments. File size limits apply — Dynamics 365 has a 25MB default per attachment. If Matrix stores attachments larger than this, they are flagged and can be stored in SharePoint with a link preserved in Dynamics 365. Inline images in notes are extracted and rehosted separately.

Matrix owner records resolve against Dynamics 365 SystemUser by email address. If a Matrix owner has no corresponding Dynamics 365 user account, FlitStack flags the record for your admin to either create the user first or reassign to a default owner. Owner resolution runs as a pre-flight check before the migration batch commits any records.

Matrix custom objects map 1:1 to Dataverse custom tables in Dynamics 365. If the Matrix custom object uses N:N relationships to contacts or accounts, FlitStack creates a junction table in Dataverse to preserve those associations. Custom object schemas are analyzed during discovery to generate the table-creation manifest with appropriate column types and relationship definitions.

Matrix workflows, sequences, and automation rules do not have a direct equivalent in Dynamics 365 Sales. FlitStack exports workflow definitions as JSON documents for your Power Automate or Dynamics 365 business rule rebuild. This export covers trigger conditions, action steps, and field update logic but does not execute automatically in Dynamics 365.

Matrix reports and dashboards do not transfer. The underlying data migrates, but report definitions require rebuild using Dynamics 365's built-in charts, Power BI, or the legacy SQL Server Reporting Services integration. FlitStack provides a data dictionary of migrated fields to assist your analyst in recreating key metrics.