Saving $50K Annually: A NYC Nonprofit's Cloud Migration

Challenge

The nonprofit had been running its own email and file servers for over a decade. What had started as a cost-saving measure, avoiding monthly per-user cloud fees, had become one of the organization’s biggest financial and operational burdens. Four on-premises servers occupied a converted closet that doubled as the “server room,” complete with a portable air conditioning unit that ran year-round.

The numbers told a painful story. Infrastructure maintenance consumed roughly 20 percent of the annual technology budget, including hardware warranties, software licenses, an outsourced IT company for server administration, and the electricity to keep everything running and cooled. Email uptime hovered around 94 percent, meaning staff experienced multiple outages per month. Some outages lasted hours, disrupting donor communications and program coordination.

Remote work was the most glaring gap. When the organization tried to implement a hybrid schedule, they discovered that accessing email and shared files from outside the office required a VPN connection that was unreliable at best and nonfunctional at worst. Staff resorted to forwarding work emails to personal Gmail accounts and sharing files via personal Dropbox accounts, creating both a productivity mess and a data governance nightmare.

The executive director knew the infrastructure had to change but was concerned about three things: cost, disruption, and whether a small nonprofit could really manage a cloud migration without losing data or productivity.

Solution

SBK’s approach centered on a principle that guides all of the firm’s nonprofit technology engagements: every dollar saved on infrastructure is a dollar that can go to mission delivery.

Assessment and Planning. SBK began with a thorough inventory of the existing environment: four servers running Exchange 2013, a Windows file server with 2.8 terabytes of shared files, a legacy donor management application, and a backup system that had not been tested in over two years. The team mapped all email accounts, distribution lists, shared mailboxes, and calendar configurations to ensure nothing would be lost in migration.

Platform Selection. SBK evaluated both Google Workspace and Microsoft 365 for the organization. Google Workspace was recommended for three reasons: the nonprofit qualified for Google’s free licensing tier for eligible organizations, the web-first interface aligned with the staff’s existing comfort level, and the built-in collaboration tools, including Docs, Sheets, and Drive, would replace the file server without requiring additional licenses. This was a vendor-neutral recommendation based purely on cost and fit, not a platform preference.

Migration Execution. The cloud transformation was executed over a two-week window, carefully sequenced to avoid disrupting active programs.

During week one, SBK migrated email accounts in batches of 15, starting with the executive team and IT-savvy staff who could serve as internal champions. Email history, contacts, and calendar events were migrated with full fidelity. Shared mailboxes and distribution lists were recreated in Google Groups. The team configured DNS records to ensure seamless mail delivery throughout the cutover.

During week two, shared files were migrated to Google Shared Drives with a folder structure redesigned in collaboration with department leads. Permission models were simplified from the overly complex Windows ACLs to Google’s more intuitive sharing model. The legacy donor management application was moved to a cloud-hosted version that the vendor already offered but the nonprofit had never adopted.

Training. SBK conducted eight small-group training sessions, each tailored to the department’s specific workflows. The sessions covered email, calendar, Drive, and Docs, with printed quick-reference guides distributed to every staff member. A dedicated support channel was maintained for four weeks after migration to handle questions as they arose in real work.

Decommissioning. With all services successfully migrated and validated, SBK decommissioned all four legacy servers. The portable AC unit was retired. The organization also renegotiated its internet contract, since the bandwidth originally provisioned for on-premises server access was no longer needed at the same level.

Results

The financial impact was immediate and significant. The organization saved approximately $50,000 per year by eliminating server hardware maintenance, software licenses, the outsourced server administration contract, and the associated electricity costs. Because Google Workspace was provided at no cost through Google’s nonprofit program, the ongoing per-user cost was zero for core services.

Email uptime jumped from approximately 94 percent to 99.9 percent, backed by Google’s enterprise SLA. In the six months following migration, the organization experienced zero email outages. Staff who had grown accustomed to starting their day by checking whether email was working could finally take it for granted.

All 75 staff members were trained within the two-week migration window. Post-migration surveys showed 89 percent of staff rated the new tools as “easier to use” than the legacy systems, and adoption of collaboration features like shared documents and team drives exceeded expectations.

The remote work problem was solved entirely. Staff could now access email, files, and collaboration tools from any device with an internet connection. The nonprofit successfully implemented a hybrid work policy within a month of completing the migration, directly enabling program delivery in communities where staff needed to work from the field.

The executive director described the project as one of the most impactful investments the organization had made in years, not because the technology was flashy, but because it removed barriers that had been holding the team back from focusing on what actually mattered: their mission.