There is a particular kind of bureaucratic magic that almost nobody notices when it works, and that magic just happened in Ethiopia!
In June 2026, at the Adwa Memorial Museum in Addis Ababa, the Ethiopian government launched something with a name that sounds more like a proverb than a policy: MAKATET (ማካተት), which translates roughly to "inclusion." Behind the ceremony and the speeches sat an impressive achievement: the government had just finished merging two entirely separate child protection system into one. If that doesn't sound thrilling, stay with it. Because what got merged, and why, is a story about what it actually takes to make "inclusion" more than a word on a banner.
The Problem with Two Systems
For years, Ethiopia ran its Child Protection Information Management System, known as CPIMS+ Primero, on two parallel platforms. One version served host communities: Ethiopian children navigating abuse, neglect, family separation, or other protection concerns. The other served refugee children, tracked separately through the Refugees and Returnees Service (RRS) in coordination with UNHCR.
Two systems. Two Primero environments. Two sets of case workers, potentially looking at two different pictures of the same community, sometimes even the same family.
Anyone who has worked in social services knows what that produces: duplicated intake interviews, cases that fall through administrative cracks, and a refugee child who, the moment their status shifts, or their family moves, or a case worker changes, effectively becomes invisible to one of the two systems tracking them. Data silos are never just an IT inconvenience. In child protection, they can mean a follow-up visit that never happens.
The Numbers Behind the Merger
The scale of what Ethiopia's caseworkers are managing makes the case for unification almost self-evident. The newly consolidated national dashboard shows the platform now holding 41,650 total cases.
That's not a small pilot project. That's a live, national-scale system now serving all of Ethiopia through two integrated platform instances, accessed by 1,430 registered users across 24 partner agencies from government ministries, UN agencies, and NGOs, all now reading from the same page instead of comparing notes across two disconnected systems.
Under the old structure of two platforms, some fraction of the work risked being duplicated, delayed, or simply lost between platforms. Under the new one consolidated platform, it's data that is coordinated, protected, and visible to the people who need to see it.
"One child, one case, one system: Ethiopia's CPIMS+ integration is turning inclusion from a policy aspiration into a daily reality for thousands of children."
What Actually Made the Merger Work
Technical integrations fail all the time, not because the code doesn't work, but because politics, trust, and the incentives around the code don't align. So, what made this one succeed?
First, a roadmap gave the merger a mandate, not just a use case. The MAKATET Roadmap reframed refugee support in Ethiopia from short-term humanitarian relief toward long-term, government-owned socio-economic inclusion. That reframing mattered enormously for the CPIMS+ merger: it turned a technical data-migration project into the flagship proof that MAKATET's philosophy could actually be implemented, not just declared. When a system upgrade becomes the evidence for a national strategy, it gets the political air cover and the resources that ordinary IT projects rarely receive.
Second, the right coalition sat at the same table. No single institution could have pulled this off. The Ministry of Women and Social Affairs brought national child-protection authority. The Refugees and Returnees Service brought the refugee case data and institutional memory. UNICEF and UNHCR brought technical standards and global child-protection expertise. Plan International Ethiopia brought field implementation muscle. And the Primero Global Team, the technical backbone behind CPIMS+ platforms worldwide, brought the software architecture that made "merge two live databases without losing a single child's history" technically achievable rather than aspirational. A joint technical team, rather than a single leading agency working in isolation, meant the merger had to satisfy everyone's operational needs from day one, which is exactly why it stuck.
Third, access control did the trust-building, quietly. One of the least visible but most important outcomes of harmonization was the introduction of enhanced role-based access controls and strengthened data protection mechanisms. This is the unglamorous engineering that lets a merger like this happen at all: agencies were willing to pool sensitive child protection data into a shared platform because the system could guarantee that a caseworker in one region, or one agency, only sees what they are authorized to see. Without that guardrail, no ministry or UN agency would have agreed to share its data pool in the first place. Trust, in digital systems, is built through permissions, not promises.
Fourth, it was designed for inclusion, not just consolidation. Rather than simply bolting refugee data onto the existing host-community system, the new platform incorporated customized configurations specifically built to support refugee inclusion in national services. That distinction matters: a lazy merger would have forced refugee case data to awkwardly conform to systems never designed for it. This one built the accommodation in from the start, which is the entire point of "inclusion" as a design principle rather than a talking point.
©UNICEF/UNI788638/Tesfaye
"Inclusion is not just about services. It is about ensuring every child remains visible, protected, and supported in one connected system."
Why This Is Bigger Than an IT Story
It's tempting to file this under "government upgrades database." But zoom out, and the CPIMS+ integration is a working model for something the humanitarian sector talks about constantly and rarely delivers durable, government-led systems that treat refugee and host-community children as part of one protective net rather than two.
With nationwide field rollout now underway, the real test begins, whether a case worker experiences a child's case file as complete, current, and connected, regardless of that child's legal status. The dashboard numbers suggest the system is already handling scale. The harder, more human work, making sure every one of the 41,650 child gets the follow-up they need, is what MAKATET was always really about.
Ethiopia didn't just merge two systems. It made a quiet promise to every child behind those 41,650-plus case files: your protection doesn't depend on which side of a border you were born on.