Google Workspace at 300 users in Australia: is the next user the point to split, self-host or go Enterprise?

01What actually changes at 300 users

The trigger is simple: Google positions Business editions as plans for 1 to 300 users, and Enterprise as the unlimited-user tier. On the public pricing page, Google says Business Starter, Business Standard and Business Plus can be purchased for a maximum of 300 users, and Enterprise has no minimum or maximum user limit. The help documentation repeats the same split, describing Business as 1 to 300 users and Enterprise as unlimited users. Google Workspace pricing and Google Workspace Help, Compare Business editions.

That is why user 300 is the planning point. If you renew an annual Business subscription while already tight on headcount, you can end up with a contract that is cheap per seat but operationally boxed in. Google’s billing help says the Annual or Fixed-Term plan requires you to pay the full commitment even if you cancel early, while the Flexible plan bills by actual usage and can be cancelled without penalty. Compare flexible and annual-fixed term payment plans and Flexible plan.

For most Australian IT leaders, the real decision is made at one of three moments: 60 to 90 days before renewal, when a merger or hiring round is visible, or when procurement asks whether the next contract term should still be on Business. If you leave it until the account admin gets a licence limit message, you have already lost most of your low-disruption options.

• Business editions are capped at 300 users
• Enterprise removes the user cap
• Annual commitments reduce flexibility at exactly the wrong time
• The best time to decide is before renewal or a hiring event

02Option 1: move to Enterprise before you need seat 301

The lowest-disruption option is usually to stay on Google and move the domain to an Enterprise edition before the cap blocks further growth. This avoids a mail migration, keeps Gmail, Drive, Meet and admin workflows in place, and removes the immediate licensing constraint. Google’s edition comparison describes Enterprise Standard as the full productivity suite with enterprise-grade security and management, and Enterprise Plus as the suite with Google’s most advanced security and compliance controls. Compare Enterprise editions.

There is a commercial catch: Google does not publish standard self-serve Enterprise seat pricing on the same basis as Business. Its billing help says Enterprise edition pricing is available through Google sales or resellers. That means you need a quote, and your price depends on route to market, term and negotiation. Understand Google Workspace bills and charges.

Enterprise is usually the cleanest answer if your business is still growing, if you rely heavily on native Workspace collaboration, or if you want to avoid a mail platform project this year. It is also the least disruptive route for identity, mobile device management, retention settings and support processes because your administrators remain in the same control plane. If you already have adjacent Google services or need help with surrounding platform controls, this often overlaps with broader cloud infrastructure and cybersecurity and risk decisions.

The important procurement question is not only seat price. Ask for the edition, contract term, support route, feature deltas from your current Business plan, data region eligibility, and any migration effort required inside the tenant. In many cases, the technical move is much easier than the commercial one.

• Best for least user disruption
• Removes the 300-user ceiling
• May improve security and compliance controls
• Requires reseller or Google sales pricing, not simple list-price budgeting

03Option 2: split into more than one Google Workspace tenant

Some organisations look at splitting users across separate Workspace tenants to stay on Business pricing. On paper, this can look cheaper than Enterprise because the published Business rates remain visible. On the Australian pricing page, Google lists Business Starter at A$7, Business Standard at A$14, and Business Plus at A$22 per user per month on annual plans, with the page also advertising that annual plans save 16 percent versus flexible pricing. But a split-tenant design turns one company into multiple collaboration islands. Google Workspace pricing, Australia.

The hidden cost is operational complexity. Directory management, user lifecycle processes, shared calendars, delegated mailbox access, Drive sharing policy, Google Meet defaults, admin roles and compliance settings all become harder across tenant boundaries. Mergers, role changes and internal transfers become mini-migrations. Help desk work rises. Security review gets messier because the same company now has multiple policy surfaces.

A split can still be rational in narrow cases: legally separate entities, strong autonomy between business units, or an existing multi-domain operating model where collaboration is already limited. It is a poor fit if your teams share files heavily, move people between functions, or need one clean identity and compliance model. Before you consider it, read the logic in our related post on Google Workspace over 300 users in Australia and map the administrative overhead in plain terms, not just licence cost.

If you do evaluate a split, insist on a pilot design first. Document what breaks for shared calendars, email aliases, executive delegation, Vault and retention policy alignment, and service desk scripts. If you cannot explain the day-two operating model in one page, the split is probably false economy.

• Can reduce visible seat cost versus Enterprise
• Adds permanent admin and collaboration overhead
• Suitable mainly for already-separated business units
• Usually poor for one-company, one-directory operating models

