Horus Eye · For Nonprofits on NPSP

NPSP Migration Readiness Assessment

Salesforce calls the move from NPSP — the Salesforce Nonprofit Success Pack — to Agentforce Nonprofit (formerly Nonprofit Cloud) a reimplementation — and reimplementations are priced by what your org actually contains, not by what the brochure assumes. Before you plan, budget, or sign anything: get the evidence. We analyze your real Salesforce NPSP org with Horus Eye, then an architect turns the findings into a migration decision you can defend to your board.[2][3][4]

Request a Readiness Assessment Read the Migration Guide

Why readiness is measurable — not a questionnaire

Evidence Over Estimates

Most “readiness assessments” in this market are a survey and a score. But two NPSP orgs with identical licenses can differ by an order of magnitude in migration effort — and the difference lives in the metadata: custom fields on NPSP objects, Apex and Flows that reference the package, integrations that read and write donation records, reports built on NPSP rollups, and the data debt accumulated over a decade of campaigns. None of that is visible to a questionnaire. All of it is visible to a scanner.

Horus Eye analyzes your org read-only across predefined rules in 12 domains — architecture, automation, data, security, development and more — and every finding carries its evidence: the component, the dependency, the reason it matters. That analysis becomes the factual floor of your migration conversation.

How the NPSP migration readiness assessment works: a read-only Horus Eye scan across predefined rules in 12 domains plus an architect review of NPSP to Agentforce Nonprofit mapping questions produce a decision readout with inventory, mapping decisions, cleanup list and recommendation
How it works: read-only scan + architect judgment → a decision readout — and “not yet” is a legitimate recommendation.

What the assessment examines

Your Org, Not a Template

Customization & coupling inventory

Which custom objects, fields, record types and components extend the NPSP data model — and which Apex, Flows, formulas, validation rules and Lightning components reference NPSP objects. This is the inventory Salesforce’s own migration guide says to build before choosing a strategy, and it is where migration quotes are won or lost.

Automation & integration dependencies

The flows and triggers wired to Contacts, Opportunities, Recurring Donations and Households — and the external systems (payment processors, marketing tools, volunteer platforms) whose compatibility with the new architecture has to be verified, not assumed. Horus Eye’s dependency analysis shows what touches what, with evidence.

Data debt that becomes migration debt

Duplicate constituents, orphaned relationships, inconsistent donation records, fields nobody has populated in years. In a migration, every record gets transformed — so every data problem becomes a transformation problem. We identify what to clean, what to archive, and what not to carry into the next decade.

Architect-led NPSP mapping review

The nonprofit-specific judgment calls — Contacts to Person Accounts, households worth keeping, the affiliation-collision question, which Opportunities become Gift Transactions versus Commitments — reviewed by a Salesforce architect against Salesforce’s own Agentforce Nonprofit Migration Guide[1] and your actual business processes. Tools inventory; architects decide.

What should an NPSP migration tool actually do?

Tools Inventory; Architects Decide

Teams searching for Salesforce NPSP migration tools usually mean one of three things: something that assesses the org, something that moves the data, or something that keeps the project honest. A worthwhile tool does all three without pretending to replace the architect. The evaluation checklist — the standard Horus Eye holds itself to, and the one we’d suggest you hold any Salesforce Nonprofit Cloud migration tool to, ours included:

And what no tool should do: name your go-live date, skip the sandbox, or guarantee an outcome — those belong to your team and your implementation partner.

More questions in this shape? The Horus Eye FAQ answers the AI, data-handling and permission questions admins and security teams ask.

Built on the audits Salesforce itself prescribes

The Guide’s Chapters 3 & 4

Salesforce’s migration guide opens with two audits before any strategy is chosen. The business process audit (chapter 3) asks why each configuration exists — real organizational need, or an accommodation of NPSP? — across permissions and record access, integrations and packages, and objects, fields and record types. The technical audit (chapter 4) asks how each piece works and classifies every integration and automation as compatible as-is, adaptable with modification, or requiring full redesign.

Five-phase migration sequence with the audit first — the readiness assessment is phase one, done before committing to the rest
Where this fits: the assessment is phase 1 of Salesforce’s own sequence — done before you commit to phases 2–5.

