CRM migration

Migrate from Wealthengine to Nutshell

Field-level mapping, validation, and rollback between Wealthengine and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Wealthengine logo

Wealthengine

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Wealthengine and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

WealthEngine is a wealth intelligence and prospect research platform used primarily by nonprofits and fundraising teams. It does not function as a CRM — it enriches contacts with wealth attributes like Propensity to Give (P2G), Gift Capacity Rating, net worth estimates, real estate holdings, charitable contributions, and behavioral scores. Your WealthEngine data lives either as enrichment attached to contacts in your existing CRM (e.g., DonorPerfect, Salesforce) or as a standalone WealthEngine export file. Nutshell is a small-to-mid-market CRM built around Person, Company, Deal, Lead, and Activity records with native support for custom fields on every object. We map WealthEngine person profiles to Nutshell Person records with all wealth attributes stored in custom fields, WealthEngine organization-level data to Nutshell Company records, and all screening metadata (screening date, data sources, match confidence) as audit fields on the Person. We do not migrate workflows because WealthEngine has no workflow engine to export. Reports and dashboards built in WealthEngine have no direct Nutshell equivalent — we rebuild them using Nutshell's built-in reporting and exported CSV analytics. The migration runs via Nutshell's JSON-RPC API with Basic auth and Nutshell's own API endpoint, sequencing record creation to respect both WealthEngine's 600-calls-per-minute API limit and Nutshell's import throughput. A delta-pickup window captures any new WealthEngine enrichment added during cutover.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Wealthengine logo

Wealthengine

What's pushing teams away

  • 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.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Wealthengine objects map to Nutshell

Each row shows how a Wealthengine object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Wealthengine

Person Profile

maps to

Nutshell

Person

1:1
Fully supported

WealthEngine person profiles map 1:1 to Nutshell Person records. The primary lookup key is email address — matched against Nutshell Person.email. Profiles that have no email in WealthEngine are matched by first name + last name + address combination. Unmatched profiles are flagged for manual review before the full migration runs.

Wealthengine

Organization (company-level data)

maps to

Nutshell

Company

1:1
Fully supported

WealthEngine returns organization attributes for individuals who are business owners, board members, or associated with companies. This data maps to Nutshell Company records by matching the organization name and domain. When no matching Nutshell Company record exists, we create one using WealthEngine's organization name and available attributes — industry, employee count estimates, and website.

Wealthengine

P2G Score (Propensity to Give)

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine's Propensity to Give score has no equivalent in Nutshell's native field set. We create a custom Number field on Nutshell Person called P2G_Score__c and store the numeric score directly. For records where WealthEngine returned a P2G tier (Low, Medium, High) rather than a raw score, we store the tier as a custom pick-list field instead.

Wealthengine

Gift Capacity Range

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine's Gift Capacity Range is a giving potential estimate expressed as a dollar range (e.g., $1,000–$5,000). This maps to a custom Currency-Range field on Nutshell Person — stored as two number fields (Gift_Capacity_Min__c and Gift_Capacity_Max__c) to preserve the range. If WealthEngine returns a single estimated figure, it lands in Gift_Capacity_Estimated__c.

Wealthengine

Total Assets

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine's Total Assets field aggregates real estate, investment, and other asset holdings into a net worth indicator. This maps to a custom Currency field on Nutshell Person called Total_Assets__c. We flag whether the asset figure is estimated or verified based on WealthEngine's confidence flag stored alongside the attribute.

Wealthengine

Estimated Annual Donations

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine estimates annual charitable giving based on its model of donor behavior. This maps to a custom Currency field on Nutshell Person called Estimated_Annual_Donations__c. The field supports comparison against actual giving history if the client's Nutshell also tracks donation records.

Wealthengine

Real Estate Holdings

maps to

Nutshell

Person custom field (repeating group)

1:1
Fully supported

WealthEngine returns individual real estate parcels with estimated value, property type, and location. Nutshell custom fields are flat — repeating groups require a custom object or concatenated text field. We store the primary parcel as Real_Estate_Primary_Value__c and a text summary of additional holdings in Real_Estate_Summary__c. Full parcel detail is preserved as a JSON blob in a Long Text Area field for admin reference.

Wealthengine

RFM Rating (Recency, Frequency, Monetary)

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine's RFM rating combines giving recency, frequency, and monetary value into a composite score. We create three separate custom Number fields on Nutshell Person — RFM_Recency__c, RFM_Frequency__c, and RFM_Monetary__c — plus a composite RFM_Score__c field. If WealthEngine returns a single RFM tier label, it maps to a custom pick-list field instead.

Wealthengine

Inclination: Giving / Affiliation

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine behavioral inclination scores indicate a person's likelihood to engage in charitable giving and their affiliation with causes. These map to two custom pick-list fields on Nutshell Person: Inclination_Giving__c and Inclination_Affiliation__c. Each stores the WealthEngine rating label (e.g., High, Medium, Low) or a numeric propensity score based on what WealthEngine returned for the profile.