04Option 3: self-host mail, or move only mail off Workspace

The third option is to leave the Business cap problem by moving away from Google-hosted mail. This can mean a full mail platform migration, or a narrower design where collaboration stays in Google while core mail is handled elsewhere. For some organisations, especially those with stable requirements and strong infrastructure discipline, this can be cheaper over time than paying Enterprise pricing. It can also give more control over retention, routing and integration.

But this is the highest-disruption option unless you already operate serious messaging infrastructure. Self-hosting is not just a software choice. It means owning availability, patching, spam protection, anti-malware, backups, restore testing, DNS hygiene, certificate management, transport rules, mailbox migration, mobile client behaviour and deliverability reputation. If your team is comparing licence cost only, the model will be wrong. Our broader post on self-hosted mail vs Google Workspace vs Microsoft 365 is useful here because the crossover point is operational, not merely financial.

There is also a data location nuance. Some buyers assume Google Workspace can be pinned to Australia. Google’s Data Regions materials say data region choices are the United States, Europe, or no preference for supported editions and covered services. The service-specific terms define Data Region the same way. That means if your board or customers need a specific Australian data residency posture, Enterprise by itself does not create an Australia-only Workspace data region. Choose a geographic location for your data, Google Workspace Data Regions and Google Workspace Service Specific Terms.

Self-hosting therefore becomes more attractive only when at least one of these is true: you have a strong platform team, you already run adjacent messaging infrastructure, your compliance or routing requirements are unusual, or the commercial gap between Enterprise and a managed mail alternative is large enough to justify a migration. If you need outside help, this is the sort of work SyncTrix handles through mail infrastructure, often alongside managed services or governance and compliance.

• Potentially lower recurring platform cost
• Highest migration and operating burden
• Best only when you can support mail as infrastructure, not just software
• Useful if your requirements have moved beyond standard Workspace assumptions

05How to choose the least-cost, least-disruption path

For most organisations at exactly 300 users, the practical ranking is: Enterprise first, split tenant second only in specific structures, self-host third unless there is a clear financial or compliance reason. That order is not ideological, it is based on transition risk.

Choose Enterprise if your headcount is likely to grow, your collaboration model is cross-functional, and your priority is to avoid user-facing disruption. The cost review should include the reseller quote, term flexibility, security uplift and any concessions for moving at renewal.

Choose a split only if your organisation is already operationally split. If collaboration across units is common, the day-two cost usually wipes out the seat-price win.

Choose self-hosting only after you cost the full operating model: migration project, spam filtering, security patching, backup and restore testing, monitoring, on-call, and support ownership. If the person proposing it cannot name who owns deliverability and recovery testing, the business is not ready for that option.

This is also the point to clean up licence policy and growth forecasting. Review dormant accounts, shared mailboxes, front-line workers who may not need full licences, and acquisition scenarios. If your current plan choice was made when you had 180 users, refresh it now. Our post on Google Workspace annual vs flexible pricing helps with the contract-side trade-off.

• Prefer the option that preserves operating simplicity
• Treat annual renewal as a commitment decision, not just a discount choice
• Cost day-two operations, not just licences
• Model growth for the full contract term

06Questions to ask before you sign anything

Use this shortlist with Google, your reseller, or any alternative provider.

For an Enterprise quote: what edition is proposed, what is the term, who provides support, what features change from our current plan, and what happens to existing billing at renewal? Google’s own help makes clear that Enterprise pricing is handled through sales or resellers, so force clarity on the commercial path. Understand Google Workspace bills and charges.

For a split-tenant design: how will you handle identity lifecycle, shared resources, delegated access, retention settings, and internal moves between business units? Ask for the exact admin runbook, not a conceptual diagram.

For self-hosting or managed mail: who owns patching, anti-spam, backup verification, restore tests, deliverability monitoring, domain authentication, disaster recovery and mailbox migration? Ask for the first 90 days of operational responsibility in writing.

Finally, ask one timing question regardless of option: what must be decided before the current renewal date to avoid paying for a full annual commitment that no longer fits? Google’s billing guidance is explicit that annual plans carry the remaining commitment if cancelled early. Compare flexible and annual-fixed term payment plans.

If the answers are vague, delay the commitment, not the analysis. At 300 users, the cheapest mistake is usually the one you avoid before renewal. If you want a practical review of mail options, migration effort and the operating model behind them, see our mail infrastructure service.

• Get term, edition and support route in writing
• Demand day-two operating details, not only transition plans
• Check cancellation and renewal implications before committing
• Do not evaluate self-hosting on licence cost alone