Most data strategy advice assumes you chose your systems.
For a lot of nonprofits, that's not true. Your CRM was required by a federal grant. Your program tracking database came bundled with a foundation's capacity building award. Your outcomes platform was mandated by a government contract that funds 40% of your budget.
You didn't pick these tools. You inherited them. And now you're running three or four or fourteen systems that don't talk to each other, track different things in different ways, and leave you unable to answer basic questions about your own organization.
This is one of the most common and least-discussed data problems in the nonprofit sector. Here's how to think about it.
Why funder-driven systems create fragmentation
Funders choose databases for their own reasons. They want data in a format they can aggregate across their grantees. They've negotiated a discount with a vendor. They need specific fields tracked for their own reporting. Their choice makes sense for them.
The problem is that what matters to a funder is not the same as what matters to your organization. A housing funder cares about housing outcomes. A workforce funder cares about employment outcomes. Neither of them cares about the cross-program view that would tell you how many people you served in total, which clients used multiple programs, or whether your services are reaching the populations your strategic plan prioritizes.
So you end up with data that answers the funder's questions and nobody else's.
Three ways organizations handle this
Accept the fragmentation and work around it. Most organizations do this by default. Staff maintain separate systems, pull reports manually before board meetings, and reconcile numbers in spreadsheets before grant reports go out. It works, in the sense that nothing catastrophically fails. But it costs staff time constantly and leaves the organization without a reliable picture of its own work.
Build a lightweight layer you control. Rather than trying to replace funder systems, add a thin central layer alongside them. A shared intake form that every program uses at first contact. A simple database that captures core fields: name, date of birth, contact information, program enrollment, before data splits into funder systems. This doesn't eliminate fragmentation, but it gives you a foundation for answering cross-program questions. The funder systems handle funder reporting. Your layer handles organizational understanding.
Negotiate with funders. More possible than most organizations realize. Many funders are open to conversation about data requirements, especially if you can articulate what you need and why. If a required platform is genuinely creating operational burden, that's worth raising. Some funders will allow you to track the required fields in your own system and export them in the format they need. Others have moved toward outcomes-based reporting that gives you more flexibility in how you collect and store data. Worth asking.
What you actually control
Even when you can't change the systems, you control the intake process. You control what happens before someone enters a funder's database.
A shared intake layer, even a simple one, is where this problem gets solved. By capturing what you need before data splits, not by replacing funder systems.
The minimum viable version looks like this: a consistent intake process that every program uses, capturing name, date of birth, a unique identifier, and whatever cross-program fields matter to your organization. Stored somewhere you own. Updated consistently.
From there, program staff enter whatever the funder requires into whatever system the funder requires. But your organization has its own record, in its own format, answering its own questions.
The governance piece
Technology is the easy part. The hard part is getting every program to use the same intake process, define terms the same way, and maintain consistency over time.
That requires decisions: what fields matter to us, how we define them, who's responsible for maintaining them. And it requires someone with the authority to hold the organization to those decisions, not just at the start, but every time a new funder adds a new requirement, every time a staff member finds a shortcut, every time it feels easier to just enter something slightly differently.
Funder-driven fragmentation is a structural problem. A lightweight shared layer with real governance is the practical solution. Not a complete fix, but enough to give your organization the data it needs to understand its own work.
Download the free Nonprofit Data Health Checklist
Joshua Barillas is the founder of Prismatic Consulting, a data services firm built exclusively for nonprofits. Learn more about our services or get in touch at hello@prismaticconsulting.us.