Data 360, formerly called Salesforce Data Cloud, isn’t just another object model or add‑on. It doesn’t behave like core Salesforce data, and it doesn’t solve problems on its own. What it does offer nonprofits, when implemented well, is something they’ve struggled to achieve for years: a genuinely unified view of people, activity, and engagement across systems. 

That promise is real—but it depends entirely on foundation, clarity, and intent.

What makes Data 360 different 

One of the most important things to understand about Data 360 is that it doesn’t replace your existing Salesforce data model. It sits alongside it. It sits alongside it. 

The platform is designed to ingest data from multiple sources, apply unification rules, and resolve those records into a single, persistent identity behind the scenes. Sources are frequently multiple Salesforce instances, cloud storage, and marketing platforms. When it works well, users don’t see the complexity. They see one person, one organization, one history—regardless of how many systems originally contributed data. 

In practice, that means records, while still stored separately in their own systems—an alum record here, a donor record there, an event attendee somewhere else—can be recognized as the same individual through defined matching logic. A set of unification rules does the heavy lifting in the background, allowing Salesforce to present a cleaner, more trustworthy picture in the foreground. 

For nonprofits that have lived with duplication and fragmentation for decades, this is a meaningful shift. 

Foundation matters more than features 

Data 360 becomes easier to understand once you’re inside it—but getting there requires preparation. Firstly, you need to understand your data model. Working with Data 360 requires you to know what your systems contain, how fields relate to one another, and where the truth actually resides. Without that clarity, unification becomes guesswork, and guesswork at scale is risky. 

This is why it projects succeed or fail long before configuration begins. The hard work is not technical wizardry. It’s the data governance decisions, and agreement on what should and should not be brought into Data 360. 

For nonprofits, this often means answering difficult questions upfront: Which systems are authoritative? What data is good enough to unify? Where are the gaps we should acknowledge instead of masking? 

Moving from analysis to action 

Salesforce often describes Data 360 in phases—analyze and act among them—but what matters most for nonprofits is what comes after unification. 

Once data is unified, it becomes far more usable. Engagement patterns are easier to see. Relationships are clearer. Downstream tools—reporting, segmentation, automation, and eventually AI—have a more reliable foundation to work from. 

But it does not make those decisions for you. It creates the conditions where acting on data becomes possible, not inevitable. 

This is where intentional design matters. Unified data should serve a purpose, whether that’s improving donor experience, supporting fundraising strategy, or reducing internal friction. Without a clear use case, Data 360 risks becoming an impressive but underused asset. 

Enablement and learning are part of the work 

Data 360 is not something teams “set and forget.” Salesforce continues to evolve it, rename it, and expand its capabilities. Keeping up requires active learning. 

Salesforce provides extensive enablement resources, from Trailhead to communities, Slack channels, office hours, and planning documentation. These resources exist for a reason: Data 360 touches architecture, data governance, and long‑term strategy, not just configuration.

Heller Consulting invests in this enablement so our teams can help nonprofits navigate Data 360 with confidence—not just implement it, but explain it, test it, and adapt it as needs evolve. 

How we help nonprofits approach their data responsibly 

We don’t start Data 360 conversations with technology. We start with readiness. 

That means helping nonprofits understand their current data landscape, clarifying goals, and determining whether Data 360 is the right next step—or whether foundational work should come first. In many cases, that foundational work is what makes the cloud viable later. 

When nonprofits are ready, we help design unification logic that reflects reality, not wishful thinking. We support testing and documentation, so organizations understand how their data is being resolved. And we help teams connect unified data back to real outcomes, rather than treating Data 360 as an abstract platform investment. 

Most importantly, we stay grounded. The platform is powerful, but it is not magical. Its value comes from thoughtful planning, strong data practices, and a clear sense of purpose. 

A practical step forward 

For nonprofits that have struggled with fragmented data, Data 360 represents a real opportunity—but only if approached with care. 

With the right foundation, the right partners, and the right expectations, Data 360 can help organizations finally see their constituents more clearly and act more intentionally. That’s not about chasing the newest Salesforce feature. It’s about building data confidence that lasts. 

Heller Consulting helps nonprofits do exactly that—one carefully and well‑designed step at a time. 

The post How nonprofits can put the Salesforce data cloud to work appeared first on Heller Consulting.

So you’re preparing for a new CRM but suddenly you realize your data is a bit messier than expected—welcome to the club. We see this all the time. A new system rollout often shines a light on long-standing data issues, and deduplication becomes a top priority.

Salesforce gives you a decent starting point with four standard Matching and Duplicate Rules—for Accounts, Person Accounts, Contacts, and Leads. But if you’ve worked in a nonprofit or higher ed environment, you already know: “standard” rarely fits your reality.

Where Salesforce defaults help—and where they don’t

Salesforce’s native deduplication tools are helpful, but they’re not comprehensive. For example, you can’t create Matching Rules for Cases or Products yet (yes, we’re watching those IdeaExchange threads too). And while you can build Matching Rules on custom objects, there are still limitations—especially when it comes to cross-field matching or automating merges.

For organizations with tight budgets, third-party tools can feel out of reach. But when you’re managing thousands (or millions) of records, the cost of bad data can be even higher.

Tailoring deduplication to your org

Every implementation we do at Heller is different. We’ve worked with clients who track multiple email or phone types—personal, business, other—and need custom Matching Rules to reflect that. A typical rule might look like:

“`

(Contact: Personal_EmailExactMatchBlank = FALSE) OR

(Contact: Business_EmailExactMatchBlank = FALSE) OR

(Contact: Other_EmailExactMatchBlank = FALSE)

“`

We often help clients implement “Never Merge” logic—Boolean fields that flag a record as the one that should always win in a merge, or relationship objects that prevent certain records from being merged at all. The Relationship object is an example where a “Never Merge” field indicator could signify two records that should never be merged (ie: two Contacts with the same name). The object alone doesn’t prevent the merge nor does it exist for the purpose of deduplication.

We have also built “External System ID” custom objects, so clients don’t have to fear losing important IDs through a merge. Typically, these data points live flat on the Contact or Account record, and would therefore be deleted during the merge.

These are small tweaks that make a big difference in preserving data integrity.

Choosing the right dedupe tool

We regularly evaluate deduplication tools and provide clients with tailored fit and gap scoring matrices. Heller’s evaluations are a great guide that clients can bring into vendor demos to ensure the right questions are being asked and addressed.

Here’s a quick rundown of four tools we often recommend:

DemandTools

Great for large datasets and power users. It’s partially cloud-based but requires a local install for full functionality. Modules like Dedupe, Import, Modify, Tune, and Schedule are especially popular. Find out more about Validity’s DemandTools.

Cloudingo

Fully cloud-based and easy to configure. It offers real-time merging, address validation, and an import tool that checks for duplicates before they hit your CRM. More on Cloudingo.

DataGroomr

Uses machine learning to identify duplicates and improve over time. It’s scalable, intuitive, and integrates directly with Salesforce. DataGroomr basics.

Duplicate Check

Embedded within Salesforce, making it accessible to a broader range of users. It supports both small and large data volumes and offers flexible processing options.

Let your data strategy govern your dedupe approach

Deduplication isn’t just a checkbox—it’s a strategy. Clean data supports better engagement, smarter decisions, and smoother operations. Whether you’re using Salesforce’s standard tools or investing in a third-party solution, the key is to align your approach with your organization’s unique needs.

And if you’re feeling overwhelmed, don’t worry. We’ve seen it all—from tangled custom fields to merge logic gone sideways—and we’re here to help you navigate it.

The post Deduplication best practices for nonprofits appeared first on Heller Consulting.