Which record types does the target carry for people, accounts and gifts?

In NPSP, record types often exist to say what a record is — this Opportunity is a grant, that one is a membership. After migration, the objects themselves say that: a transaction, a commitment, a refund are different objects, not different labels on one. A record type carried over just to classify now duplicates what the data model states natively — and it is not free. Every record type kept is another layout to maintain, another branch in the security model to test, another value for reports to filter. The lean default — Person Account, household and organization accounts, with gift record types only where a page layout or business process genuinely differs — keeps the target org explainable.

The legitimate counter-case is installed-base gravity: reports, layouts and automation that select on a specific NPSP record type and must keep working unchanged. Carrying those types over one-for-one is sometimes the cheaper rebuild — but make that choice by listing the actual dependents, not by habit. A useful test for each candidate type: if it disappeared tomorrow, what specifically would break, and who would notice? A type with a concrete answer earns its place; a type whose defense is “we have always had it” is classification nostalgia, and the migration is the moment to let it go.

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 Help · Nonprofit Cloud Data Model Objects — The target objects, as Salesforce documents them. ↩︎
• 2. Salesforce · Fundraising Implementation Guide (PDF) — How Fundraising is planned and configured in the target: processes, objects, gift entry, RFM scoring. ↩︎

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