A new Agentforce Nonprofit org, or transform NPSP in place?

Every other decision can be revisited; this one cannot, which is why it comes first. Person Accounts, once enabled in an org, cannot be disabled — Salesforce is explicit about it. Migrate in place and you take that irreversible step inside the org your fundraisers are using today; migrate to a new org and you take it in a clean room while NPSP keeps running untouched. That difference is what makes back-out real: with a new org, the worst day before the point of no return ends with “re-open entry in NPSP and regroup”; in place, the org itself has already changed under you.

The new-org path has honest costs, and naming them builds trust with whoever signs the license agreement: a second org to license during the transition, NPSP kept licensed and read-only for an agreed period after go-live, and users, permission sets and every kept integration set up fresh against the new org. The in-place path trades those costs for concentrated risk. What genuinely flips the answer is rare but real: an external system keyed to the org’s ID that cannot be re-pointed, a licensing position that makes two orgs untenable, data volumes that cannot load inside the cut-over window, or a contract that names the org. Check for all four before defaulting to either path.

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

• 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 · Enable Person Accounts for Fundraising — The enablement step — and why it is planned, not casual: Person Accounts cannot be disabled once enabled. ↩︎
• 3. 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.