Wealthengine

Screening Metadata (date, source, confidence)

maps to

Nutshell

Person custom fields

1:1
Fully supported

Every WealthEngine profile carries audit metadata: the date the record was last screened (lastModifiedDate), the date WealthEngine first created the profile (createdDate), and a confidence flag indicating match quality. We store these as three custom fields on Nutshell Person: WealthEngine_Screened_Date__c (Date), WealthEngine_Created_Date__c (Date), and WealthEngine_Match_Confidence__c (Pick-list: Verified, Probable, Estimated).

Wealthengine

Data Sources

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine aggregates from 60+ public and proprietary data sources. We store the most relevant sources as a text field (WealthEngine_Data_Sources__c, Long Text Area) on Nutshell Person so your team can audit which public records informed each wealth estimate without logging back into WealthEngine.

Wealthengine

Planned Giving Indicators

maps to

Nutshell

Person custom field

1:1
Fully supported

WealthEngine flags planned giving indicators (bequest, annuity, trust) as separate attributes. These map to individual custom Checkbox fields on Nutshell Person: Planned_Giving_Bequest__c, Planned_Giving_Annuity__c, and Planned_Giving_Trust__c — set to true when WealthEngine indicates the flag is active for the profile. This allows your team to filter and segment prospects based on their planned giving status directly within Nutshell's native list views and reports.

Gotchas + challenges

What specifically takes care here

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 logo

Wealthengine gotchas

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • WealthEngine API 600 calls-per-minute limit requires batch sequencing

    WealthEngine's API enforces a hard 600 calls per minute ceiling with plan-dependent daily and monthly quotas. When a client's WealthEngine data is sourced from the API rather than a manual export, bulk retrieval requires sequencing API calls across batches with delay insertion to avoid HTTP 429 errors. The sub-second response time helps but large datasets of 50,000+ profiles can take hours to pull depending on the plan tier. We implement a queue-based retriever with exponential backoff on 429 responses and batch WealthEngine profile fetches into groups of 100 so the retrieval phase does not exceed the rate cap. This is disclosed because it directly affects the timeline estimate for API-sourced migrations — file-export-based migrations skip this step entirely.

  • No-match profiles require decision before import completes

    WealthEngine explicitly states that match rates vary by the identifier used for lookup — name and address lookup has different coverage than email lookup, and the national database does not contain every U.S. adult. When WealthEngine returns no profile match for a contact, the Nutshell Person record is created without any wealth attributes. We flag every no-match record in a separate review report delivered alongside the migration. Your team decides whether to accept records without enrichment as-is, re-screen those contacts with a different identifier, or remove them from the import. The migration plan documents this threshold before the full run so your team is not surprised by the no-match rate during cutover.

  • Real estate holdings and wealth ranges collapse to summary fields

    WealthEngine returns multi-parcel real estate holdings as a repeating group with individual property values and addresses. Nutshell's custom fields are flat key-value pairs — there is no native repeating-group or sub-object model for Person-level attributes. We store the primary parcel value in a dedicated Currency field and compress additional holdings into a JSON-encoded text field. The full parcel detail is preserved and queryable via Nutshell's API but not visible in the standard Nutshell UI without a custom component. If your team needs multi-parcel visibility in the native UI, a Nutshell custom object with a lookup to Person is the correct architecture — we include this as a post-migration recommendation when the wealth data warrants it.

  • WealthEngine organization data may duplicate or conflict with existing Nutshell Companies

    WealthEngine returns organization affiliation for individuals (business owner, board member, executive) but the organization itself may already exist as a Nutshell Company record from a separate data source. If the Nutshell Company name and the WealthEngine organization name differ slightly — due to legal suffix variation or abbreviation — we risk creating a duplicate Company record. We resolve this by fuzzy-matching organization names during the migration plan phase and surfacing duplicate candidates. Your admin chooses whether to merge the existing Nutshell Company with WealthEngine's organization attributes or keep them separate. We do not auto-merge to avoid overwriting data your team has already curated in Nutshell.

  • WealthEngine Salesforce integration package issues mean API data may be stale

    G2 reviews document that WealthEngine's Salesforce installed package has had reliability problems — enrichment results failing to write back to Salesforce contacts, API authentication expiring, and profile sync dropping silently. If your WealthEngine data currently lives in Salesforce via the installed package, the data may already be incomplete or outdated. We recommend re-screening all contacts via WealthEngine's API before the migration rather than relying on potentially stale data that passed through the broken Salesforce package. This adds a screening phase to the migration timeline but ensures Nutshell receives the complete and current enrichment, not the filtered result of a broken integration.

Migration approach

