DHIS2
UPGRADES

The challenge

National DHIS2 instances accumulate years of customizations — program stages, validation rules, dashboards, integrations — built up over multiple administrations and multiple versions of the platform. Upgrading isn't a routine update; it's a project where a missed breaking change can quietly corrupt reporting for an entire program.

Programs needed a path to newer DHIS2 versions without interrupting the reporting cycles that health teams depend on week to week.

The approach

I led national malaria programs through complex DHIS2 upgrades by treating each one as a structured migration rather than a simple version bump.

• Audited release notes for breaking changes against each instance's customizations
• Built staging environments to test upgrades before touching production
• Validated metadata, program rules, and dashboards post-upgrade
• Planned and executed phased deployment to minimize disruption

The outcome

Programs moved onto current, supported DHIS2 versions with no loss of historical data or reporting continuity — giving them access to newer platform features and security patches without the downtime or data risk that ad hoc upgrades typically carry.