CRM migration
Field-level mapping, validation, and rollback between Wealthengine and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Wealthengine
Source
Freshsales
Destination
Compatibility
11 of 13
objects map 1:1 between Wealthengine and Freshsales.
Complexity
BStandard
Timeline
24–72 hours
Overview
WealthEngine is a wealth-intelligence and prospect-enrichment platform — it does not store contacts, accounts, or deals natively. Instead, it returns wealth attributes (net worth, income, real estate, charitable giving, propensity scores) against a lookup request using name, address, email, or phone. The migration challenge is therefore two-part: exporting your enriched profiles from WealthEngine's batch-output format, then mapping those enrichment fields into Freshsales's object model as custom fields. FlitStack AI sequences the migration by first establishing which Contacts and Accounts in Freshsales correspond to enriched WealthEngine profiles (resolved by email or name+address match), then writing wealth attributes as custom fields on the correct records. Where WealthEngine stores complex composite objects like the Score Card (RFM, Inclination: Giving, Affiliation, Influence, Planned Giving), we flatten these into discrete custom fields and preserve the raw JSON blob for reference. Workflows, scoring models, and automation rules built in WealthEngine do not have a migration path — they must be rebuilt in Freshsales's native tools or reimplemented as Freshsales workflows post-cutover. The migration mechanism is a combination of WealthEngine batch export (CSV or API response files) and Freshsales REST API ingestion with custom field pre-creation on the Freshsales side.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Wealthengine object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Wealthengine
Individual Profile
Freshsales
Contact
1:1WealthEngine Individual Profile maps 1:1 to Freshsales Contact. Email, phone, name, and address from the WE lookup populate standard Contact fields. Wealth attributes attach as custom fields on the Contact record. Where the prospect has not yet been converted from a Lead in Freshsales, the Individual Profile maps to the Lead object first, with field mapping for WE attributes on the Lead.
Wealthengine
Individual Profile
Freshsales
Lead
1:manyIf the enriched profile corresponds to a Freshsales Lead (not yet a Contact), the WealthEngine Individual Profile maps to the Lead object. The same custom fields (net worth, propensity score, etc.) apply on Lead. Upon Lead conversion in Freshsales, these custom fields can be mapped to corresponding Contact fields using Freshsales's lead-conversion field mapping tool.
Wealthengine
Organization Profile
Freshsales
Account
1:1WealthEngine Organization Profile maps to Freshsales Account. Business name, industry, employee count, and annual revenue populate standard Account fields. Organization-level wealth attributes (business ownership indicators, foundation affiliations) attach as custom fields on the Account. Each enriched Individual Profile is linked to its corresponding Account via the Account lookup on the Contact record.
Wealthengine
Score Card (composite)
Freshsales
Multiple custom fields on Contact
1:manyWealthEngine's Score Card aggregates RFM (Recency, Frequency, Monetary), Inclination: Giving, Inclination: Affiliation, Influence, and Planned Giving indicators into one composite response. We split this into individual custom fields on Contact: RFM_Score__c, Inclination_Giving__c, Inclination_Affiliation__c, Influence__c, Planned_Giving__c. The raw JSON blob is preserved in Score_Card_Raw__c for audit reference.
Wealthengine
Net Worth Estimate
Freshsales
Net_Worth_Estimate__c (custom currency field on Contact)
1:1Net worth is stored as a currency field on the Contact. WealthEngine returns estimated ranges and point estimates — point estimates are stored directly; range values are stored as formatted text with the range bounds preserved. Precision is limited to WealthEngine's reported granularity (typically nearest $10k or $100k).
Wealthengine
Estimated Income
Freshsales
Estimated_Income__c (custom currency field on Contact)
1:1Estimated Income migrates as a currency field on Contact. Income bands from WealthEngine (e.g. '<$50k', '$50k-$100k') are stored as formatted text; point-estimate income is stored numerically. This field enables income-based segmentation in Freshsales reports, powers tiered lead scoring, and can be referenced in workflow conditions to route prospects into appropriate sales sequences or appeal campaigns. It also supports dashboard visualizations of donor capacity across the pipeline.
Wealthengine
Real Estate Holdings
Freshsales
Real_Estate__c (custom field on Contact)
1:1Real estate ownership, property count, and estimated value are consolidated into a formatted text field. If WealthEngine returns structured real estate records (multiple properties), these are stored as a JSON array in the custom field and can be parsed in Freshsales reports or via a supporting app.
Wealthengine
Stock & Business Ownership
Freshsales
Ownership_Indicators__c (custom field on Contact/Account)
1:1Business ownership flags, stock holdings, and executive board positions are consolidated into a multi-value text field. For executive board positions, the organization is linked via the Contact's Account lookup. Stock holding values are stored as a separate currency field if numeric.
Wealthengine
Charitable Giving History
Freshsales
Charitable_Giving__c (custom field on Contact)
1:1Estimated annual donations and giving capacity ratings migrate as custom fields on Contact. Gift_Capacity_Rating__c is a pick-list matching WealthEngine's rating scale. Estimated_Annual_Donations__c is a currency field. These fields feed into Freshsales deal qualification, appeal segmentation, and custom scoring rules to prioritize high-capacity donors. They also drive targeted campaign workflows, such as routing prospects to major-gift teams, and can be visualized in Freshsales dashboards to monitor fundraising pipeline health.
Wealthengine
Propensity to Give (P2G) Score
Freshsales
Propensity_to_Give__c (custom number field on Contact)
1:1WealthEngine's P2G score is a 0–100 numeric score predicting charitable giving likelihood. Migrates as a Number field on Contact. This can be used in Freshsales's custom scoring rules, workflow conditions, or Freddy AI lead scoring as a manual override signal.
Wealthengine
Enrichment Metadata
Freshsales
Source_System_ID__c, Last_Enriched__c, Match_Confidence__c (custom fields on Contact)
1:1Three metadata fields are attached to every Contact: Source_System_ID__c stores the WealthEngine profile ID for traceability and delta-run de-duplication; Last_Enriched__c is a datetime field capturing when WealthEngine last returned a match; Match_Confidence__c stores WealthEngine's confidence score (percent) for the lookup result. These ensure data provenance is visible directly on the Freshsales record.
Wealthengine
Batch Export File (CSV/API response)
Freshsales
Freshsales REST API / Import Wizard
1:1WealthEngine batch exports arrive as CSV files or API response JSON — neither matches Freshsales's import format directly. FlitStack AI transforms the export schema into Freshsales-compatible CSV with column headers matching Freshsales field API names, creates custom fields on Freshsales before import, and ingests via the Freshsales API respecting per-plan rate limits (1000/hr on Growth, 2000/hr on Pro, 5000/hr on Enterprise).
Wealthengine
WealthEngine Workflows / Scoring Models
Freshsales
No equivalent in Freshsales migration scope
1:1WealthEngine's propensity models, RFM calculations, and segmentation workflows are built on WE's proprietary scoring engine. These do not have a structural equivalent in Freshsales and cannot be exported as data. They must be rebuilt as Freshsales custom scoring fields, workflow conditions, or Freddy AI scoring rules post-migration. FlitStack AI exports WealthEngine workflow definitions as reference documentation for the rebuild.
| Wealthengine | Freshsales | Compatibility | |
|---|---|---|---|
| Individual Profile | Contact1:1 | Fully supported | |
| Individual Profile | Lead1:many | Fully supported | |
| Organization Profile | Account1:1 | Fully supported | |
| Score Card (composite) | Multiple custom fields on Contact1:many | Fully supported | |
| Net Worth Estimate | Net_Worth_Estimate__c (custom currency field on Contact)1:1 | Fully supported | |
| Estimated Income | Estimated_Income__c (custom currency field on Contact)1:1 | Fully supported | |
| Real Estate Holdings | Real_Estate__c (custom field on Contact)1:1 | Fully supported | |
| Stock & Business Ownership | Ownership_Indicators__c (custom field on Contact/Account)1:1 | Fully supported | |
| Charitable Giving History | Charitable_Giving__c (custom field on Contact)1:1 | Fully supported | |
| Propensity to Give (P2G) Score | Propensity_to_Give__c (custom number field on Contact)1:1 | Fully supported | |
| Enrichment Metadata | Source_System_ID__c, Last_Enriched__c, Match_Confidence__c (custom fields on Contact)1:1 | Fully supported | |
| Batch Export File (CSV/API response) | Freshsales REST API / Import Wizard1:1 | Fully supported | |
| WealthEngine Workflows / Scoring Models | No equivalent in Freshsales migration scope1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Wealthengine gotchas
Profile lookups do not guarantee a match
API rate limits are plan-gated and not publicly documented
WealthEngine is an enrichment layer, not a contact database
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit WealthEngine batch export and Freshsales schema
FlitStack AI ingests your WealthEngine batch export file (CSV or API response JSON) and catalogs every attribute returned per profile — net worth, propensity scores, giving history, real estate, and score card sub-components. Simultaneously, we inventory the target Freshsales account's existing objects, current custom field inventory, and remaining field capacity per module. This produces a gap analysis: which WealthEngine attributes map directly to Freshsales standard fields, which require custom fields, and whether the target Freshsales plan has sufficient field capacity for the full attribute set. We deliver this as a schema setup plan before any data moves.
Create Freshsales custom fields and resolve record owners
FlitStack AI (or your Freshsales admin) creates the custom fields identified in the gap analysis on Freshsales Contacts and Accounts. We apply Freshsales field types correctly — currency for net worth and income, number for propensity scores, pick-list for Gift Capacity Rating and ownership type, datetime for Last_Enriched__c, and text for Score_Card_Raw__c. Simultaneously, we resolve Freshsales user accounts by email match against WealthEngine owner metadata, flagging any unmatched owners so your team can assign a fallback owner or invite the user to Freshsales before the migration run.
Run sample migration with field-level diff
A representative sample — typically 100–500 enriched profiles spanning individual and organization records, high-net-worth and low-propensity profiles, and records with composite score cards — migrates first. FlitStack generates a field-level diff comparing the source WealthEngine values against the resulting Freshsales custom field values for each record. You verify that net worth estimates, propensity scores, Gift Capacity Ratings, RFM sub-components, and enrichment metadata landed correctly before the full run commits. This sample run also validates that the email-matching de-duplication logic resolved the correct Freshsales records.
Execute full migration with delta-pickup window
The full batch migration runs against Freshsales via the REST API, respecting per-plan rate limits (Growth: 1000/hr, Pro: 2000/hr, Enterprise: 5000/hr). A delta-pickup window of 24–48 hours after the full migration captures any WealthEngine records enriched or updated during the cutover. Every operation — field mapping, value transformation, owner resolution, and record creation — is logged in FlitStack's audit trail. One-click rollback is available if reconciliation identifies missing or misaligned records.
Deliver reconciliation report and rebuild reference
FlitStack AI generates a post-migration reconciliation report: record count by object, custom field fill rate (percentage of contacts with WealthEngine attributes populated), unmatched records requiring owner assignment, and any fields that exceeded the Freshsales plan's custom field limit and were deferred. We also deliver the WealthEngine workflow and scoring model definitions as a written rebuild reference for your Freshsales admin to reimplement scoring logic using Freshsales native tools.
Platform deep dives
Wealthengine
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Wealthengine and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Wealthengine: 600 calls per minute baseline; daily/monthly limits are plan-gated and not publicly documented.
Data volume sensitivity
Wealthengine doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Wealthengine to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Wealthengine to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Wealthengine
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.