DEV Community: Maintask

[Boost]

Maintask — Wed, 17 Jun 2026 09:57:23 +0000

Maintask

Jun 17

Your Apex Might Return Fewer Records in Summer '26 — and Not Throw a Single Error

#ai #salesforce #apex #security

6 min read

Your Apex Might Return Fewer Records in Summer '26 — and Not Throw a Single Error

Maintask — Wed, 17 Jun 2026 09:57:09 +0000

If you maintain custom Apex on a Salesforce org, Summer '26 (API v67.0) ships a change that can quietly alter what your code returns — no exception, no failed deploy, just different results. It's a good change. It's also the kind of change that surprises a production org if nobody saw it coming.

Here's what's happening and how to get ahead of it.

Problem: Apex used to ignore the running user's permissions

For most of Apex's history, database operations ran in system mode by default. That means SOQL, SOSL, DML, and Database methods ignored the running user's:

object permissions,
field-level security (FLS), and
sharing rules.

A query in a controller would happily return records the logged-in user was never supposed to see, and write to fields they couldn't access — unless you explicitly added guards. In a nonprofit org, that's exactly how a volunteer with a restricted profile ends up able to read every donor's giving history through a custom Lightning component nobody pen-tested.

The platform gave us tools to opt into security (WITH SECURITY_ENFORCED, Security.stripInaccessible(), with sharing on classes), but they were opt-in. If you forgot, your code ran wide open. Secure was the thing you had to remember; insecure was the default.

Solution: Summer '26 flips the default to user mode

In API version 67.0, that default inverts. Database operations now run in user mode unless you explicitly say otherwise. Concretely, on v67.0:

