Out of the Data Center, Into the Cloud: How a Southeast Nonprofit Cut $67K From Its IT Run-Rate
A 250-user nonprofit human services provider operating across 12+ locations completed its data center exit on January 1, 2026, retiring every on-premise server, and consolidated identity, productivity, and security around Microsoft 365 — cutting roughly $67,500 from annual IT spend in the process.
What Was the Problem with the Data Center?
The customer — a longstanding nonprofit serving children and adults with disabilities across more than a dozen locations in the Southeast — had quietly grown an IT footprint that was costing more every year and delivering less.
By the start of 2023, their core operating environment included a leased data center cage running terminal servers, file servers, and the on-premise accounting platform; a legacy on-premise Active Directory domain with site-to-site VPNs to every branch office; a patchwork of hardware support contracts, hypervisor licenses, server-tier backup, and server endpoint protection — each renewing on its own cycle; and three days a week of on-site engineering just to keep the environment running.
The data center lease was set to expire on December 31, 2025. Aging server hardware was approaching end-of-warranty. Annual run-rate spend on the on-premise estate had reached roughly $59,000 — before counting site internet circuits — and was trending upward as renewals stacked up.
Leadership wanted a single, decisive answer to a simple question: do we keep paying to maintain a data center, or do we get out of the server business entirely?
How Did Netsafe Approach the Data Center Exit?
Netsafe Solutions framed the engagement around replacement, not relocation. Where a SaaS option existed, the workload would move to it rather than be lifted-and-shifted to Azure IaaS — the goal was to retire infrastructure, not re-host it. A 10-user pilot ran ahead of the broader rollout to surface usability and training gaps where they were cheapest to fix, and to give the helpdesk a pattern to scale from before department-wide cutovers began.
The schedule was reverse-engineered from the lease’s December 31, 2025 expiration, leaving margin for rework. And critically, the planning effort weighted the people side as heavily as the technology — pilot feedback shaped the training plan, the communications cadence, and the helpdesk staging for every department cutover that followed. The result was a multi-year migration that produced almost no support volume the existing team couldn’t absorb.
Built With
How Was the Migration Sequenced?
The data center exit ran for roughly three years, sequenced so that the highest-risk and highest-cost dependencies were addressed first.
| Phase | Workstream | Outcome |
|---|---|---|
| Q1 2023 | Discovery & strategy | Two-track plan scoped: SaaS replacement for line-of-business + retire every on-prem server before lease expiry |
| Q3 2023 | 10-user pilot | Department heads moved to Entra ID, M365 Business Premium, OneDrive, managed endpoint protection. Pilot established the cutover playbook and surfaced training gaps |
| Q4 2023 | Site-by-site cutover | ~110 remaining users across 12+ locations migrated off the legacy domain to Entra ID. SharePoint replaced the on-premise file server; SaaS backup wrapped around the new M365 estate |
| 2024 | Compliance hardening | MFA rolled out org-wide. Encrypted email enabled to support HIPAA workflows. First wave of network refresh (firewalls, site internet circuits) |
| Q3 2025 | Line-of-business modernization | Legacy on-prem accounting platform replaced with a modern cloud ERP. Specialist implementation partner engaged for data conversion |
| Q4 2025 | Final server retirement | Last operational on-prem application server disconnected from active use, retained read-only for historical retrieval. Active Directory retired entirely; identity now exclusively in Microsoft 365 |
| Q1 2026 | Data center exit | Lease ended. Customer now operating cloud-first. On-site engineering reduced from three days a week to one |
What Were the Total Savings?
| Cost category | Before (annual) | After (annual) | Annual savings |
|---|---|---|---|
| Data center & lease | $11,148 | $0 | $11,148 |
| IT managed services | $28,380 | $10,320 | $18,060 |
| Data backup | $10,800 | $6,000 | $4,800 |
| Server antivirus | $2,160 | $480 | $1,680 |
| Hardware support contracts | $3,000 | $0 | $3,000 |
| Legacy security services | $1,620 | $0 | $1,620 |
| Hypervisor licensing | $1,200 | $0 | $1,200 |
| Server monitoring | $528 | $192 | $336 |
| Subtotal — data center exit | $58,836 | $16,992 | $41,844 |
| Right-sized internet circuits (5 sites) | $34,668 | $9,000 | $25,668 |
| TOTAL ANNUALIZED IMPACT | $93,504 | $25,992 | $67,512 |
All figures USD. Run-rate dropped from approximately $94,000 to $26,000 annually — a 72% reduction across data center, IT managed services, data backup, security tooling, hardware support, hypervisor licensing, and site internet.
What Did the Data Center Exit Deliver Beyond the Cost Savings?
The savings story is only part of the picture. The cloud-first architecture also delivered a meaningfully stronger operating posture.
Disaster recovery improved
With workloads distributed across Microsoft 365 and multiple SaaS platforms, there is no longer a single server room whose loss takes the organization offline. Both recovery time and recovery point objectives improved materially over the legacy environment.
24/7 SOC coverage
Endpoint detection and response is monitored continuously by an external Security Operations Center with the authority to remediate active threats — coverage the previous on-premise stack did not provide.
All Microsoft 365 data backed up
Email, OneDrive, and SharePoint are now protected by an independent SaaS backup, separate from Microsoft’s own retention. Recovery from accidental deletion or ransomware does not depend on Microsoft’s built-in tooling alone.
Every endpoint, every site
Identity, configuration, and security policy are now applied uniformly across every endpoint at every location, including remote and tablet users — without VPN dependency.
Lower operational drag
On-site engineering reduced from three days a week to one. Hardware support contracts, hypervisor renewals, and server-class security licenses were eliminated outright.
Audit-ready & cyber-insurance favorable
Microsoft Secure Score reached 74% (well above small-business median), with documented identity, backup, and endpoint controls aligned to the customer’s HIPAA obligations. The modernized identity, MFA, managed EDR, and SaaS backup posture aligns with what cyber-insurance underwriters now expect — easier renewals and better positioning at quote time.
Frequently Asked Questions — Data Center Exit
Should I exit my data center?
If your core line-of-business applications have viable SaaS replacements, and your existing Microsoft 365 (or comparable) tenant already provides identity, file storage, and email, you are likely paying twice for capacity. A data center exit replaces a high-fixed-cost on-premise estate with consumption-based SaaS, typically reducing run-rate by 50–75% over the first three years.
How long does a data center exit take?
The engagement above ran roughly three years, sequenced around a fixed lease-end date. Smaller environments without the same compliance footprint and line-of-business complexity can complete a comparable exit in 12–18 months. The lease-end date is the single most useful forcing function in the timeline.
What happens to legacy applications that don’t have a clean SaaS replacement?
Some workloads don’t migrate — they archive. The legacy line-of-business platform on this engagement was retained read-only for historical lookup rather than being forced into a costly conversion. Pragmatic compromises like that keep the project on schedule and the budget intact.
How does HIPAA compliance work after a data center exit?
The Microsoft 365 estate, when configured with MFA, Conditional Access, audit logging, encrypted email, and managed EDR, supports the technical controls HIPAA requires. Documentation of those controls — produced as the configuration lands, not reconstructed at audit time — is what auditors actually ask for. Microsoft Secure Score in the mid-70s and above is a reasonable proxy for “audit-ready posture.”
Will my team be productive during a multi-year migration?
Yes, when the migration is sequenced and piloted. The 10-user pilot in this engagement surfaced training and workflow issues — not technical ones — well before the broader rollout, which kept support volume low and protected day-to-day operations. Templated end-user communication ahead of every department cutover is what separates a smooth migration from a noisy one.
Is my organization a good candidate for a data center exit?
Most organizations paying separately for an on-premise data center alongside a Microsoft 365 subscription are good candidates. The case is strongest when the data center lease is approaching renewal, when server hardware is approaching end-of-warranty, or when the organization is consolidating IT vendors. Netsafe Solutions provides a free data center exit assessment for businesses across the Charlotte metro area and the broader Southeast.
Sitting on a data center lease? Let’s plan your exit.
Most organizations on Microsoft 365 alongside an on-premise data center are paying twice for capacity. We model your specific exit, including the line-of-business sequence, identity migration, security posture, and what your real run-rate looks like once the servers are gone. Free assessment.
Or call us:
(704) 333-0404