Should a multi-academy trust use one Google Workspace tenant or one per school?

One tenant with an org unit per academy suits most trusts: central safeguarding and sharing policy, one billing relationship, and staff can move between schools without a new account. Separate tenants are justified mainly where an academy is expected to leave or a local requirement forces separation.

Is Google Workspace free for academy trusts?

Education Fundamentals is available at no cost to qualifying schools, with paid editions adding security and archiving features. Qualification is assessed by Google against the trust's status, so confirm it before budgeting for paid seats.

When should a trust migration run?

Easter or the summer holidays. Term-time cutovers are possible but they convert a scheduled event into a support incident, because staff discover changes during lessons rather than during setup.

What causes the most work when an academy joins mid-year?

Shared drives owned by staff who have already left. Ownership has to be reassigned in the source tenant before the copy, or the files arrive with no accountable owner and nobody able to grant access.

Sectors

Google Workspace for academy trusts and MATs

Name: Workspace Migration Services
Address: 5th Floor, 5 Conduit Street, London, W1S 2XD, GB
Telephone: +44 20 7183 3436

A multi-academy trust running Google Workspace faces one structural decision before any migration work: a single tenant with 1 org unit per school, or a separate tenant per academy. A single tenant makes central safeguarding policy and staff movement between schools workable, and it is the right answer for most trusts.

Trust migration shape
Structure	One tenant, one org unit per academy, shared central policy
Licensing	Education Fundamentals is free to qualifying schools
Typical window	Easter or summer holidays, not term time
Per-school effort	Driven by staff count and shared drive sprawl, not pupil roll
Safeguarding	Central alerting rules, per-school delegated review
Rollover	One graduation and archiving process, run trust-wide in August

One tenant or one per academy

This is the decision that shapes everything after it. A single tenant lets the trust write safeguarding and sharing policy once, apply it per academy through org units, and move a teacher between schools without recreating an account. It also means one billing relationship and one place to look during an incident.

Separate tenants per academy make sense in narrow cases: where a school is expected to leave the trust, where a local authority requirement forces separation, or where an academy joins with a functioning estate and the trust has no capacity to absorb it this year. Those are real cases, but they are the exception, and they carry a permanent coordination cost.

Consolidating academies that arrive with their own tenant

New academies almost never arrive clean. Expect a tenant nobody has audited, shared drives owned by departed staff, pupil accounts created by a previous provider under an unknown naming convention, and at least one third-party application still authorised against the domain.

The sequence that works is discovery, ownership reassignment, then the copy. Reassigning shared drive ownership before the migration means the files arrive attached to somebody who still works there, and it is far cheaper to do in the source tenant than to unpick afterwards.

Full inventory of accounts, groups, shared drives and third-party app grants
Ownership reassignment for every drive held by a leaver
Naming convention decided centrally before any account is created
Mail routing during coexistence so neither school loses delivery
A dated cutover per academy rather than a trust-wide weekend

Safeguarding policy that survives delegation

Trust-level responsibility and school-level knowledge both have to be respected. The pattern that holds is central rules with delegated review: the trust decides what is alerted on and retained, while each academy's designated safeguarding lead reviews their own alerts rather than everything landing in one inbox nobody reads.

Sharing defaults belong to the same structure. Pupil org units restrict external sharing, staff org units permit it under conditions, and the difference is applied by org unit rather than by asking staff to remember which account they are using.

The August rollover, run once for the whole trust

Every academy has the same annual event: leaving pupils, arriving pupils, and staff changing schools. Run separately by each school it consumes the summer. Run once as a trust process, with a March decision on archiving and a scripted August execution, it is a day of work and an audit trail.

The decision worth making early is what happens to a leaving pupil's coursework, because it is a records decision rather than a technical one, and it is far easier to answer in March than during the first week of term.

What we see that others don't say

Trusts that started as separate school tenants and later consolidated describe the same surprise: the difficult part was never the mail or the files, it was the 4 or 5 years of shared drives owned by staff who had already left, which nobody could reassign because ownership had never been recorded centrally.

What this doesn't cover

We are not a safeguarding advisory service. We implement the alerting and retention policy your designated safeguarding lead sets; we do not write it for you.
We do not manage classroom devices, MIS platforms or filtering appliances, though we will work alongside the suppliers that do.
We do not advise on Education edition eligibility on the trust's behalf; qualification is determined by Google against the trust's own status.
We do not migrate pupil records held in an MIS. That is a separate system with its own supplier process.

Get a fixed price for this

Send your seat count, current platform and deadline. You get a fixed price and an available cutover date, usually within one working day, from the engineer who would run the work.

Prefer to talk? Call +44 20 7183 3436 (Mon–Fri 08:00–18:00 GMT), or message WhatsApp +44 7403 423563.

Questions we get asked

Should a multi-academy trust use one Google Workspace tenant or one per school?: One tenant with an org unit per academy suits most trusts: central safeguarding and sharing policy, one billing relationship, and staff can move between schools without a new account. Separate tenants are justified mainly where an academy is expected to leave or a local requirement forces separation.
Is Google Workspace free for academy trusts?: Education Fundamentals is available at no cost to qualifying schools, with paid editions adding security and archiving features. Qualification is assessed by Google against the trust's status, so confirm it before budgeting for paid seats.
When should a trust migration run?: Easter or the summer holidays. Term-time cutovers are possible but they convert a scheduled event into a support incident, because staff discover changes during lessons rather than during setup.
What causes the most work when an academy joins mid-year?: Shared drives owned by staff who have already left. Ownership has to be reassigned in the source tenant before the copy, or the files arrive with no accountable owner and nobody able to grant access.

How this page is verified

Reviewed by Workspace Migration Services migrations desk, Google Workspace migration engineers. Last checked 2026-09-19.

Education edition availability and feature differences reflect Google Workspace for Education documentation as of 2026-09-19.
Org unit and delegated administration behaviour reflects Google Admin Help as of 2026-09-19.
Consolidation observations derive from Workspace Migration Services project records to 2026-09-19.

Sources you can check

Plan the trust estate before the next joiner arrives

Send the number of academies, the staff count per school, and which tenants already exist. We will come back with a structure recommendation and a holiday-window plan.

Book an audit See pricing