Google Workspace at 301 users: do you need Enterprise or should you self-host mail?

01What actually changes at user 301

The hard change is licensing eligibility. Google’s current edition guidance places Business editions in the 1 to 300 user category, and the Australian pricing page repeats that Business Starter, Standard and Plus are capped at 300 users. Enterprise is the path Google presents once you grow beyond that limit.

The soft change is procurement leverage. Google publishes standard prices for Business editions, including in its billing guidance, but for Enterprise editions it tells customers to contact Google Sales or a reseller. That means the clean self-serve buying model disappears at the same moment your seat count gets large enough for licence spend to become material.

The decision therefore moves from product selection to commercial architecture. At 80 users, paying more for a bundled suite may be simpler than redesigning mail. At 301 users, even a modest per-user uplift compounds quickly across active staff, shared accounts, leavers under retention, and future headcount. That is why many buyers start modelling alternatives such as a split estate, a third-party hosted mail stack, or fully managed mail infrastructure rather than assuming Enterprise is the only sensible route.

• Hard rule: Google Workspace Business editions stop at 300 users
• Commercial consequence: Enterprise pricing usually becomes a sales negotiation
• Architecture consequence: email can now be reviewed as a standalone service, not just part of the suite

02When Enterprise is the right answer

Enterprise is usually the right move when you are buying control, not just extra seats. Google positions Enterprise as adding premium security and advanced controls for unlimited users. Its enterprise comparison says Enterprise Standard includes the full productivity suite with enterprise-grade security and management.

This matters if your organisation already uses Google’s governance layer deeply. Google Vault provides retention, legal hold, search and export for Workspace data. If legal, HR or investigations teams already rely on Vault, moving mail off Google is not just a transport project. It changes retention, discovery, supervision, and access processes.

Security control is another major reason to stay. Google’s current documentation says Context-Aware Access is supported for Enterprise Standard and Enterprise Plus, and lets you set app access rules using identity, location, device security status and IP address. For organisations trying to reduce account takeover risk or limit access from unmanaged devices, that can be more valuable than the mailbox itself.

Enterprise also fits better when you want the least operational change. Keeping Gmail, Drive, Meet and admin tooling under one control plane reduces migration effort, user retraining, support load and integration breakage. For some firms, especially those with lean internal IT, avoiding a mail platform redesign is worth more than the licence delta. If you need outside help on the broader platform and security side, the related work usually sits closer to cloud infrastructure engineering and cybersecurity and risk engineering than to a basic mailbox move.

• Choose Enterprise if you actively use Vault or expect legal hold requirements
• Choose Enterprise if device-aware or network-aware access policy matters
• Choose Enterprise if minimising change risk matters more than reducing licence spend

03When self-hosted mail is worth considering

Self-hosted mail becomes worth considering when email is a commodity in your environment rather than a control platform. If most users live in browser tabs, line-of-business systems, chat and shared docs, then the email layer may not need to remain bundled with your collaboration suite.

The strongest case is economic and operational simplicity at the mail layer. If you can run a standards-based mail platform with IMAP, SMTP submission, modern authentication, anti-spam, backups and monitoring, you may be able to separate a costly all-in-one suite decision from a much narrower mail requirement. The buyer mistake here is assuming self-hosting means one VM with Postfix and Dovecot. In practice, a viable production service also needs mail hygiene, authentication, certificate management, queue monitoring, abuse protection, backup and restore, logging, admin workflows, and a clear path for user lifecycle management.

Self-hosting is most defensible when your team can tolerate using Google primarily for collaboration without Gmail, or when you are prepared to replace more of the Google stack. It is far less attractive if users expect seamless Gmail-native workflows, delegated mailbox handling inside Google admin patterns, or Google-based discovery on mail data.

There is also a compliance angle. For Australian organisations, the OAIC guidance on APP 8 cross-border disclosure says an APP entity that discloses personal information overseas must take reasonable steps to ensure the overseas recipient handles it in line with the APPs, and the entity can remain accountable under section 16C. The OAIC’s practical guidance on sending personal information overseas is relevant here. For some buyers, self-hosting or choosing an Australian-hosted specialist is less about sovereignty theatre and more about reducing cross-border exposure and simplifying procurement answers.

• Self-hosted mail is a real option if email is infrastructure, not a workflow hub
• It only works if you cost the full operating model, not just server rental
• It becomes more attractive when privacy, control or residency questions are commercially important

