Outreach Source Codes under the campaigns, or campaigns alone?

Attribution is where fundraising analytics lives or dies, and the target model changes its mechanics: Salesforce’s mapping carries a gift’s campaign through an Outreach Source Code under the campaign, not a bare campaign lookup. Following the mapping keeps appeal- and channel-level reporting — the “which letter, which segment, which channel” layer below the campaign — intact in the shape the target’s fundraising objects expect. The simpler “campaigns alone” route loads fewer records but flattens exactly that layer; it suits a team that genuinely reports by campaign only, and short-changes everyone else.

Two companion choices travel with this one and deserve their own recorded answers. Campaign members: the Migration Guide treats them as deprecated in the target model, so each org decides — archive them (the usual answer), migrate them, or discard them, counted and listed whichever way. And the campaign hierarchy: flatten it (leaf campaigns become source codes, middle levels drop, top levels remain campaigns) or carry it one-to-one. The right answer is whichever one your fundraising team’s actual reports can be rebuilt on — pull last year’s campaign performance reports and check what level they really read before deciding.

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 · Outreach Source Codes — Campaign attribution in the target, as Salesforce documents it. ↩︎
• 2. 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. ↩︎

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