Email Migration for Schools: FERPA-Compliant Guide (2026)

For most businesses, an email migration is a project you schedule around a quiet week. For a school or district, it’s a project you schedule around a school year, a graduating class, an incoming kindergarten cohort, and a federal privacy law that doesn’t care how busy your IT department is in August.

School and district IT leaders face a unique combination of pressures that don’t show up in a typical SMB migration: thousands of student accounts that need to be created, suspended, or purged on a predictable annual cycle; parent and student privacy protections under FERPA; content filtering obligations under CIPA; and a decision between two platforms, Google Workspace for Education and Microsoft 365 Education, that were both built with classrooms specifically in mind.

This guide walks through what makes school email migrations different, how to choose between Google Workspace and Microsoft 365 for an education environment, and how to plan a migration that survives contact with the school calendar.

Why School Email Migrations Are Different

1. FERPA governs more of your email than you think

The Family Educational Rights and Privacy Act protects student education records, and that protection extends into email. Staff messages that reference grades, discipline, IEPs, or attendance are education records once they exist in writing. Schools are expected to keep those records secure, limit access to staff with a legitimate educational interest, and avoid routing them through personal or unsecured email accounts.

A migration is exactly the moment this gets tested. Mailboxes, shared drives, and distribution lists get copied, re-permissioned, and sometimes temporarily duplicated across two systems. Every one of those steps needs the same access controls and audit trail the district already promises in its annual FERPA notice.

2. CIPA and content filtering don’t pause during a migration

The Children’s Internet Protection Act requires districts receiving E-Rate discounts to filter internet content for minors and monitor online activity. Filtering and monitoring tools are frequently tied to the identity platform, so a mid-migration state where some students are on the old domain and some are on the new one can create gaps in content filtering coverage if it isn’t planned for.

3. Student accounts follow a lifecycle, not a headcount

A business migrates a relatively stable list of employees. A school migrates:

Graduating seniors, whose accounts typically need to be suspended or transitioned to personal email within weeks of graduation
Incoming students, whose accounts often need to exist before the first day of school
Mid-year enrollments and withdrawals
Staff turnover, which follows its own separate calendar

Getting the provisioning and de-provisioning rules right during a migration matters more than getting the mailbox move itself right, because those rules will run every year after the migration is done.

4. The timing window is short and non-negotiable

Nearly every district migration happens in the same six-to-ten week window between the last day of school and the first day back. IT staff typically use the summer specifically to clean up the email database, creating new accounts for incoming students and removing graduated students’ accounts shortly after the school year ends. There’s no “we’ll finish it next sprint.” If the migration isn’t done before the first day of school, the district starts the year on two systems.

Google Workspace for Education vs. Microsoft 365 Education: Which Fits Your School?

Both platforms offer free or steeply discounted tiers for eligible institutions, and both have invested heavily in classroom-specific features over the past few years. The right choice usually comes down to grade level, existing devices, and how much dedicated IT staff the district has.

Google Workspace for Education Fundamentals tends to provide the best value with minimal administrative complexity for K-8 environments, while Microsoft 365 Education A3 is often positioned as the better fit for high school and higher education settings where device management and professional-tool familiarity carry more weight.

Factor	Google Workspace for Education	Microsoft 365 Education
Core hub	Google Classroom, with Gmail, Drive, and Meet layered around it	Teams, with virtual classrooms, assignment distribution, and grading built in
Admin experience	Generally considered easier for IT coordinators without enterprise IT backgrounds	More capable, but typically requires more IT skill to use to its full potential
Device fit	Works well on Chromebooks and any device with a browser	Stronger fit when the district is already standardized on Windows devices, particularly with A3-and-above tiers
Free tier	Education Fundamentals: free, includes Gmail, Meet, Drive, and Classroom	A1: free for eligible institutions, includes Exchange, Teams, SharePoint, and web Office apps
Paid tier example	Education Plus, roughly $3 per student/month, adds enhanced admin controls and audit tools	A3/A5, roughly $2.50–$8 per user/month, adds desktop Office apps, device management via Intune, and advanced security
Accessibility tools	Screen reader and captioning support built into Docs and Meet	Immersive Reader and Dictation support students with diverse learning needs
Best-fit grade band	K–8, where administrative simplicity matters most	High school and higher ed, where device management and professional-tool exposure matter more

Pricing on both platforms shifts fairly often, so confirm current education-tier rates directly with Google and Microsoft (or your reseller) before budgeting. Districts weighing the platform decision on cost alone should also see our Email Migration Cost Guide for the variables that move a quote up or down.

If your district is genuinely undecided between the two platforms as a general business matter (not education-specific), our Microsoft 365 vs. Google Workspace comparison covers the broader feature and pricing tradeoffs.

Planning the Migration: A Realistic District Timeline

A typical district migration compresses into the gap between the last day of school and the first day of the next one. Here’s a working structure:

8–10 weeks before the first day of school

