Technology · 8 min read
Getting Microsoft 365 for Nonprofits: A Practical Migration Guide
Microsoft 365 can be free for qualifying nonprofits. Here's how to get it, what to expect, and how to migrate without chaos.
Microsoft 365 can be free for qualifying nonprofits. Here's how to get it, what to expect, and how to migrate without chaos.
Why This Matters
This guide is for organizations already on Microsoft 365 or committed to the Microsoft ecosystem. If you're evaluating whether M365 is the right fit for your organization — or considering a sovereign-first approach where your data and infrastructure stay under your control — visit our Sovereign Stack guide first.
Microsoft Nonprofits gives free or deeply discounted Office 365/Microsoft 365 subscriptions to qualifying organizations. Here's who qualifies:
If you meet these criteria, you likely qualify. The verification process is straightforward and handled through TechSoup (more on that below).
Microsoft sells discounted licenses through TechSoup, a nonprofit technology donation platform. Here's the process:
Go to techsoup.org, create an account, and register your nonprofit. You'll need your EIN, nonprofit registration documents, and a nonprofit email address ([email protected], not Gmail). TechSoup verifies your status—typically instant for 501(c)(3) orgs, sometimes 1-3 days for others.
Once verified, browse TechSoup's catalog for "Microsoft 365 for Nonprofits" (look under Business Productivity). You'll see donation options: usually free or heavily discounted licenses. Add what you need to your cart.
After checkout, TechSoup gives you a license key. Use it to activate a new Microsoft 365 organization or add licenses to an existing one. You'll set up your organization domain (e.g., yourorg.onmicrosoft.com or a custom domain like yourorg.org).
In the Microsoft 365 Admin Center, create user accounts and assign licenses. Each user gets their own account and sign-in. Users then download the Office desktop apps, set up Outlook, or access everything through the web.
If your nonprofit is large, buying annual licenses through TechSoup is cheaper than monthly Enterprise subscriptions. Nonprofits with 50+ staff often save thousands by buying annually on TechSoup rather than licensing through Microsoft directly.
Microsoft offers several tiers. Here's what matters for nonprofits:
| Tier | Cost (Nonprofit) | Best For | Key Features |
|---|---|---|---|
| Microsoft 365 Business Basic | Free or $6/user/month | Small nonprofits, limited budget | Outlook, Teams chat, OneDrive (1TB), Word/Excel/PowerPoint (web only), 50 GB email |
| Microsoft 365 Business Standard | ~$12/user/month | Growing nonprofits, need desktop apps | Everything in Basic, plus desktop Office apps, Teams meetings (300 participants), 1 TB OneDrive, advanced sharing |
| Microsoft 365 Business Premium | ~$18/user/month | Tech-savvy nonprofits, strong security needs | Everything in Standard, plus advanced threat protection, device management, advanced analytics, DLP (data loss prevention) |
| Microsoft 365 Enterprise E1 | ~$8/user/month (nonprofit discount) | Large nonprofits, high collaboration needs | Teams, Exchange, OneDrive, web Office, Teams meetings (300 participants), advanced eDiscovery, compliance |
Start with Business Basic (free). This covers email (Outlook), instant messaging (Teams), file storage (OneDrive), and web-based Office apps. If your staff needs desktop Word/Excel/PowerPoint, upgrade to Business Standard.
Don't overthink it. You can start with one tier and upgrade users later. Licenses are per-user, so you can have a mixed environment: some staff on Basic, others on Standard or Premium.
Before you migrate anything, spend 2-3 weeks planning. This prevents chaos later.
Document where your organization's data currently lives:
Create a simple spreadsheet: Tool name → owner → number of users → amount of data → criticality to business. This tells you what to migrate and what can wait.
Not everything needs to move on day one. Prioritize:
This phased approach reduces the shock to your team and gives time for troubleshooting.
Don't surprise your team. Two weeks before migration:
Staff who understand the "why" and have a training opportunity will adapt faster. Surprise migrations breed resentment. Give people time to adjust.
Here's the high-level approach. Detailed tools and tutorials are available from Microsoft, but this is how to think about it:
If you want [email protected] instead of [email protected], you need to set up a custom domain:
DNS changes can take 24-48 hours to propagate worldwide, even though Microsoft might accept them sooner. Don't panic if emails don't immediately arrive—wait a day.
In Microsoft 365 Admin Center, create an account for each staff member. You can:
This is the biggest step. You're moving years of emails from one system to another.
From Gmail: Use Microsoft 365's built-in Migration tool or third-party tools like Mimecast or Skykick. The process:
If anyone has emails with huge attachments, migration can slow or fail. Consider archiving old large emails in Gmail before starting migration.
Files move to OneDrive (personal) or SharePoint (team/collaborative). The approach varies:
For large migrations (50+ GB), use a third-party migration tool. It's faster and more reliable than manual copying. Tools like Mimecast, Sharegate, or Microsoft's own FastTrack service can handle thousands of files without timeouts or errors.
If you use Google Calendar:
Contacts migrate similarly: export from Gmail as a .csv, import into Outlook.
Don't do a big-bang migration. Use a phased approach:
| Week | What Happens | Staff Action | Downtime? |
|---|---|---|---|
| Week -2 | Announce migration, run training | Attend 30-min training, optional questions | None |
| Week 0 | Set up M365 tenant, buy licenses, verify domain | None | None |
| Week 1 | Migrate email. Run overnight. Verify next morning. | Check Outlook. Resend anything missing. Keep Gmail open. | 1-2 hours (email may be slow during sync) |
| Week 2 | Migrate shared drive files. Reorganize in OneDrive/SharePoint. | Help identify what to keep. Open files in new locations. | None if after-hours |
| Week 3 | Set up Teams channels, migrate chat history if needed | Start using Teams. Learn channel etiquette. | None |
| Week 4+ | Turn off Gmail, delete Dropbox. Full M365 operation. | Everything in M365 now. Support as issues arise. | None |
Why this timeline? It gives staff time to adapt, allows you to catch mistakes, and prevents panic. A 4-week rollout for 30 people is realistic. For 100+ people, expect 6-8 weeks.
Don't assume people will figure it out. Run these sessions:
Record these sessions. Staff will watch them again if they forget something.
OneDrive is personal storage (1 TB per user). SharePoint is team/organizational storage. If your whole team needs to collaborate on a file, it should be in a SharePoint document library or shared folder, NOT in someone's OneDrive. If it's only in Alice's OneDrive and Alice leaves, your team loses access. Establish a rule: "If it's for the team, it goes in SharePoint."
New Microsoft users often send important messages via email when they should use Teams channels. This defeats the purpose of moving to Teams. Educate staff: Channels = async discussion (visible to the whole team, searchable). Direct messages = private side conversation (like email, but within Teams). Don't email what belongs in a channel.
You can create email groups (Distribution Lists) in Microsoft 365, but Teams are better. Email groups are just lists; Teams give you shared calendar, shared files, and channels. If you create an email group for "Board Members," you've created a dead end. Create a Teams team instead and add people to channels.
OneDrive gives 1 TB per user. If someone has 2 TB of files, they won't all fit. Plan for this. Also, Microsoft is NOT your backup—if someone deletes a file, you have 93 days to recover it. After that, it's gone. Don't assume Microsoft 365 is a backup solution.
SharePoint and OneDrive sharing is powerful but confusing. Staff will over-share ("give everyone in the org access") when they meant to share with one person. Document your sharing policy: Who can share with whom? Are external partners allowed? Can people create new teams freely, or is that IT-only?
Plan for these questions to pop up:
Create a simple FAQ document or video. Have one person as the "Microsoft 365 champion" who staff can ask questions without going through IT (if you have IT). Make it easy to ask, and people will adapt faster.
If your nonprofit is ready to move to Microsoft 365 but wants expert guidance, we offer:
Schedule a free operations review. We'll assess your current tools, map out a realistic migration plan, and tell you exactly what you need to do and when. No obligation—just clarity.
Your answers shape what we write next.
Questions, experiences, or ideas — we're listening.