Migrate from Populate to Microsoft Dynamics 365 Sales

Populate Contacts map directly to Dynamics 365 Sales Contacts. The primary company association in Populate (company-name text property) resolves to an AccountId lookup after Accounts are migrated first. Unmatched companies receive a default placeholder Account. Owner resolution happens via email matching against Azure AD-synced users in Dynamics 365 Sales.

Populate records without a company association can route to Dynamics 365 Sales Leads. FlitStack applies a configurable rule — if a record has email domain X, assign it to Lead; otherwise create as Contact with a placeholder Account — based on your business logic during discovery.

Populate Companies map to Dynamics 365 Sales Accounts. Parent-company relationships in Populate translate to the ParentAccountId lookup in Dynamics. Multi-company networks in Populate with N:N associations collapse to one primary Account per Contact, with secondary links surfaced as Account Contact Relationships.

Populate Deals map directly to Dynamics 365 Sales Opportunities. The deal name becomes Opportunity Name; amount and close date translate directly. Pipeline and stage names undergo value mapping against the target Opportunity Stage pick-list defined in Dynamics 365 Sales. Stage probability values are reapplied from the destination Business Process Flow during migration.

Stage names are mapped value-by-value. Each unique Populate deal stage is matched to the nearest equivalent Dynamics 365 Sales stage name, and stage probability values are applied from the destination Business Process Flow. Unmapped stages default to the nearest closed stage or an open stage per your specification.

Populate activity types split into their Dynamics 365 Sales equivalents: emails become Email activities, calls become Phone Call activities, meetings become Appointments, and standalone notes become Notes. Original timestamps, activity owners, and regarding-object links (Contact, Account, Opportunity) are preserved during migration to maintain full audit history.

Every unique Populate custom property that has no native Dynamics 365 Sales equivalent requires a custom Dataverse column created before migration runs. FlitStack delivers a custom-field creation manifest listing each property, its data type, and whether a pick-list value map is needed. Sales Enterprise or Premium is required for unlimited custom tables; Sales Professional is limited to 15 custom tables.

Populate custom objects map 1:1 to Dataverse custom tables. Custom-object associations that use Populate's N:N relationship model need a junction table in Dynamics 365 Sales — FlitStack surfaces these in the schema plan and creates the relationship tables before data loads.

Files attached to Populate records are downloaded and re-uploaded to the corresponding Dynamics 365 Sales record's SharePoint document location or Notes attachment. File size limits follow Dynamics 365 Sales storage quotas. Inline images in notes are extracted and rehosted as note attachments.

Populate owner IDs are resolved by email match against Dynamics 365 Sales users (synced from Azure Active Directory). Records whose owner email has no matching Dynamics user are flagged before migration commits — your admin either invites the user or reassigns to a fallback owner. Source system owner IDs are preserved as a read-only custom field.

Populate workflow definitions do not migrate. We export each workflow's trigger, conditions, and actions as a structured JSON reference document that your Dynamics admin can use to rebuild equivalent flows in Power Automate. The rebuilt flows are not validated by FlitStack as part of the data migration.

Populate reports and dashboards do not transfer. The underlying data migrates to Dynamics 365 Sales, so reports can be rebuilt using native Dynamics reporting tools or Power BI connected to Dataverse. FlitStack does not rebuild reports as part of the data migration scope.