That is precisely the split our assessment automates and staffs: Horus Eye produces the how — the dependency inventory, the NPSP coupling, the automation and integration surface, with evidence — at scan speed instead of weeks of workshops, and the architect supplies the why, the classification calls, and the guide’s license-compatibility and change-management considerations. You get the audit chapters Salesforce says to do, done with instruments instead of interviews alone.

Beyond readiness: one desk, five stages

From Findings to a Validated Migration

Readiness is where the desk starts, not where it stops. The NPSP migration desk carries the whole journey on one screen — five stages, each with its status, and always one clear “do this next”:

1 · Understand

Every finding with its evidence; blockers and risks; and an honest account of how much of the approved assessment actually ran.

2 · Decide

Each question only your organization can answer, with the recommendation marked and the reasons stated — the sixteen named migration decisions plus your org’s own preparation questions. Accept records it; Change opens the options.

3 · Prepare

Migration scripts generated for this org from the recorded decisions, in run order — each showing what it reads, what it writes, and how you’ll know it worked.

4 · Validate

Pair your source org with the target sandbox; after your architect runs a script there, the two are compared by count — and the headline is always the status on your org, never on ours.

Validation pairs the source NPSP org with the target sandbox and compares record counts after each script runs
Stage 4, drawn: pair your source org with the target sandbox; after your architect runs a script there, the two are compared by count.

5 · Report. Deliverables written for the sponsor, the architect and the delivery manager; the decision register; readiness reports; the validation and cut-over assessment; a mapping workbook (Excel) and a Jira-ready backlog (CSV). See sample pages from each →

The Horus Eye NPSP migration desk: objective, five stages with their status, and one Do-this-next action
One desk, five stages, one next step — shown on a Kemisoft test org with seeded example data.

Go deeper in the knowledge base: the 16 decisions · the roadmap and go / no-go gates · where migrations go wrong · the admin’s checklist.

What you walk away with

The Readout

A readout your leadership can act on: the full customization and dependency inventory; the NPSP-coupled components that need mapping decisions (and which decisions they are); the data issues worth fixing before any migration — cleanup that pays off even if you stay; and a clear recommendation with reasoning: migrate soon, prepare first, or wait deliberately. If the right answer is “not yet,” that is what the readout says. There is no announced NPSP end-of-life, and we don’t invent deadlines.

When you do move, the same evidence base de-risks the project: the inventory becomes the migration workplan, and the cleanup list becomes the pre-migration sprint. Our nonprofit practice — NAACP, AIPAC, FASNY, the Chicago Community Trust — has lived on both sides of that handoff.

Sources & further reading

Read Salesforce’s primary documentation alongside any vendor’s summary, ours included.

Questions nonprofits ask us

FAQ
What is an NPSP migration readiness assessment?

A structured, evidence-backed analysis of your existing NPSP org — customization intensity, NPSP coupling, automation and integration dependencies, data debt — that tells you what a move to Agentforce Nonprofit would actually involve before you commit to a plan or budget.

Does it change anything in our org?

No. Horus Eye is read-only by default; it analyzes metadata and configuration without modifying your org, and every finding carries its evidence.

Will you push us to migrate?

No. This is decision support, not a funnel. “Stay on NPSP for now and clean up first” is a recommendation we genuinely make.

What do we receive?

The inventory, the mapping decisions, the pre-migration cleanup list, and an architect’s recommendation — migrate soon, prepare first, or wait deliberately — with the reasoning attached.

Protected AI — the Trust Layer

Every AI read in Horus Eye is metadata-first: built from an allowlist, sanitized by pattern, made through one audited gateway and checked by an output firewall on the way back — and AI is off by default, per org. Every request carries an audit id and an AI Data Scope manifest you can open.

See the Trust Layer

Start your migration readiness now

One readiness assessment now beats a mid-project surprise later. Read-only analysis of your real NPSP org, architect judgment on top.

Try Horus Eye Free Request a Readiness Assessment

Free start · 250 credits for 60 days · no card required · scans are free