Finalize platform choice and licensing (education-tier pricing and eligibility verification can take longer than expected)
Inventory mailboxes, shared department accounts, distribution lists, and any special-education or counseling mailboxes that need tighter access controls
Confirm which accounts should be excluded from migration (accounts for graduating seniors, staff who’ve resigned, etc.)

6–8 weeks before

Set up the destination tenant, domain verification, and DNS records
Build the access and permission model before moving a single mailbox — this is the step most likely to create a FERPA exposure if rushed
Communicate the plan to staff, including any downtime windows

4–6 weeks before

Run the migration in batches, starting with departments least likely to need email access during the summer (this gives you a chance to catch issues before migrating active summer-school staff)
Test content filtering and CIPA-required monitoring tools against the new platform before cutting over the full district

1–2 weeks before the first day of school

Final delta sync to capture any mail sent during the migration window
Provision new student accounts for the incoming class
Confirm graduated students have received clear instructions and a deadline for transferring personal content; most districts give departing students only a couple of weeks after graduation before accounts are disabled and then purged, with no way to recover data once that happens

First day of school onward

Monitor for missed mail, broken distribution lists, and shared mailbox access issues in week one
Decommission the old tenant on a schedule, not immediately; keep it available in read-only mode for a defined retention period in case anything was missed

For the technical mechanics of moving mailboxes between platforms, our step-by-step guides cover the process in detail: Google Workspace to Microsoft 365, Microsoft 365 to Google Workspace, and, for districts still running on-premises Exchange or an older IMAP-based system, our legacy email migration guide.

Student Account Lifecycle: Getting the Ongoing Rules Right

The migration itself is a one-time event. The account rules you build during it run every year afterward, so it’s worth getting them right the first time.

Graduating students: Decide in advance whether accounts are disabled immediately, given a short transfer window, or (less commonly) kept active longer for alumni purposes. Document the deadline clearly and communicate it directly to students, not just parents, since FERPA rights transfer to the student at 18 or upon enrolling in a postsecondary institution.
Incoming students: Automating account creation from your Student Information System (SIS) removes the scramble of manually provisioning hundreds of accounts the week before school starts.
Mid-year enrollment and withdrawal: Build a standing process rather than a summer-only one; students move in and out of districts throughout the year.
Staff offboarding: Departing staff mailboxes often contain education records that need to be preserved or transferred to a supervisor, not simply deleted. This is a different retention rule than the one you’d apply to a departing employee at a typical small business.

Common Pitfalls in School Email Migrations

Migrating during the school year “in pieces” to avoid disruption. This sounds safer but usually creates more support tickets, since staff end up split across two systems for an extended period.
Forgetting shared and departmental mailboxes. Front office, nurse’s office, athletics, and special education department mailboxes are easy to miss in an inventory built from a staff directory alone.
Assuming content filtering carries over automatically. CIPA-required filtering and monitoring tools frequently need to be reconfigured or reconnected against the new platform, not just the new mail system.
No clear alumni/graduate communication plan. Complaints from recent graduates who lost access to email they didn’t know would be disabled are one of the most common post-migration issues districts report.
Underestimating education-tier licensing verification time. Confirming eligibility for free or discounted tiers can add unexpected lead time to a project that’s already working against a fixed calendar.

Frequently Asked Questions

Does FERPA require a specific email platform for schools? No. FERPA doesn’t mandate a specific platform or vendor. It requires that education records, including relevant email communications, are protected with appropriate access controls, and that disclosures follow the law’s consent and exception rules. Both Google Workspace for Education and Microsoft 365 Education can be configured to meet these requirements.

When is the best time of year to migrate a school’s email system? The summer break between school years is the standard window, since it minimizes disruption to instruction and gives IT staff time to test the new environment before students and staff return. Most districts plan for a project that starts shortly after the last day of school and finishes before the first day of the next one.

What happens to a graduating student’s school email account? This depends on district policy, but most districts disable accounts a short time after graduation, often just a few weeks, and permanently delete them shortly after. Students who want to keep any of that content typically need to export or forward it themselves before the deadline, since there’s usually no way to recover it once the account is purged.

Is Google Workspace or Microsoft 365 better for K-12 schools? There isn’t a universal answer. Google Workspace for Education is often favored in K-8 settings for its administrative simplicity, while Microsoft 365 Education is frequently chosen in high schools and districts already standardized on Windows devices, particularly where device management and professional-tool exposure are priorities. The right choice depends on your grade bands, existing hardware, and IT staffing.

Can a small or mid-sized district afford a professionally managed migration? Yes. Education-tier licensing is typically free or heavily discounted compared to standard business pricing, which often leaves more budget available for migration and ongoing management services than districts expect. See our pricing guide for the variables that affect cost.

How EMNMS Helps Schools Migrate Without the Summer Panic

School and district email migrations run on a calendar that doesn’t bend, with a privacy law that doesn’t forgive shortcuts. EMNMS plans the project around your academic calendar, builds the access controls FERPA and CIPA expect from day one, and handles the account lifecycle rules that keep working long after the migration is finished.

Talk to EMNMS about your district’s migration →

Email Migration for Schools: FERPA-Compliant Guide (2026) | EMNMS