Migrate from Wealthengine to HubSpot

WealthEngine individual profile records map 1:1 to HubSpot Contact records. Resolution is by email match — WealthEngine profiles include email as a lookup key, and FlitStack resolves each profile to a HubSpot contact by email address before loading wealth properties. Unmatched profiles are flagged for manual review before the full run commits.

WealthEngine organization profiles (nonprofit, foundation, or corporate entities) map to HubSpot Company records. Organization-level wealth attributes such as foundation assets or corporate giving history are stored as custom properties on the HubSpot Company object. FlitStack resolves by organization name and domain where email domains are available.

WealthEngine returns net worth as a numeric estimate in USD. HubSpot has no native equivalent. FlitStack creates a custom number property (net_worth_estimate) on the Contact object and populates it with the most recent WealthEngine screen result. If WealthEngine returned a range (e.g., $5M–$10M), the midpoint is stored as a number for reporting compatibility.

WealthEngine total assets attribute — the sum of real estate, stock, business ownership, and other holdings — migrates as a custom number property on the HubSpot Contact. FlitStack parses the WealthEngine assets object and sums listed asset categories into a single total_assets value per profile.

WealthEngine cash-on-hand attribute migrates as a separate custom number property on the HubSpot Contact. This field is frequently null in WealthEngine profiles if the data source did not surface liquidity data — FlitStack records null as a blank property and flags it in the field-level diff report.

WealthEngine's proprietary Propensity to Give score is a numeric value (0–100 or tiered scale depending on plan). It migrates as a custom number property (p2g_score) on the HubSpot Contact. FlitStack also creates a read-only note property capturing the score interpretation label (e.g., 'High', 'Medium', 'Low') from the WealthEngine response.

WealthEngine Gift Capacity Rating is a categorical tier label (e.g., '$10K–$25K', '$25K–$50K', '$50K+'). FlitStack maps these as a custom HubSpot pick-list property (gift_capacity_rating) with values matching the WealthEngine rating taxonomy exactly so reporting in HubSpot dashboards uses consistent labels. Any tier labels not found in the WealthEngine response remain blank on the HubSpot Contact to avoid introducing inconsistent data.

WealthEngine provides an estimated annual donations figure based on philanthropic intent signals. This migrates as a custom number property (estimated_annual_donations) on the HubSpot Contact. Fundraising teams use this to segment major-gifts prospects directly in HubSpot list views without returning to WealthEngine.

WealthEngine does not maintain a persistent screening history on the profile — each API call returns a snapshot. FlitStack captures the timestamp of the most recent WealthEngine screen API response and stores it as a custom date property (last_wealthengine_screen_date) on the HubSpot Contact. This tells the fundraising team how current the wealth data is.

WealthEngine profiles that were ever enriched via screening (even if the most recent call returned no match) are flagged with a boolean property (ever_screened_in_wealthengine) set to true on the HubSpot Contact. Contacts without a WealthEngine profile are left blank — this property differentiates enriched from non-enriched contacts in HubSpot lists and workflows.

WealthEngine returns multiple categorical ratings — RFM (Recency, Frequency, Monetary), Inclination: Giving, and Influence — as separate attributes. Each maps to a distinct HubSpot pick-list property. FlitStack creates all three as custom properties and populates only those present in the WealthEngine response, leaving others blank.

If WealthEngine screenings were run in named batches (e.g., 'Capital Campaign 2025 Prospects'), FlitStack preserves the batch list name as a custom single-line text property on the HubSpot Contact. This allows fundraisers to filter HubSpot lists by the original screening cohort without needing WealthEngine access.

WealthEngine's internal profile identifier is stored as a read-only custom string property (wealthengine_profile_id) on the HubSpot Contact. This enables future delta re-enrichment: the FlitStack reconciliation run can look up the WealthEngine profile ID and update the HubSpot contact properties with a fresh screen result.

WealthEngine profiles include organization affiliation when a donor is linked to an employer or foundation. FlitStack resolves the organization to a HubSpot Company record by name/domain match and creates the native HubSpot contact-to-company association. Multi-affiliation edges (a contact employed by two organizations in WealthEngine) are handled as primary plus secondary Company associations.

For organization-level WealthEngine profiles (foundations, nonprofits screened as prospects), FlitStack creates custom text properties on the HubSpot Company object to store the WealthEngine account type and subscription tier used for the screening. This helps the fundraising team understand what data depth was available for each organization in WealthEngine.