A regional nonprofit switches IT providers without downtime

// the problem

Locked out of their own organization

The nonprofit — 28 staff plus a rotating volunteer pool, serving a multi-county region — had outgrown its IT provider years earlier, but switching felt riskier than staying. Support requests took days. Every fix arrived with an invoice nobody had approved. And when the executive director asked for the administrator credentials to their own systems, the answer was vague.

The trigger was a grant application that asked pointed questions about data security. Nobody could answer them, and the provider didn't reply for a week. The board approved finding a replacement.

// the approach

Thirty days of parallel running, then a quiet goodbye

Switching providers fails when it's treated as a cliff edge. Our onboarding runs alongside the incumbent instead. Week one, we documented everything independently — accounts, licenses, domains, backups, and the credentials situation, which we resolved through formal handover requests and, where those stalled, documented recovery through the platform vendors. The organization now holds its own keys, in a password vault it owns.

Week two fixed the urgent risks: MFA everywhere, offboarding of six former staff accounts that were still active, and verified backups of the donor database. Weeks three and four moved support to our helpdesk, ported vendor relationships, and — because eligibility had never been claimed — registered the organization for the Microsoft nonprofit program, replacing full-price licenses with granted and discounted ones worth roughly $9,000 a year.

Staff experienced the switch as an email announcing a new support contact. Nothing went down, because nothing was cut over until its replacement was already working.

// the outcome

What actually changed

• Zero downtime across the 30-day transition — verified against helpdesk and monitoring logs.
• About $9,000 a year in licensing costs removed through the Microsoft nonprofit program.
• Average ticket response went from days to our standard 14 minutes.
• The grant application's security questions got real answers, with documentation attached — and the grant came through.

The honest caveat: the licensing saving was possible because eligibility had never been claimed. An organization already on nonprofit programs would see the service improvements but not that particular number.