Migrate your Wealthengine data
Wealth intelligence and prospect research platform that enriches donor and contact records with modeled wealth scores, giving capacity ratings, and philanthropic data.
In its favor
Why people choose Wealthengine
The signal that keeps Wealthengine on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
WealthEngine aggregates over 60 data sources covering assets, income, real estate, business ownership, and charitable giving, giving fundraisers a single enrichment layer rather than buying multiple data subscriptions.
The Propensity to Give (P2G) score and Gift Capacity Rating provide modeled predictions that help fundraisers prioritize outreach without manually cross-referencing multiple spreadsheets.
Batch Screening handles hundreds or thousands of records in a single pass, which nonprofit development teams with large donor files say cuts prospect research time significantly.
Real-time On Demand Screening can be triggered at event registration or web sign-up, enabling wealth-informed engagement from the first touchpoint rather than post-campaign.
Out-of-the-box integrations with Salsa and Salesforce push enrichment data directly into existing workflows, reducing manual export-import cycles.
Prospect researchers report that data is sometimes missing or less precise for certain geographic regions, income brackets, or demographic segments, requiring manual verification before acting on scores.
WealthEngine operates on a subscription and API-call model with no publicly listed pricing, which creates uncertainty for organizations managing tight nonprofit budgets.
Nonprofit teams without dedicated development resources find the API-first approach and CRM integration setup to require more technical effort than expected.
Screening only enriches contacts the organization already has; WealthEngine does not supply net-new prospect names, so teams expecting a standalone prospecting tool feel the platform is limited to enrichment of existing lists.
Reasons to switch
Why people leave Wealthengine
The recurring reasons buyers give for replacing Wealthengine. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Wealthengine fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Wealthengine pricing overview
WealthEngine does not publish pricing on its website. Subscriptions are sold as custom quotes based on seat count, screening volume, and plan tier. Annual contracts are typical, and API call limits are set per-plan rather than published as standard rate cards.
Free / Sandbox
Tier 1 of 4
Free
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Wealthengine's schedule — see our quote-based pricing →
What gets migrated
Wealthengine object support
Object-by-object support for Wealthengine migrations. Per-pair details surface during scoping.
Profiles (Basic and Full)
Fully supportedProfiles are the core object returned by the WealthEngine API. Basic Profile returns a subset of wealth attributes; Full Profile includes the complete set. We preserve the full set of returned fields as custom contact properties in the destination CRM, tagging each field with the profile type so downstream users know which enrichment tier was used.
Wealth Scores and Ratings
Fully supportedProprietary scores including Propensity to Give (P2G), Gift Capacity Rating, Estimated Spending Capacity, RFM, Inclination: Giving, Inclination: Affiliation, Influence, and Planned Giving ratings. We migrate these as named numeric or tiered custom fields, mapping the rating scale to the destination system's equivalent field type (picklist or number) based on the customer's scoring model.
Screening Sessions
Mapping requiredScreening Sessions track which batch of records was processed at what time, with what parameters. We map session metadata (date, record count, screening type) into a custom object or audit log in the destination system, since most CRMs do not have a native session concept. Session results — the individual profile matches — are migrated as linked enrichment records.
Real Estate Holdings
Fully supportedWe migrate real estate attribute fields including estimated property value, property type, and address. These land as text or structured address fields in the destination CRM. Where multiple properties exist for a single profile, we flatten them into a semicolon-delimited list or create child records depending on the destination system's capabilities.
Charitable Contributions / Philanthropic Data
Mapping requiredEstimated Annual Donations, nonprofit board positions, foundation trusteeships, and volunteer activities are modeled fields rather than sourced transaction records. We preserve these as-is but flag them as modeled estimates in the destination system to prevent them from being mistaken for verified donation totals.
API Keys and App Credentials
Not in this platformAPI keys, session keys, and app credentials are scoped to the individual WealthEngine account and cannot be migrated. Customers must generate new credentials in the destination environment or in the target enrichment platform. We include this step explicitly in the migration checklist.
Users and Organization Account Settings
Not in this platformWealthEngine is a per-seat subscription without a hierarchical user-object model that maps to standard CRM users. Role assignments, team structures, and account-level preferences in WealthEngine do not have a direct equivalent in most destination systems and must be manually reconfigured post-migration.
Custom Reports and Saved Searches
Mapping requiredWe migrate the output of saved searches and custom reports as CSV exports before the cutover, but the saved search definitions themselves are platform-native. We convert the criteria into equivalent filtered views in the destination CRM where the schema permits, or flag them as reference documents for manual rebuild.
| Object | Support | Notes |
|---|---|---|
| Profiles (Basic and Full) | Fully supported | Profiles are the core object returned by the WealthEngine API. Basic Profile returns a subset of wealth attributes; Full Profile includes the complete set. We preserve the full set of returned fields as custom contact properties in the destination CRM, tagging each field with the profile type so downstream users know which enrichment tier was used. |
| Wealth Scores and Ratings | Fully supported | Proprietary scores including Propensity to Give (P2G), Gift Capacity Rating, Estimated Spending Capacity, RFM, Inclination: Giving, Inclination: Affiliation, Influence, and Planned Giving ratings. We migrate these as named numeric or tiered custom fields, mapping the rating scale to the destination system's equivalent field type (picklist or number) based on the customer's scoring model. |
| Screening Sessions | Mapping required | Screening Sessions track which batch of records was processed at what time, with what parameters. We map session metadata (date, record count, screening type) into a custom object or audit log in the destination system, since most CRMs do not have a native session concept. Session results — the individual profile matches — are migrated as linked enrichment records. |
| Real Estate Holdings | Fully supported | We migrate real estate attribute fields including estimated property value, property type, and address. These land as text or structured address fields in the destination CRM. Where multiple properties exist for a single profile, we flatten them into a semicolon-delimited list or create child records depending on the destination system's capabilities. |
| Charitable Contributions / Philanthropic Data | Mapping required | Estimated Annual Donations, nonprofit board positions, foundation trusteeships, and volunteer activities are modeled fields rather than sourced transaction records. We preserve these as-is but flag them as modeled estimates in the destination system to prevent them from being mistaken for verified donation totals. |
| API Keys and App Credentials | Not in this platform | API keys, session keys, and app credentials are scoped to the individual WealthEngine account and cannot be migrated. Customers must generate new credentials in the destination environment or in the target enrichment platform. We include this step explicitly in the migration checklist. |
| Users and Organization Account Settings | Not in this platform | WealthEngine is a per-seat subscription without a hierarchical user-object model that maps to standard CRM users. Role assignments, team structures, and account-level preferences in WealthEngine do not have a direct equivalent in most destination systems and must be manually reconfigured post-migration. |
| Custom Reports and Saved Searches | Mapping required | We migrate the output of saved searches and custom reports as CSV exports before the cutover, but the saved search definitions themselves are platform-native. We convert the criteria into equivalent filtered views in the destination CRM where the schema permits, or flag them as reference documents for manual rebuild. |
Gotchas
What to watch for in Wealthengine migrations
Issues we've hit on past Wealthengine migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| Medium | Profile lookups do not guarantee a match |
| Medium | API rate limits are plan-gated and not publicly documented |
| High | WealthEngine is an enrichment layer, not a contact database |
Leaving Wealthengine?
Where Wealthengine customers move next
12 destinations Wealthengine can migrate to.
How a Wealthengine migration works
Four steps, Wealthengine-specific
Connect
API Key (Bearer token) or Session Key into Wealthengine. Scopes limited to read-only on the data we move.
Map
We translate Wealthengine-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Wealthengine quirks before production.
Migrate
Full migration with Wealthengine rate-limit handling. Rollback available throughout.
FAQ
Wealthengine migration FAQ
Answers to the questions buyers ask most during Wealthengine migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Wealthengine migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Wealthengine.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Wealthengine setup and destination — written quote back within a business day.