SOQL / SOSL / DML / Database methods enforce the running user's object permissions, FLS, and sharing rules by default.
A class with no sharing declaration now defaults to with sharing (previously an omitted declaration effectively inherited the caller's mode — often without sharing).
WITH SECURITY_ENFORCED is removed and no longer compiles — you migrate to WITH USER_MODE.
Triggers always run in system mode and can't declare a sharing or access mode.

The important nuance: this is keyed to the API version of the Apex class. Existing classes stay on their current API version and behave as before until you bump them to 67.0. So this is a migration you control — not an overnight change forced on every line of code you own. New classes you create on 67.0 get the new behavior immediately.

You opt back into system mode explicitly, per operation, when you genuinely need it:

// SOQL — inline
List<Opportunity> gifts = [SELECT Id, Amount FROM Opportunity WITH USER_MODE];   // enforce user access (now the default)
List<Opportunity> all   = [SELECT Id, Amount FROM Opportunity WITH SYSTEM_MODE]; // intentional escape hatch

// DML
insert as user newGifts;     // respect the user's create/FLS
update as system staleRows;  // intentional system-mode write

// Database methods — pass the AccessLevel enum
List<Opportunity> dyn = Database.query(
    'SELECT Id, Amount FROM Opportunity',
    AccessLevel.SYSTEM_MODE
);
Database.insert(newGifts, AccessLevel.USER_MODE);

The mental model: user mode is the safe default; SYSTEM_MODE / without sharing is now the thing you write down on purpose, in the open, where a reviewer can see it.

Example: a donor-giving controller before and after

Say you have a Lightning component that shows a contact's giving history. Pre-v67, a common (and quietly unsafe) version looks like this:

// Pre-Summer '26 — no sharing declaration, system-mode query
public class DonorGivingController {
    @AuraEnabled(cacheable=true)
    public static List<Opportunity> getGifts(Id contactId) {
        // Runs in system mode: returns gifts regardless of who is asking,
        // and exposes Amount even if the user has no FLS on it.
        return [
            SELECT Id, Amount, CloseDate, StageName
            FROM Opportunity
            WHERE Primary_Contact__c = :contactId
        ];
    }
}

On v67.0, the same class — with no code changes — now behaves as with sharing in user mode. If a restricted user opens the component:

gifts on records they can't see via sharing are filtered out, and
if they lack FLS on Amount, the query throws instead of leaking the field.

That's the behavior you almost certainly wanted all along. The explicit, reviewer-friendly version makes the intent obvious:

// Summer '26 — intent is explicit and secure by default
public with sharing class DonorGivingController {
    @AuraEnabled(cacheable=true)
    public static List<Opportunity> getGifts(Id contactId) {
        return [
            SELECT Id, Amount, CloseDate, StageName
            FROM Opportunity
            WHERE Primary_Contact__c = :contactId
            WITH USER_MODE
        ];
    }
}

And when you do have a legitimate system job — a nightly rollup that must see every gift regardless of the running user — you say so, out loud:

public without sharing class NightlyGivingRollup implements Database.Batchable<SObject> {
    public Database.QueryLocator start(Database.BatchableContext bc) {
        return Database.getQueryLocator(
            'SELECT Id, Amount, Primary_Contact__c FROM Opportunity',
            AccessLevel.SYSTEM_MODE
        );
    }
    // ...
}

Pitfalls: what actually breaks, and how to catch it

The reason this deserves a real migration pass — not just a version bump — is that the failures are often silent. Here are the ones to watch.

1. Queries return fewer rows, with no error. A query that returned 500 records can return 40 once user access is enforced, and nothing throws. Downstream logic that assumed a full result set produces wrong numbers — bad rollups, missing list items, under-counted reports. To confirm a row drop is access-related, compare the two modes:

Integer asUser   = [SELECT COUNT() FROM Opportunity WITH USER_MODE];
Integer asSystem = [SELECT COUNT() FROM Opportunity WITH SYSTEM_MODE];
System.debug('user=' + asUser + '  system=' + asSystem);

A large gap means the running user simply can't see those rows — decide whether that's correct (it usually is) or whether this code is a true system context that needs SYSTEM_MODE.

2. WITH SECURITY_ENFORCED won't compile. If you bump a class to 67.0 and it still contains the old clause, deployment fails. Find-and-replace it with WITH USER_MODE, which is stricter (it also enforces sharing, not just FLS/object perms), so re-test afterward:

// Before (fails to compile on v67.0)
[SELECT Id, Name FROM Contact WITH SECURITY_ENFORCED];
// After
[SELECT Id, Name FROM Contact WITH USER_MODE];

3. Integration and automation users hit walls. This is the big one for nonprofits with connected apps (Click & Pledge, FormAssembly, ETL/data loads, scheduled jobs). Code that runs as an integration user and assumed system-level reach will now be filtered to that user's permissions. The fix is a deliberate choice per context: either grant the integration user the object/field/sharing access it legitimately needs, or mark the genuinely-system code paths without sharing + SYSTEM_MODE. Don't blanket-SYSTEM_MODE everything to make red tests green — that just recreates the old wide-open default you're trying to leave behind.

4. The sharing-declaration default flips. A class you relied on to run unrestricted (because an omitted declaration used to behave like without sharing in many call paths) may now enforce sharing as with sharing. Audit every class with no explicit declaration and write the intent down — with sharing or without sharing — so behavior no longer depends on who called it.

5. Triggers no longer enforce sharing. All triggers now run in system mode, period. If any logic quietly leaned on sharing being enforced inside a trigger, move it into a handler class that declares with sharing:

trigger OpportunityTrigger on Opportunity (after update) {
    new OpportunityTriggerHandler().afterUpdate(Trigger.new, Trigger.oldMap);
}

public with sharing class OpportunityTriggerHandler {
    public void afterUpdate(List<Opportunity> updated, Map<Id, Opportunity> oldMap) {
        // sharing is enforced here because the class declares it
    }
}

A pragmatic migration order

You don't have to do this all at once — the API version is per-class, so migrate deliberately:

Inventory first. Search your codebase for WITH SECURITY_ENFORCED (must change) and for classes with no sharing declaration (behavior may change).
Bump high-risk classes in a sandbox, one batch at a time: controllers, @AuraEnabled methods, REST endpoints, and anything an integration user runs.
Run your tests, but don't trust green alone — user-mode bugs are about data visibility, which weak test setups miss. Add tests that run as a restricted user via System.runAs().
Decide each escape hatch on purpose. Every SYSTEM_MODE / without sharing should be a conscious, commented decision, not a reflex to silence a failure.
Only then bump the API version in production, class group by class group.

Done this way, a change that could have been a silent production incident becomes a routine, secure-by-default upgrade — which is exactly what it's meant to be.

Five Salesforce Reports Every Nonprofit Leadership Team Should Have

Maintask — Mon, 25 May 2026 10:44:35 +0000

Nonprofit leadership teams often rely on Salesforce for fundraising, program tracking, grant management, and operational reporting.

But having the data in Salesforce is not the same as having useful reports.

A report is only valuable if it helps someone make a decision.

For nonprofit leaders, that usually means answering questions like:

Are we on track to meet our fundraising goal?
Which donors are at risk of lapsing?
Are our programs reaching the right people?
Which grant deadlines are coming up?
Can we trust the data in this dashboard?

This article walks through five Salesforce reports that can help nonprofit leadership teams make better decisions.

Problem

A nonprofit may have thousands of records in Salesforce. The data exists, but leadership still struggles to answer basic questions.

Common symptoms:

The board asks for a fundraising forecast, but only closed donations are reported.
Program impact numbers are pulled manually from spreadsheets.
Grant deadlines live in inboxes or individual calendars.
Lapsed donors are noticed months too late.
Dashboards look accurate, but the underlying data is incomplete.

The core problem is not usually Salesforce itself. The problem is that reports are often built around available fields instead of leadership decisions.

Solution

Build a small set of reports around the questions leadership asks most often. A practical nonprofit leadership reporting set should include:

Fundraising Pipeline Report
Donor Retention and Lapsed Donor Report
Program Impact Report
Grant Tracking and Compliance Report
Data Quality and Operational Health Report

Each report should have:

A clear owner
A clear audience
A clear business question
A defined update frequency
A next action when something looks wrong

The goal is not to create more reports. The goal is to create reports people actually trust.

Example 1: Fundraising Pipeline Report

What it answers

Are we likely to meet our fundraising target?

Many nonprofit teams report only on closed donations. That shows what already happened, but it does not show what is likely to happen next.

A pipeline report gives leadership visibility into expected revenue.

Useful fields

Opportunity Name
Donor or Account
Amount
Stage
Probability
Expected Close Date
Campaign
Owner
Next Step
Last Activity Date

Suggested grouping

Group by Stage
Then group by Expected Close Month

Why it matters

If many major gifts are stuck in “Proposal Sent”, the issue may not be the fundraising strategy. It may be the follow-up.

If several grants are expected to close this quarter but have no next step, leadership can act before the forecast becomes a surprise.

Simple report logic

Object: Opportunities
Filter:
  IsClosed = False
  Amount > 0
  CloseDate = Current Fiscal Year

Group:
  Stage
  Close Month

Show:
  Sum of Amount
  Sum of Expected Revenue

Example 2: Donor Retention and Lapsed Donor Report

What it answers

Which donors are at risk of disappearing?

A donor may not actively cancel or complain. They may simply stop giving.

That makes retention reporting important, especially for recurring donors and major donors.

Useful fields

Donor Name
Last Gift Date
Last Gift Amount
Total Giving
Current Year Giving
Previous Year Giving
Giving Frequency
Recurring Donation Status
Last Activity Date
Owner or Relationship Manager

Simple report logic

Object: Contacts or Accounts with Opportunities

Filter:
  Previous Year Giving > 0
  Current Year Giving = 0

Optional:
  Last Activity Date older than 90 days

Why it matters

This report turns donor retention into an operational process.

Instead of asking “Why is donor retention down?” leadership can ask:

Which donors need follow-up?
Who owns the relationship?
What action should happen next?

Example 3: Program Impact Report

What it answers

What work are we delivering, and what outcomes are we seeing?

Fundraising reports show how money comes in. Program impact reports show what that money supports.

For nonprofits, this is often the report leadership needs for board updates, grant reporting, and strategic planning.

Useful fields

Program Name
Participant or Beneficiary
Service Type
Service Date
Status
Outcome
Location
Funding Source
Owner
Completion Date

Useful metrics

Participants served
Programs completed
Open cases or active enrollments
Completion rate
Outcome achievement rate
Services delivered by location
Demand by program area

Simple report logic

Object: Program Participation or Custom Program Object

Filter:
  Service Date = Current Fiscal Year

Group:
  Program Name
  Status
  Outcome

Show:
  Record Count
  Completion Rate

Why it matters

Counting records is not enough. A useful impact report should separate:

Started
In progress
Completed
Dropped
Outcome achieved
Outcome not achieved

This prevents teams from reporting activity as impact.

Example 4: Grant Tracking and Compliance Report

What it answers

What grant deadlines, deliverables, or reports are at risk?

Grant tracking often breaks when key information lives outside Salesforce.

Common places where grant details get lost:

Email threads
Individual calendars
Spreadsheets
PDF award letters
Staff memory

A Salesforce grant tracking report creates a shared source of visibility.

Useful fields

Grant Name
Funder
Amount Requested
Amount Awarded
Stage
Application Deadline
Award Date
Reporting Deadline
Restricted Purpose
Program Funded
Responsible Owner
Deliverable Status
Next Step

Simple report logic

Object: Grants or Opportunities

Filter:
  Grant Status = Active
  Reporting Deadline = Next 90 Days

Group:
  Reporting Deadline Month
  Responsible Owner

Show:
  Grant Amount
  Deliverable Status

Why it matters

This report reduces reliance on memory. Leadership can see what is due, who owns it, and where risk is building before a deadline is missed.

Example 5: Data Quality and Operational Health Report

What it answers

Can we trust the data behind the dashboard?

This report is usually less exciting than fundraising or impact reporting, but it is also one of the most important.

If Salesforce data is incomplete or inconsistent, every dashboard built on top of it becomes questionable.

Simple report logic

Object: Contacts

Filter:
  Email = Blank
  Created Date = Last 30 Days

Group:
  Created By
  Owner

Show:
  Record Count

Another example:

Object: Opportunities

Filter:
  Campaign = Blank
  Close Date = Current Fiscal Year

Group:
  Owner
  Stage

Why it matters

Data quality reporting helps teams identify process issues.

For example:

If many gifts are missing campaigns, the donation entry process may need adjustment.
If many contacts are missing emails, form mapping may be incomplete.

This report should not be used to blame users.

It should be used to improve the system.

Pitfalls

Pitfall 1: Creating too many reports

Leadership does not need 80 reports.

They need a small number of reports that answer important questions.

Too many reports often create confusion because different teams may use different filters, definitions, or date ranges.

Pitfall 2: Reporting on fields no one updates

A dashboard is only as reliable as the fields behind it.

If “Stage”, “Status”, “Outcome”, or “Next Step” fields are not maintained consistently, leadership reports will become unreliable.

Pitfall 3: Confusing activity with impact

For program reporting, avoid treating every record count as an outcome.

For example:

“1,000 participants registered” is not the same as “1,000 participants completed the program”.

The report should make that distinction clear.

Pitfall 4: Building dashboards before fixing data quality

Dashboards can make bad data look official.

Before relying on dashboards, build data quality reports that show whether key fields are complete and consistent.

Practical Checklist

Before publishing a Salesforce leadership report, confirm:

Does this report answer a leadership question?
Is the audience clear?
Are field definitions consistent?
Is there a known action when numbers look wrong?
Can users trust the underlying data?
Should this be part of a dashboard?

Final Thought

Good Salesforce reporting is not about having more dashboards.

It is about creating a small set of reports that leadership can trust.

For many nonprofits, these five reports are a strong starting point:

Fundraising Pipeline
Donor Retention
Program Impact
Grant Tracking
Data Quality

Once those are in place, board meetings become less about reconciling numbers and more about making decisions.

Reporting Failure Patterns We Keep Seeing in Nonprofit Salesforce Orgs

Maintask — Mon, 04 May 2026 15:20:17 +0000

If you have ever inherited a nonprofit Salesforce org with eighty reports, three dashboards, and zero confidence in any of them, you already know the real problem: the report is usually not broken. The reporting design is.

Most of the time, the bad number on the dashboard is just the last visible symptom. The real issue sits deeper: no one agreed on stage definitions, recurring-donation exceptions are mixed into retention reporting, programme counts are based on row volume instead of unique participants, or critical grant deadlines still live in someone's calendar.

This post is not a list of "reports leaders should have." It is a list of the reporting patterns that keep making leadership stop trusting the CRM in the first place.

A quick note before the examples: names ending in __c indicate custom objects or custom fields — adapt those names to your own org. In NPSP and nonprofit orgs generally, package fields and custom models vary, and Salesforce recommends checking the actual object schema in the target org before hard-coding anything.

Pattern 1 — Stale pipeline disguised as forecast

When someone asks, "what is likely to close this quarter?", they are not asking for a sum of every open opportunity in the system. They are asking for a forecast that excludes deals nobody has touched in weeks.

The first fix is to separate forecast reporting from stale-opportunity cleanup. For a quarter view, use a grouped query or report that looks at stage and close-date timing together.

SELECT StageName, CALENDAR_MONTH(CloseDate), COUNT(Id), SUM(Amount)
FROM Opportunity
WHERE IsClosed = FALSE
  AND CloseDate = THIS_QUARTER
GROUP BY StageName, CALENDAR_MONTH(CloseDate)

Then pair it with a stale-opportunity view:

SELECT Id, Name, Amount, StageName, CloseDate, OwnerId, LastActivityDate
FROM Opportunity
WHERE IsClosed = FALSE
  AND CloseDate = THIS_QUARTER
  AND (LastActivityDate = NULL OR LastActivityDate < LAST_N_DAYS:60)
ORDER BY CloseDate ASC

COUNT_DISTINCT, date grouping functions like CALENDAR_MONTH(), and relative date literals in WHERE clauses are all documented parts of SOQL, so this pattern is technically sound. The pitfall is not the query. It is trying to "clean the pipeline" before the team has written down what each stage actually means. Skip that conversation, and the team will move records around for weeks while quietly redefining the stages on the next call.

Pattern 2 — Recurring revenue drift hiding inside donor retention

In NPSP, recurring donations are their own object, and Salesforce distinguishes between open-ended and fixed-length recurring gifts. That matters because "lapsed donor" and "recurring gift stopped processing" are not the same operational problem — and if the org also relies on soft credits to attribute gifts to multiple contacts, the reporting layer gets messier still (more on that pattern here).

Merging the two into a single report usually produces a noisy list nobody owns. The cleaner approach is to split it into two views:

a classic retention report for donors who gave in the previous period but not the current one
a recurring-donation exception report for open recurring gifts with no recent successful payment or no expected next-payment movement

The exact field names depend on the org, the NPSP version, and whether the team is on classic NPSP or has moved to the newer Nonprofit Cloud product line — which Salesforce has been increasingly pushing as the primary path for new implementations. Official NPSP source code confirms package fields such as npe03__Amount__c, npe03__Contact__c, and npe03__Open_Ended_Status__c, but reporting should stay field-agnostic until the exact schema in the target org is confirmed. A field name that fails on day one undermines the whole report — and the trust attached to it.

Pattern 3 — Participant numbers inflated by reporting design

This one shows up constantly: a team says it served 1,200 participants, but the report is really counting enrolment rows, not people. Duplicates, dropouts, reopened cases, and migration artefacts quietly inflate the number.

The fastest fix is to stop treating raw row count as impact. In Salesforce reports, unique count on a column and row-level formulas (or other report formulas) handle per-record logic — the supported way to do "completed vs dropped vs active" style analysis inside reporting.

If the org uses a custom enrolment object, the aggregate logic can be simple:

SELECT Program__c, COUNT_DISTINCT(Contact__c)
FROM Program_Enrollment__c
WHERE Enrollment_Date__c = THIS_FISCAL_YEAR
GROUP BY Program__c

What should not be published as runnable SOQL is SQL-style SUM(CASE WHEN ...). Salesforce's documented SOQL syntax does not include standard CASE expressions, so conditional completed/dropped metrics belong in report formulas, formula fields, or separate grouped reports. The query above gives unique participants per programme; everything beyond that — completed, dropped, in-progress — belongs in the reporting layer or a custom formula field, not in the SOQL itself.

The pitfall here is not technical. It is that the program team has to commit to a written definition of "completed." Otherwise the report gets rebuilt three times in six months as definitions drift.

Pattern 4 — Grant obligations stored outside the CRM

A grant can be in Salesforce and still be operationally unsafe if the reporting obligations live in email or in one person's calendar. The opportunity exists, but the actual compliance work is invisible.

This is where a separate obligation model works better. Not because Salesforce ships a standard Grant_Obligation__c object — it does not; names ending in __c indicate a custom object — but because the reporting requirement is operationally different from the revenue record.

A simple custom object pattern is enough:

Grant_Obligation__c
- Grant__c           (Lookup -> Opportunity)
- Obligation_Type__c (Picklist: Interim Report, Final Report, Deliverable, Compliance Doc)
- Due_Date__c        (Date, required)
- OwnerId            (User, required)
- Status__c          (Picklist: Not Started, In Progress, Submitted, Late)
- Days_Until_Due__c  (Formula: Due_Date__c - TODAY())

A single dashboard component over Status__c != 'Submitted' and Days_Until_Due__c <= 60, grouped by owner, gives leadership a clean early-warning view.

The mistake that keeps showing up here is trying to auto-generate every obligation from the grant itself. In real organisations, grant requirements vary too much, and the auto-generated records will be wrong often enough that the grant manager will quietly stop trusting them — and go back to the inbox. A manual but mandatory creation step is usually more reliable than a clever automation nobody believes.

Pattern 5 — Dashboards without a health layer

Every leadership dashboard depends on an assumption about the data underneath it. If duplicates are rising, campaign attribution is patchy, or overdue tasks are piling up, the dashboard can look polished while the organisation slowly loses trust in it.

A small admin-facing "org health" dashboard sitting next to the executive one solves this. It does not need to be fancy — and in long-running admin engagements that function as a nonprofit's internal Salesforce team, this is one of the first things to set up. The cost is low, the trust dividend is enormous.

The dashboard just needs to answer questions like:

how many duplicate contacts are being carried?
how many won opportunities are missing campaign attribution?
how many donor records are missing critical contact data?
where are overdue operational tasks accumulating?

Each component should have an explicit target — duplicates < 2%, missing campaign attribution < 5% — so that "good" and "bad" stop being subjective.

The pitfall here is cultural, not technical. The moment a data-quality dashboard gets framed as a tool for blaming staff, the data quietly gets worse. People stop logging things honestly. Frame it as a process indicator instead: "if duplicates are climbing, the intake form needs revisiting," not "Sarah created twelve duplicates last month." The goal is traceability, not accountability theatre.

The pattern behind the patterns

Trace all five back and they share one thing: the report was built around the fields that were available, not around the decision somebody needed to make.

That is the underlying technical debt in most nonprofit Salesforce orgs. It is not the schema, it is not the automation, it is not the integration — it is the gap between "what data do we have?" and "what decision needs to be made?"

Closing that gap is mostly a scoping skill, not a Salesforce skill. The five patterns above are just the most common places it shows up.

Avoiding the “$100K Spreadsheet” Trap in Nonprofit Salesforce Projects

Maintask — Mon, 23 Feb 2026 15:37:29 +0000

Salesforce projects in nonprofits rarely fail because of the platform.

They fail because unclear processes, inconsistent definitions, and messy data get automated instead of resolved.

When that happens, Salesforce becomes what many teams privately call it: "A very expensive spreadsheet."

This post breaks down why that happens and how to avoid it from an implementation perspective.

Problem: Automating Without Structural Clarity

Nonprofits typically move to Salesforce when operational complexity increases. More donors. More grants. More reporting pressure. More cross-team collaboration.

Spreadsheets stop scaling. Manual reconciliation becomes painful. Leadership loses visibility.

The problem is not the decision to adopt Salesforce. The problem is how the implementation starts.

Many projects begin with configuration:

Creating custom objects
Building automation flows
Designing dashboards
Importing legacy data

But the foundational questions are often unresolved:

What exactly qualifies as a "major donor"?
When is a fundraising opportunity officially "closed won"?
How are grant stages defined?
What metrics matter to the board?
Who owns data quality?

If these definitions vary across teams, automation will only make inconsistencies permanent.

Technology scales whatever it is given — clarity or confusion.

Solution: Sequence Matters More Than Features

A stable Salesforce implementation in a nonprofit context follows a predictable sequence. It is less about technical complexity and more about order of operations.

Step 1: Define Outcomes Before Building Objects

Before touching configuration, define success.

What decisions need better visibility?
What reporting gaps currently exist?
What operational friction are you trying to reduce?

If leadership cannot articulate the outcomes, dashboards will not fix that later.

Salesforce is a system of record. It should reflect decisions, not create them.

Step 2: Standardize Process Definitions

Most CRM inconsistencies are semantic.

If one fundraiser marks a donor as "major" at $5,000 and another at $25,000, segmentation breaks immediately. If grant tracking stages differ across departments, reporting becomes unreliable.

Before building automation, document and align on:

Fundraising lifecycle stages
Opportunity definitions
Program tracking structure
Grant state transitions

This alignment reduces downstream rework significantly.

Step 3: Treat Data Migration as a Data Project

Legacy nonprofit databases often contain:

Duplicate records (sometimes 20–30%)
Inconsistent formatting
Missing emails
Partial donation histories

If this data is imported without cleansing, Salesforce will reflect those flaws at scale.

User trust erodes quickly when reports do not match expectations.

Clean data is not a cosmetic improvement. It is a prerequisite for adoption.

Step 4: Resist Early Over-Customization

Nonprofit Cloud includes a strong baseline architecture — household data model, campaign tracking, standard opportunity handling, and built-in reporting.

It is tempting to customize everything to replicate legacy workflows. But over-customization introduces:

Technical debt
Upgrade friction
Increased admin burden
Dependency on one "system expert."

Start with standard functionality. Customize only when process requirements truly demand it.

Example: Two Implementation Paths

Consider two mid-sized nonprofits implementing Salesforce.

Path A: Configuration-First

The organization imports 50,000 records without deduplication. Each department keeps its own opportunity definitions. Custom objects are created to match historical spreadsheets. Dashboards are built late in the process.

Two months later:

Segmentation produces inconsistent counts
Grant reporting requires manual adjustment
Leadership questions data accuracy
Admin workload increases

The platform functions technically, but it does not create operational clarity.

Path B: Process-First

Before configuration begins:

Fundraising stages are standardized
Grant lifecycle definitions are aligned
Duplicate records are reduced
Reporting requirements are mapped
Governance ownership is assigned

Configuration then reflects those agreements.

Result: reliable dashboards, higher adoption, lower long-term maintenance, reduced reporting friction.

Same platform. Different discipline.

Pitfalls to Avoid

Most nonprofit Salesforce failures share similar patterns:

Treating CRM implementation as an IT task instead of an organizational alignment exercise
Importing legacy data without validation or deduplication
Allowing uncontrolled field creation post go-live
Building automation before definitions are finalized
Skipping governance planning

None of these are technical limitation. There are sequencing issues.

Summary

Salesforce does not inherently create clarity. It scales it.

If your nonprofit has agreed-upon definitions, clean and structured data, documented processes, and clear governance ownership, Salesforce becomes a strategic asset.

If not, it becomes a powerful system delivering spreadsheet-level value.

The difference is rarely about advanced automation or complex architecture. It is about implementation order and organizational alignment.

DEV Community: Maintask

[Boost]

Your Apex Might Return Fewer Records in Summer '26 — and Not Throw a Single Error

Your Apex Might Return Fewer Records in Summer '26 — and Not Throw a Single Error

Problem: Apex used to ignore the running user's permissions

Solution: Summer '26 flips the default to user mode

Example: a donor-giving controller before and after

Pitfalls: what actually breaks, and how to catch it

A pragmatic migration order

Further reading

Five Salesforce Reports Every Nonprofit Leadership Team Should Have

Problem

Solution

Example 1: Fundraising Pipeline Report

What it answers

Useful fields

Suggested grouping

Why it matters

Simple report logic

Example 2: Donor Retention and Lapsed Donor Report

What it answers

Useful fields

Simple report logic

Why it matters

Example 3: Program Impact Report

What it answers

Useful fields

Useful metrics

Simple report logic

Why it matters

Example 4: Grant Tracking and Compliance Report

What it answers

Useful fields

Simple report logic

Why it matters

Example 5: Data Quality and Operational Health Report

What it answers

Simple report logic

Why it matters

Pitfalls

Pitfall 1: Creating too many reports

Pitfall 2: Reporting on fields no one updates

Pitfall 3: Confusing activity with impact

Pitfall 4: Building dashboards before fixing data quality

Practical Checklist

Further Reading

Final Thought

Reporting Failure Patterns We Keep Seeing in Nonprofit Salesforce Orgs

Pattern 1 — Stale pipeline disguised as forecast

Pattern 2 — Recurring revenue drift hiding inside donor retention

Pattern 3 — Participant numbers inflated by reporting design

Pattern 4 — Grant obligations stored outside the CRM

Pattern 5 — Dashboards without a health layer

The pattern behind the patterns

Further reading

Avoiding the “$100K Spreadsheet” Trap in Nonprofit Salesforce Projects

Problem: Automating Without Structural Clarity

Solution: Sequence Matters More Than Features

Step 1: Define Outcomes Before Building Objects

Step 2: Standardize Process Definitions

Step 3: Treat Data Migration as a Data Project

Step 4: Resist Early Over-Customization

Example: Two Implementation Paths

Pitfalls to Avoid

Summary

Further Reading