Solutions4sf I build CRMs, and fix the ones that broke

Case study · Sales Cloud for a charity, no NPSP

Gifts from different people stopped landing on one donor.

After the order history was reloaded from the website, Salesforce matched the website’s own orders, month by month. The client is a charity foundation in Ukraine that takes donations on its website and keeps them in Sales Cloud. No NPSP, no Nonprofit Cloud: donors are person accounts, gifts are opportunities. I repaired how a donor is matched and how a gift arrives, and set how a donor’s first campaign is kept for every gift from the change on. All of it runs in production.

This is for you if your charity runs fundraising on plain Sales Cloud and you cannot say how a gift reached its donor, or which campaign gets the credit. Nonprofit Cloud itself is sold as Agentforce Nonprofit, formerly Nonprofit Cloud, since 2 December 2025.

Delivered on one of my projects, with the foundation’s own team. The foundation is not named and none of its donors, gifts or totals are published: a client’s money and records stay the client’s. Reviewed 7 November 2026.

What changed

What changed for the foundation?

Before: gifts paid without a phone number collected on one shared record, the website and the CRM disagreed, and the integration could report success for a gift that never arrived. Built: matching that ignores blanks, one integration path keyed on the order number, and a written attribution rule. Now: when the website changed its order format, some CRM fields stayed blank, so the order history was reloaded from the website, and each month in Salesforce then equalled the website’s order report.

01

Every month

covered by the reload matched, in each currency, the website’s own order report

02

0

duplicate gifts after the reload and after replaying the integration queue, counted by a query on the order number

03

19 of 19

attribution tests passed, run three times in each of two sandboxes before the change went to production

04

3 of 3

orgs carry the same donation flow: development, staging and production, so a fix tested in one is the fix that runs in the other two

Without a package

Can a charity run donations on Sales Cloud without NPSP?

Yes. This foundation does: donors are person accounts, gifts are opportunities, and a flow turns each website order into both. What a package would decide, you then own: donor matching, first gift dates, links between monthly payments, campaign credit, and which channels a report counts. Each needs a written rule and a test.

01

First gift dates are a rule you write

Here the condition compared product names that no order ever carried, so the dates were never written. It now reads the order’s status and gift type, and the history was filled from each donor’s earliest completed order, in the foundation’s own calendar day rather than GMT.

The duplicate donor

Why do gifts from different people end up on one donor record?

Because a blank value matched. The flow looked for a donor by phone or by email. An order without a phone became “phone is empty”, which matches any donor without a phone, and the flow took the first. The update step then copied the blank onto that donor, so it caught the next phoneless gift too.

01

A blank phone is normal, not rare

Wallet payments skip the website’s form, so those gifts arrive without a phone. A rule that breaks on blanks breaks every day.

02

Five formula guards in the flow

Two make a blank phone or email match nothing. Three stop a blank from overwriting a phone, email or first name the donor already has. Four test runs proved each path.

03

The gifts moved to the people who gave them

After a backup, each gift that belonged to someone else moved to the donor matched by its own email, and their first gift dates were recalculated.

The gift that never arrived

Why does the integration report success when the gift is missing?

Because the donation flow runs in the same transaction as the integration’s write. When the flow fails, Salesforce rolls back the request, the donor and the gift. The integration catches the error in its alert branch and marks the run successful. A green run proves the call was made; only the order number proves the gift exists.

01

Fix the cause, then replay the same run

One order failed for lack of a last name; the flow now falls back to the phone, the email, the first name, then the word Donor. After the fix reached all three orgs, the same run was replayed and the gift confirmed by its order number. A hand entry would leave the order and the CRM telling two stories.

Attribution

How do you keep the campaign that first brought a donor?

Write the rule before building it. Here the foundation’s team decided, for every gift from the change on: the donor keeps the first campaign, each gift keeps its own, and name, phone and email are never overwritten. A second phone or email goes to spare fields. The flow saves the donor’s original values before reading the new order.

01

Why the original values are saved first

The flow loads the order into the variable that holds the donor. Without a copy, “keep the first campaign” compares the order with itself.

The decisions that mattered

Which three decisions broke the obvious build?

Three decisions broke the obvious build: one integration scenario takes both order events, because two scenarios race and fail on the same order; the order number is the external ID, because the website never knows the Salesforce record ID; and the two donation channels stay apart, because mixed together they look like broken logic.

01

One integration scenario for every order event

The obvious build has one scenario for a new order and one for an update. The website sends both in the same second, and sequential processing keeps runs in order inside one scenario, not between two. Both inserted the same order and the second failed. One scenario now takes both events.

02

The order number as an external ID

Matching on the Salesforce record ID fails because the website never knows it. The order number became an external ID, unique in all three orgs, so a repeated event updates the same request. One trap: send the key among the fields as well and Salesforce rejects the call.

03

Two donation channels kept apart

Gifts from an international giving platform arrive by another route and have their own dashboard. Mixed into a website check, they look like gaps in the logic. Excluded by lead source, the first gift date check found no mismatch.

What charities ask first

What do charities ask before they start?

Q

Should we not just install NPSP or move to Nonprofit Cloud?

Perhaps, later. Donors here are already person accounts, which Nonprofit Cloud requires, while NPSP is built around household accounts. A move is a new implementation, and it carries the same matching and integration rules with it, broken or not. Repairing them where your gifts already live is the smaller first step, and it shows what a move would need to carry.

Q

Can one person safely work on a live org with real donations?

Every flow change was built in development, tested in staging and deployed to production inactive, then switched on, with the previous version named for rollback. Integration changes had no sandbox, so every reload started from a backup and every result was checked against the order number.

Q

What happens when you leave?

The attribution rule is written down with the foundation’s team, the tests are kept as scripts with the written rule, and the three orgs hold the same flow. Whoever comes next starts from a description and a test.

For your charity

Which parts carry over to another charity?

Any charity taking online gifts into plain Sales Cloud can ask five questions. Does a blank phone or email match a donor? Can a gift fail while the integration reports success? Is there a written rule for which campaign gets credit? Does each month equal the payment source? Are channels that arrive by different routes kept apart? The objects change from org to org; the questions do not.

The one working day check measures four things in your own org, read only, for €650 fixed: pipeline that is not real, accounts that share a web domain, logged emails and meetings per open opportunity, and the share held by the largest single lead source value. It does not count donors merged by a blank phone, because person accounts have no web domain, and it does not test an integration; the five questions above you can run yourself. If one lead source value holds most of your gifts, campaign credit is already unreadable. The fee is credited in full against any engagement booked within sixty days of delivery.

Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 7 November 2026.

Read next

01

NPSP vs Nonprofit Cloud: Must You Move?

Salesforce still supports NPSP, and its own guide treats the move to Nonprofit Cloud as a reimplementation in a new org. When staying is fine and when moving pays.

02

Salesforce Records Go Missing

Records never reach Salesforce and nothing alerts anyone, because the errors land where nobody looks. How to count them yourself.

03

CFO Does Not Trust the CRM Numbers

Marketing reports one figure, finance reports another, the board sees a third. More dashboards never fix it, because the disagreement is upstream.