Six steps for a successful Wealthengine to Nutshell data migration

  1. Audit WealthEngine data source and export method

    Before any mapping begins, FlitStack AI determines how your WealthEngine data is stored. The most common setup is WealthEngine enrichment attached to contacts in a connected CRM (DonorPerfect, Salesforce, Blackbaud Raiser's Edge) — in this case, we export from the CRM rather than from WealthEngine directly. If WealthEngine is accessed via API, we retrieve profiles using the findOne endpoints (by email, address, or phone) and paginate through the full contact list. We also check whether WealthEngine's Salesforce installed package has been used — if so, we flag any known-sync-failure contacts for re-screening. The output of this step is a data inventory showing record count, data source, and the coverage rate for each wealth attribute.

  2. Create Nutshell custom fields and document mapping plan

    FlitStack AI creates every required custom field in Nutshell before any import begins — P2G_Score__c, Gift_Capacity_Min__c, Gift_Capacity_Max__c, Total_Assets__c, RFM_Recency__c, RFM_Frequency__c, RFM_Monetary__c, Inclination_Giving__c, Inclination_Affiliation__c, Planned_Giving_Bequest__c, WealthEngine_Screened_Date__c, WealthEngine_Match_Confidence__c, and all other attributes identified in the data audit. Each field's type (Currency, Number, Pick-list, Checkbox, Date) is set to match the WealthEngine data format. We deliver a field-by-field mapping plan so your Nutshell admin can review and approve field names and data types before any data is written.

  3. Resolve organization data and company duplications

    WealthEngine organization affiliations are matched against existing Nutshell Company records by name and domain. Fuzzy matching handles legal suffix variations (Inc vs. LLC vs. Corporation) to prevent duplicate Company records from being created. Candidates for duplicate resolution are surfaced in the mapping plan with both the existing Nutshell Company data and the WealthEngine organization attributes so your admin can choose the merge approach. Organization attributes that have no Nutshell Company equivalent are created as new Nutshell Company records. This step sequences before Person import so AccountId lookups on Nutshell Person records resolve correctly if your Nutshell configuration links Persons to Companies.

  4. Run sample migration with field-level diff

    A representative slice of 100–300 Nutshell Person records migrates first, covering a range of wealth attribute completeness — records with full P2G scores, records with no match, records with multi-parcel real estate, and records with RFM ratings. We generate a field-level diff showing what landed in each custom field and flag any attributes that failed to write due to format mismatches. You review the sample in Nutshell to confirm the field placement, the no-match handling, and the organization resolution before we commit to the full run. Adjustments to field types, pick-list values, or organization merge rules are made at this stage at no additional cost.

  5. Execute full migration with delta-pickup window

    The full migration runs via Nutshell's JSON-RPC API, using Basic auth with an API key scoped to your Nutshell account. WealthEngine API calls are sequenced to stay within the 600-calls-per-minute limit using a queue-based retriever with delay insertion. All Nutshell Person and Company records are created or updated in dependency order — Companies first, then Persons with organization lookups resolved, then custom field population. A delta-pickup window opens after the initial run completes (typically 24–48 hours) to capture any new WealthEngine enrichment added during cutover. An audit log records every API operation. One-click rollback reverts all records to their pre-migration state if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Wealthengine logo

Wealthengine

Source

Strengths

  • Aggregates data from 60+ sources into a single normalized wealth profile on U.S. individuals.
  • Provides the Propensity to Give (P2G) score and Gift Capacity Range, which are uncommon in general-purpose CRMs.
  • Batch Screening handles large donor files without per-record manual lookups.
  • RESTful API with sub-second response times and sandbox environment for testing.
  • Direct integrations with Salsa and Salesforce reduce engineering overhead for common nonprofit CRM stacks.

Weaknesses

  • WealthEngine does not supply net-new prospect names — it only enriches records the customer already holds.
  • Profile coverage is not uniform across all U.S. adults; match rates vary by lookup identifier (name/address vs. email vs. phone).
  • Pricing is not publicly documented, making budget planning difficult for organizations without dedicated sales engagement.
  • API-first architecture means non-technical fundraisers depend on IT or developer resources to set up and maintain integrations.
  • Modeled fields (e.g., Estimated Donations, Net Worth ranges) are algorithmic estimates, not verified financial data.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Wealthengine and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Wealthengine: 600 calls per minute baseline; daily/monthly limits are plan-gated and not publicly documented.

  • Data volume sensitivity

    B

    Wealthengine doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Wealthengine to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Wealthengine to Nutshell data migrations

Answers to the questions buyers ask most during Wealthengine to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Wealthengine to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most WealthEngine-to-Nutshell migrations complete in 48–72 hours of clock time for under 50,000 records. The longest phase is usually creating the Nutshell custom fields and reviewing the mapping plan — that runs in parallel with data audit. API-sourced WealthEngine retrievals add time proportional to your record volume and plan tier rate limits; file-based exports from a connected CRM skip the API rate-limit wait entirely. Larger datasets with 500,000+ records or complex organization-deduplication scenarios extend to 5–10 days.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Wealthengine.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day