Migrate from Wealthengine to Twenty CRM

WealthEngine person profiles (name, email, phone, address) map directly to Twenty's People object. The import resolves People by email — each person record must be unique by email address in Twenty. If a person has multiple enrichment records from different screening batches, the most recent enrichment value wins for each attribute.

When WealthEngine profile data includes employer or associated organization, that name maps to Twenty's Companies object using the domain or company name as the unique key. The import order enforces that Companies must exist before People records are imported so Twenty can resolve the companyId relation.

Twenty has no native net-worth field. FlitStack pre-creates a custom field (Net_Worth__c) in Twenty's Settings → Data Model as a currency or number type before the import runs. The WealthEngine net-worth value (e.g., '$2.4M – $4.1M') is stored as a number using the midpoint or lower-bound value per agreed mapping convention.

Income data from WealthEngine requires a custom field (Estimated_Income__c) on the People object in Twenty. Income band values (e.g., '$250K–$500K') are stored numerically using the band midpoint; ranges that cannot be resolved are stored as a custom text field with the original label preserved.

WealthEngine's P2G score is a proprietary composite score (0–100 or similar scale) with no native Twenty equivalent. FlitStack creates P2G_Score__c as a custom number field on People and maps the score directly. The original score label (if any) is preserved in a companion P2G_Label__c text field.

Real estate property counts, values, and addresses from WealthEngine require custom fields. If the migration includes multiple properties per person, FlitStack creates a custom object (Real_Estate_Property__c) linked to People via a one-to-many relation, or stores a summary string (property count, total value) on the People record as a text field — the choice is made during schema planning.

WealthEngine giving-capacity ratings (e.g., Gift Capacity Range, Inclination to Give) migrate to custom fields on the People object. If detailed donation history is included, a custom object (Giving_History__c) linked to People may be required; if summary scores only, fields like Giving_Capacity_Rating__c and Inclination_to_Give__c store the values directly.

WealthEngine's markers of wealth (stock holdings, private company ownership, board positions) map to text or multi-select custom fields on the People object. A custom field (Wealth_Markers__c) stores the full list as a comma-separated or multi-select value; a companion number field (Business_Ownership_Value__c) captures estimated value if provided.

WealthEngine batch screening runs produce metadata (screening date, batch ID, screening tier) that is not a standard field on a profile. FlitStack creates a Screening_Batch__c text field and a Last_Screened__c date field on the People object to preserve the context of when and in what batch each enrichment record was produced.

WealthEngine's internal profile ID (the source system ID) is stored as Source_System_ID__c on the People record in Twenty. This enables delta-run reconciliation — when WealthEngine updates enrichment for a subset of profiles, FlitStack matches on Source_System_ID__c to update only the changed fields in Twenty without creating duplicates.

If WealthEngine was connected to a CRM that also holds Deals or Opportunities, those objects do not exist in WealthEngine itself — they live in the connected CRM. FlitStack does not migrate those records as part of a WealthEngine-to-Twenty migration; the recommendation is to run a parallel migration from the connected CRM to Twenty for Deals and Opportunities while the WealthEngine enrichment data migrates simultaneously.

WealthEngine does not have native workflow or sequencing logic — it is a data-enrichment service, not a CRM with automation. Any automated rules that triggered enrichment calls in a connected CRM must be rebuilt in Twenty's workflow builder post-migration. FlitStack exports the rule definitions from the connected CRM as a reference for the rebuild.