If your Australian business is approaching 300 Google Workspace users, the awkward part is not technical first, it is commercial. Google’s current edition guidance still places Business editions in the 1 to 300 user bracket, while Enterprise is positioned for unlimited users and adds controls many mid-market firms do not actually need yet. You can see that in Google’s own edition comparison pages for Business editions, all Workspace editions and pricing. For teams at 280 to 300 users, that creates a decision point before the next hiring round: accept an edition jump, split domains, or move only mail and calendar workloads off first while keeping Google Drive, Docs and Meet for collaboration. For many buyers, the third option is the least disruptive. Google itself now describes Essentials editions as collaboration tools without Gmail, and Cloud Identity Free as suitable for users who do not need Workspace services such as Gmail and Calendar. That means a partial-exit pattern is possible, but it needs careful design around identity, mail routing, archives, calendar behaviour, mobile device management and user experience. This post sets out when a mail-only exit makes sense, how to design it, what to ask a vendor, and where the effort really sits. If you are comparing this with a full edition upgrade, it also helps to read Google Workspace Enterprise in Australia: which controls are you buying that a mail-only exit would replace more cheaply?.
01What changes at 301 users, and what does not
The first thing to ground is the licensing trigger. Google’s current public documentation says Business editions are for organisations with 1 to 300 users, and its pricing page states that Starter, Standard and Plus can be purchased for a maximum of 300 users. Enterprise editions are presented as the tier for unlimited users.
What does not automatically change is your need for every Enterprise feature. If your real requirement is still standard collaboration, file sharing, video meetings and identity management, a forced move of the whole stack can be disproportionate. That is why some firms redesign just the mail layer first. The idea is simple: remove the workload that is commercially forcing the decision, keep the collaboration stack that staff already use, then review the rest later.
This is not the same as pretending Gmail can stay active for everyone while another provider also becomes the real mail system. Google’s admin guidance still treats Gmail as an integrated service within Workspace, and the supported no-Gmail patterns sit under Essentials editions or Cloud Identity. So the design question is not whether to run two primary mail systems forever. It is whether to move hosted mailboxes out first, while preserving Google identity and collaboration.
- Use the 280 to 300 band as a design window, not as a panic point
- Separate licensing pressure from real collaboration requirements
- Assume mail, calendar and identity dependencies need explicit rework
02The viable architecture: move mail first, keep Google collaboration
There are two workable target states. The first is to keep users on paid Google Workspace collaboration licences that do not depend on Gmail as the primary mailbox. The second is to keep a smaller licensed Google cohort and use Cloud Identity Free for users who only need identity and basic Google access, because Google says that edition is for users who do not need Workspace services such as Gmail and Calendar. Which one fits depends on whether those users still need managed Drive, Meet, Docs and admin controls.
Google also positions Essentials editions as being designed to integrate with an existing email solution, and its Essentials guidance describes Enterprise Essentials as including Drive, Docs, Meet and Chat without Gmail inbox hosting. That makes the collaboration-without-Gmail model an official pattern, not a workaround.
In practice, the target state usually looks like this: your domain identity stays in Google, user sign-in remains familiar, Drive and Shared Drives stay in place, Meet continues as the meeting platform, but MX records and mailbox hosting move to another platform. Gmail is then either disabled for the migrated population or retained only for a reduced set of users during transition. This is often easier on the business than replacing storage, chat, meetings and email all in one programme.
If you are already standardising cloud operations and access control, this is also where cloud infrastructure engineering, DevOps and platform engineering and governance and compliance support become relevant. The technical work is less about mailbox copy alone, more about a clean coexistence boundary.
- Keep Google identity as the directory anchor
- Keep Drive, Docs, Shared Drives and Meet where they are
- Move MX and mailbox hosting to the new mail platform
- Decide whether users stay on collaboration licences or shift to Cloud Identity or Essentials based on feature need
03Where the design gets hard: calendar, search, mobile and archives
The hidden complexity is not inbound SMTP. It is the user-facing behaviours tied to Gmail and Calendar. If you move mailboxes out but keep Google accounts, you need to define where the primary calendar lives, how meeting invitations are processed, whether staff will send and receive invites from the new mail platform or still schedule in Google Calendar, and what the accepted source of truth is for free-busy data.
You also need to check which services you will lose or change. Google’s current setup guidance for integrated Gmail shows how deeply Gmail sits beside Chat and Meet in the user experience. If Gmail is removed from that experience, users can still keep collaboration tools, but your support model must reflect the new split.
Data handling matters too. Google’s data regions feature allows covered Workspace data to be stored and processed in the United States or Europe, not an Australia-only region, and Google’s admin help confirms those location options as United States, Europe or no preference. If your reason for changing mail is sovereignty or customer commitments, a mail-only exit may solve only one part of the requirement.
Retention and discovery need an explicit plan. On Google’s pricing page, Vault is included with Business Plus and above. If you remove Gmail but rely on Vault for email retention today, you need to replace that capability on the target mail platform or redesign your legal hold process. This is the point where many partial-exit projects either become properly governed, or become messy.
- Choose a system of record for calendar before migration starts
- Map retention and eDiscovery obligations before removing Gmail
- Decide how mobile mail profiles will be re-provisioned
- Check whether any regulatory requirement needs Australia-specific hosting, not just non-Google hosting
04Routing and coexistence: what Google supports, and what to avoid
During transition, some organisations want a long coexistence period. That can work, but it should be short and controlled. Google still documents advanced Gmail routing through the Admin console, and its setup page for integrated Gmail points admins to advanced email routing. Google also supports SMTP relay for devices and apps, which matters because printers, scanners, ERP notifications and line-of-business systems are often forgotten until the week of cutover.
What you should avoid is an indefinite hybrid where users do not know whether Gmail or the new platform is authoritative for mailflow. That causes missed delegates, broken sent-item expectations, unreliable journalling and support noise around calendar invitations. Use routing only as a migration bridge: staged pilot users, controlled batches, verified forwarding, then a firm switch of MX and client profiles.
Google’s own migration tooling guidance notes practical constraints as well. For example, suspended accounts cannot be migrated. That matters if you planned to export old Gmail data from dormant accounts after the main wave. Clean the account inventory first.
If you need a detailed pre-cutover runbook, your vendor should treat this like a mail infrastructure change, not a licence admin task. That is the same operational mindset behind mail infrastructure services and the checklist discipline used in Migrating to Google Workspace without losing mail, even though the direction here is the reverse.
- Use routing to bridge migration, not as a permanent architecture
- Inventory scanners, apps, no-reply senders and SMTP relays early
- Clean suspended and orphaned accounts before migration tooling is scoped
- Freeze mailbox moves during DNS and client-profile cutover windows
| Area | Question to answer before cutover | Why it matters |
|---|---|---|
| Licensing | Which users stay on Workspace collaboration licences, and which move to Cloud Identity or another no-Gmail model? | This decides both cost and which Google features remain available. |
| Calendar | Will Google Calendar or the new mail platform be the source of truth for invites and free-busy? | Mixed ownership is the fastest route to missed meetings. |
| Retention | How will email holds, archive search and legal export work after Gmail is removed? | Vault coverage may no longer match your obligations. |
| Devices and apps | Which systems send mail today through Google SMTP or user mailboxes? | Printers, ERP alerts and service accounts often break first. |
| Identity | Will users still authenticate to Google for Drive, Meet and Docs with the same primary address? | Sign-in continuity affects user adoption and support volume. |
| Support | Who owns incidents when mail is external but collaboration stays in Google? | Without a clear boundary, tickets bounce between vendors. |
05When this pattern is a good fit, and when it is not
A mail-first exit is a good fit when four things are true. First, staff heavily use Drive, Docs and Meet and you do not want to retrain everyone. Second, the main trigger for change is the Business-edition ceiling and the economics of crossing it, not a desire to replace collaboration. Third, your compliance needs around email can be met more cleanly elsewhere. Fourth, you can tolerate a design project around identity and calendar, rather than pretending it is only an MX change.
It is a poor fit when your business already wants to leave Google collaboration, when your legal team depends heavily on Google-native retention workflows, when you need one platform for mail and calendar because of executive support expectations, or when your actual requirement is more security and control inside Google, not less. In that case, a full review of what Enterprise buys is more sensible. The closest internal comparison is Google Workspace over 300 users in Australia: is Enterprise really required if you only need mail and calendar?.
It is also a poor fit if your chosen target platform cannot preserve the user experience your staff expect. Some organisations save on licensing but lose far more in meeting friction, search inconsistency and helpdesk load. The transition is worth doing only if the split is deliberate and supportable.
- Good fit: collaboration stays in Google, mail economics drive the change
- Bad fit: you also want to replace Drive, Meet and document workflows soon
- Bad fit: your archive and legal-hold model depends on Gmail staying primary
- Good fit: you need a phased transition, not a platform reset
06What to ask a vendor before you approve the project
This is where buyers can filter out teams that only know mailbox copy tools. Ask the vendor to show the target identity model, not just a migration tool demo. Ask them whether they propose keeping all users on paid Workspace licences, moving some to Cloud Identity Free, or using an Essentials edition, and why.
Ask for a calendar coexistence design, a retention design, and a line-by-line inventory method for SMTP senders. Ask how they will handle Google login continuity for Drive and Meet after mailbox cutover. Ask who owns support after go-live when the user says, 'email failed from my Google account', even though Gmail is no longer primary.
You should also ask for effort in business terms. For a tenant of roughly 280 to 300 users, the hard work is usually not the data transfer itself. It is discovery, pilot validation, client reprovisioning, cutover support, and post-move clean-up of archives, aliases, delegated access and devices. If a proposal is cheap because it ignores those items, it is not cheap. It is incomplete.
If you need a team to shape and deliver that split cleanly, SyncTrix can support the planning and implementation through its mail infrastructure service.
- Show me the target licence map per user cohort
- Show me the calendar source-of-truth design
- Show me how SMTP apps, scanners and service accounts will be tested
- Show me how retention and legal hold change after Gmail is removed
- Show me who owns BAU support across both platforms after cutover
07A practical recommendation for Australian firms at 280 to 300 users
If you are in the 280 to 300 band and you want to avoid a forced full-stack change, the sensible next step is not to rush into Enterprise or rush out of Google. It is to model a bounded mail-only exit. Start with a 30-day discovery that confirms licence cohorts, calendar ownership, archive obligations, SMTP dependencies, device impact and support boundaries. Then run a pilot with a contained group before the tenant crosses the cap.
The point is not that mail must leave Google. It is that you should decide before user 301, while you still have room to stage the move with less pressure. For many firms, keeping Google where it is strongest for them, collaboration and familiar identity, while shifting only mail first, is the most pragmatic path.
Sources
- Compare Business editions | Getting started | Google Workspace Help
- Compare Google Workspace editions
- Compare Flexible Pricing Plan Options | Google Workspace
- Essentials editions | Getting started | Google Workspace Help
- Compare Essentials editions | Getting started | Google Workspace Help
- Editions | Cloud Identity | Google Cloud Documentation
- Cloud Identity pricing | Google Cloud
- Data regions: Control geo-location of data | Google Workspace
- Choose a geographic location for your data - Google
- Set up integrated Gmail for your organization
- Activate Gmail with Google Workspace (@your-company)
- Send email from a printer, scanner, or app | Gmail | Google Workspace Help
- Google Workspace migration requirements
Topics
SyncTrix Editorial
SyncTrix · SyncTrix
Writes about the engineering decisions behind production systems - architecture, delivery and the trade-offs that only show up at scale.
Building something like this?
SyncTrix engineers AI, SaaS, platform and cloud systems for enterprises and high-growth teams. Tell us what you're shipping and we'll scope it with you.