NPSP Migration Decisions · AD-5
Which records outside the core migration move — and where does the rest go?
The NPSP data archive question starts where the transformation specification[1]s stop: they cover constituents, households and gifts — but an org also holds users, leads, tasks and events, files, notes and old campaigns. Files, notes and attachments are not in Salesforce’s mapping workbook at all. Each category is a scope call: migrate it, or archive it somewhere verified readable. In a new-org strategy, nothing survives that is not deliberately loaded.[2]
Who decides
Data owners with the executive sponsor
Decide after
AD-1 (target org strategy)
Estimated effort
M count the volumes, pick the archive
What answers it
The measured volumes of tasks, events and files, and any retention policy that sets how much history must stay live.
Your options, and what each one does
The Options| The option | What it means for the migration |
|---|---|
| Migrate what the teams use, archive the rest | Users move first (every load needs the owner crosswalk); leads before campaign members; tasks and events re-pointed to their migrated records; files re-parented. What is not migrated is exported to an archive, verified readable, and kept with the crosswalk. |
| Archive all activity history and files | A smaller load; the history stays readable only in the archive, and open tasks are re-created by hand. |
What Horus Eye recommends — and when
Recommendation, Not VerdictCount before you choose — the split is decided by the measured volumes and your retention policy, not by taste. Whatever is archived: verify the archive is actually readable before cut-over, and record where it lives and for how long. The NPSP data archive is a decision about obligations, not storage.
A recommendation is a starting point, not a verdict. The same question lands differently org by org — one fact about your automation, volumes or vendors can flip the right answer. That is why the reasons are stated, and what would change them.
How this decision plays out
In PracticeThe core migration moves constituents, households and gifts — but an org is also years of tasks, events, notes, files and old campaigns, and in a new-org strategy none of it survives unless deliberately loaded. Files, notes and attachments are not in Salesforce’s mapping workbook at all, so their fate is entirely this decision. The honest default — migrate what teams actively use, archive the rest — only works when “use” is measured rather than asserted: count the volumes, check the retention policy, and let the split follow the evidence. Sequencing matters more than it looks, too: users move first because every record needs an owner, activities re-point to migrated records through the crosswalk, files re-parent to their new homes.
Two rules keep the archive from becoming a regret. First, “archived” means verified readable — somebody opens the archive and finds a known record in it before cut-over, not during an audit two years later. Second, the archive gets an address and a lifetime: which platform, who can query it, how long it is kept. “We exported it somewhere” is how institutional history disappears; a named archive with a named owner is how it survives the org that created it.
Questions to settle before you record an answer
Before You Decide
How Horus Eye helps
With Horus EyeWhen Horus Eye assesses an NPSP org, this question is raised with the evidence the scan saw — the record types, fields and settings behind it — its recommendation marked, and the reasons stated. Accept records the recommendation; Change opens the options. Recording an answer writes nothing to Salesforce: it is captured in the decision register, with who decided and when, and the migration plan, mappings and documents are kept consistent with what your organization actually decided. Horus Eye recommends; your organization decides.
Related decisions
Keep Planning- AD-1 · Target org strategy — A new Agentforce Nonprofit org, or transform NPSP in place?
- MD-7 · Program data (PMM) — Which Program Management data must migrate to the target program and benefit objects?
- MD-5 · Fields without a target — Where does the information in fields without a direct target go?
- All sixteen decisions →
Sources & further reading
References- 1.
Salesforce · Agentforce Nonprofit Migration Guide v2.0 (PDF) — The official guide this content follows: platform differences, migration recommendations, and how NPSP features map to Agentforce Nonprofit. ↩︎ - 2.
Salesforce Help · Nonprofit Cloud Migration and Implementation Guides — Salesforce’s index of the migration, implementation, Fundraising and Program Management guides. ↩︎
“Salesforce”, “Agentforce” and related marks are the property of Salesforce, Inc. Horus Eye is an independent product and is not affiliated with, endorsed, or sponsored by Salesforce, Inc.
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.
Facing this decision in your own org?
Horus EyeA read-only assessment puts the evidence behind it on the table — what your org holds, what it means for this choice, and the decisions that depend on it.
Try Horus Eye Free Request an Assessment All Horus Eye pagesFree start · 250 credits for 60 days · no card required · scans are free