Migrate from Wealthengine to Microsoft Dynamics 365 Sales

WealthEngine stores individual prospect records identified by name, email, address, or phone. FlitStack maps individuals to Dynamics 365 Contacts, resolving by email match for owner assignment. If a WealthEngine individual has no primary organization link, it creates a Contact without an AccountId — flagged for admin review.

Prospects in WealthEngine that have not been qualified as donors or customers in a CRM map to Dynamics 365 Leads. The WealthEngine screening result becomes a custom field on the Lead record, keeping the prospect in a pre-contact state until a rep qualifies them.

WealthEngine organizations are corporate or household entities linked to screened individuals. FlitStack maps organizations directly to Dynamics 365 Accounts, preserving aggregate wealth-attribute fields that reflect the organization's giving potential where WealthEngine provides organization-level scores. When no primary contact exists for an organization, FlitStack creates a standalone Account that may require admin review.

WealthEngine's screening result — Propensity to Give score, Gift Capacity Rating, Estimated Total Assets, Estimated Annual Donations — does not map to any native Dynamics 365 field. FlitStack creates custom fields on Contact (e.g., WE_Propensity_to_Give__c, WE_Gift_Capacity_Rating__c) and populates them from the screening result row linked to the individual.

WealthEngine organization-level enrichment attributes — Estimated Net Worth, Estimated Income Range, Business Ownership flags — are identified during planning and created as custom __c fields on Dynamics 365 Accounts. FlitStack creates these fields during the migration plan phase and populates them directly from the organization screening result data.

For prospects that land as Leads, WealthEngine's Propensity to Give and Gift Capacity Rating migrate to custom fields on the Lead entity. This preserves the wealth intelligence for sales and fundraising teams using Dynamics lead management without requiring a qualification step first.

WealthEngine logs screening session details — timestamp, lookup method (email, address, phone), and result confidence — for each enrichment. FlitStack maps these to custom text and datetime fields on the Contact so Dynamics users can see when and how the wealth data was sourced.

Organization screening session metadata (lookup method, screening date, API call count) migrates to custom fields on the Dynamics 365 Account record. Session metadata helps users evaluate data freshness when acting on wealth attributes, providing context on when and how the wealth screening was performed.

WealthEngine's internal contact ID (we_id) is preserved as Source_System_ID__c on the Dynamics 365 Contact. This ID enables delta-run de-duplication and allows FlitStack to match updated screening results back to the correct Contact on subsequent migration runs, maintaining a reliable link between the two systems.

WealthEngine's we_id is stored as Source_System_ID__c on the Dynamics Lead. This mapping supports delta-pickup scenarios where a Lead was enriched in WealthEngine after the initial migration run and needs to be updated in Dynamics, keeping the two systems synchronized over time.

WealthEngine supports lookups by email, address, or phone number. FlitStack records the lookup method used for each screening as a custom pick-list field (WE_Lookup_Method__c) on the Contact. This metadata indicates data confidence — email lookups typically return more attributes than phone-only lookups.

WealthEngine allows re-screening of the same individual over time, producing multiple result rows with updated scores. FlitStack migrates the most recent screening result as the primary custom field value and stores prior score snapshots as a JSON blob in a historical field (WE_Score_History__c) for trend analysis.