04The hidden costs buyers miss when they compare Enterprise with self-hosting

The easiest comparison is monthly licence cost. It is also the least useful. Google publicly lists Business edition pricing and says Enterprise pricing is via sales or resellers, so you will need actual quotes before making a fair model. What you can compare now is effort and risk.

With Enterprise, the cost drivers are usually commercial: seat uplift, contract term, archived user handling, and add-ons. Google documents Archived User licensing for preserving former users’ Workspace data, and Vault documentation notes that assigning an archived user licence can preserve data for departed staff instead of keeping a suspended account billed like an active one. If you have a lot of leavers under retention, this affects total cost of ownership, not just active headcount.

With self-hosting, the hidden cost drivers are engineering and operations. You need design time for identity integration, migration planning, MX cutover, spam filtering, DKIM, SPF and DMARC alignment, mailbox import, backup validation, restore testing, monitoring, patching, and on-call ownership. You also need someone accountable for deliverability when outbound mail starts landing in junk, which is a real operating concern and not a one-off setup task.

A practical rule is this: if no named person or partner owns mail operations after go-live, you are not comparing like with like. You are comparing a managed service with an unfinished internal project. That is why many mid-market firms that reject Enterprise still do not truly self-host. They use a provider or specialist partner to run the platform as an operational service. If you are weighing that route, our related post on self-hosted mail vs Google Workspace vs Microsoft 365 can help frame the trade-offs.

• Enterprise hides cost in contract structure and retention licensing
• Self-hosting hides cost in labour, tooling and support ownership
• Deliverability and recovery are operating disciplines, not setup tasks

05A simple decision framework for Australian buyers

Start with legal and security requirements, not price. If you need Google-native retention, holds, exports and tightly integrated admin control, Enterprise should be your baseline. If mail is mostly transport and recordkeeping, and your controls can live outside Google, then self-hosted or specialist-hosted mail enters the shortlist.

Next, map user behaviour. How many staff really need Gmail as part of Workspace, and how many simply need a mailbox that works? How much delegated mailbox use exists? How much filtering, routing, journalling or shared inbox behaviour is tied to the current platform? Buyers often discover they are not comparing 301 equal users. They are comparing a smaller set of high-need users and a larger set of commodity mail users.

Then test compliance posture. For Australian entities handling personal information, the OAIC’s APP 8 guidance should sit in the decision pack if data may be disclosed overseas. Even if you are comfortable with offshore processing, procurement, customer questionnaires and board reporting may still favour a clearer hosting story.

Finally, score execution risk. Moving to Enterprise is mostly a commercial event with some admin change. Moving off Google mail is an infrastructure project. That project can still be the right decision, but only if you treat it like one. You need discovery, architecture, staged migration, rollback planning, validation, user communication and post-cutover support. If your team is small, a partner-led approach through mail infrastructure services or broader managed services is usually safer than trying to absorb it into BAU support.

• Step 1: decide whether governance or low-cost mail is the primary requirement
• Step 2: separate high-need users from commodity mail users
• Step 3: review APP 8 and customer data handling expectations
• Step 4: compare delivery risk, not just run-rate cost

06Questions to ask before you sign Enterprise, or before you leave Google mail

Ask Google or your reseller: what is the actual Enterprise edition proposed, what are the included controls, what term is assumed, what happens to pricing at renewal, and what archived user options apply in your contract model. Google’s own billing guidance makes clear that Enterprise pricing is not presented like Business pricing and must be obtained from sales or a reseller. Get it in writing.

Ask any self-hosting or specialist mail vendor: who owns deliverability, how are backups tested, what is the restore process, how are spam and abuse handled, what monitoring exists, what is the admin model for joiners and leavers, and how will legal hold or discovery be handled if you leave Google mail. Also ask how MX cutover, coexistence and rollback are run.

Ask internally: do we want a software subscription, or a mail service? Those are not the same purchase. If you only need business email, buying a full suite at enterprise tier may be inefficient. If you need integrated governance and low-change operations, building or operating mail yourself may be false economy.

This threshold is exactly where firms benefit from a short architecture and commercial review rather than jumping straight into procurement. SyncTrix works on this kind of mail infrastructure decision and migration, but the main point is broader than any one vendor: at 301 users, do not let a licensing cap make your architecture decision for you.

• Get a real Enterprise quote, with term and renewal assumptions
• Require named ownership for deliverability, backup and incident response
• Do not approve a self-hosting plan without discovery and rollback planning