NPSP Migration Decisions · AD-3
Which source record becomes the Gift Transaction: the gift, its payment, or both?
When one gift was paid in several payments, which record becomes the Nonprofit Cloud Gift Transaction[2]? The grain decides whether payment-level history survives, how revenue is counted, and what reconciliation compares. It sounds technical; it is actually a finance question about how your organization wants to see its money.[1]
Who decides
Finance with the fundraising lead
Decide after
MD-2 (gift classification)
Estimated effort
S one working session with finance
What answers it
How gifts and payments are structured in the org — single-payment gifts versus installment gifts.
Your options, and what each one does
The Options| The option | What it means for the migration |
|---|---|
| One Gift Transaction per paid payment; multi-payment gifts become Gift Commitments | Follows Salesforce’s workbook: a payment’s gift maps to the Gift Transaction’s Gift Commitment. A single-payment gift is one Gift Transaction; revenue is counted once; installment detail is kept as transactions under their commitment. |
| One Gift Transaction per gift, payments merged into it | Simpler, but loses the payment-level history of gifts paid in installments, and diverges from Salesforce’s workbook for multi-payment gifts. |
What Horus Eye recommends — and when
Recommendation, Not VerdictOne Gift Transaction per paid payment — it is how Salesforce’s workbook maps a payment, and it counts each received amount once. What would change it: a finance requirement to report each gift as a single record regardless of how it was paid. The Nonprofit Cloud gift transaction grain shapes every report downstream, so decide it deliberately.
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 PracticeStrip away the object names and this is a finance question: when a donor paid one gift in four installments, how many revenue records should the new org hold? Salesforce’s workbook answers “four transactions under one commitment” — each paid payment becomes a Gift Transaction, the gift itself becomes the Gift Commitment above them — and that answer has two virtues: every received amount is counted exactly once, and installment-level history survives for anyone who later asks when the money actually arrived. The alternative — one transaction per gift with payments merged — reads simpler but quietly discards payment-level history and departs from the workbook for every multi-payment gift, which means custom explanation forever after.
The grain also sets what reconciliation means. Counts and amounts will be compared between old and new org by fiscal year and fund, to the cent; the grain decides what a “row” in that comparison is, so changing your mind later re-opens reconciliation itself. Settle it with finance early, in their language — “how do you want to see installment gifts in the books?” — and let the genuine exception (a hard finance requirement for one record per gift) be argued explicitly rather than drifted into.
Questions to settle before you record an answer
Before You DecideHow 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 PlanningSources & 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 · Gift Transactions — The received-gift object NPSP Opportunities classify into. ↩︎
“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