Australia at 280 Google Workspace users: should you split domains now to avoid an expensive jump at 301

01What the 280-user mark really changes

At 280 users, you still have time to choose an architecture on your terms. At 301, you are normally reacting to a commercial constraint. Google’s own edition comparison pages place Business editions in the 1 to 300 user bracket and Enterprise as the unlimited-user tier: Compare Google Workspace editions, Compare Business editions.

That matters because the workaround most buyers imagine first, adding more domains inside the same Google Workspace tenant, does not solve the cap. Google lets you add a domain as a user alias domain or a secondary domain so users can have addresses at more than one domain, but those domains still sit inside the same account boundary: Add a user alias domain or secondary domain. If your goal is to stay on Business beyond 300 paid users, secondary domains are branding and routing tools, not a licence-cap escape hatch.

The practical question at 280 is therefore this: do you want one integrated Google tenant with simpler collaboration, or do you want to preserve Business-plan economics by running separate tenants or moving only some services away from Google mail? If you expect to add 20 to 60 users in the next renewal period, decide now, not after procurement is staring at an Enterprise quote.

• Do not assume adding a secondary domain avoids the 300-user limit
• Treat 280 as the design window, not a comfort zone
• Model the next 12 months of hires, contractors, acquisitions and seasonal users before renewal

02Your three realistic paths before 301

For most organisations, there are three credible options.

First, stay in one tenant and move to Enterprise when needed. This is the cleanest operating model. You keep one identity boundary, one global address list, one set of sharing rules, one admin plane and fewer migration risks. It is usually the right answer when Google Drive collaboration, shared calendars, Google Meet, security controls or central governance matter more than squeezing licence cost.

Second, split into multiple Google Workspace tenants before you hit the cap. This can preserve access to Business editions because each tenant is its own purchase boundary. But the trade-off is operational fragmentation: separate directories, more complex sharing, duplicated admin, more work for mail routing, archives, address books, onboarding and offboarding. Google documents limitations when you run multiple domains in one account, and moving to multiple accounts introduces even more separation than that: Limitations with multiple domains.

Third, move only mail for a selected group, usually users who mainly need email and calendar, while keeping some teams or workloads on Google Workspace. This route is attractive when your issue is per-seat economics for basic communication users, not Google Docs or Drive collaboration. It can mean another mail platform, a separate low-cost mail environment, or in some cases a self-hosted approach. The trade-off is that identity, calendaring, coexistence and deliverability design become the real project. If mail is the part you are reconsidering, mail infrastructure services and this broader comparison can help frame the options: Self-hosted mail vs Google Workspace vs Microsoft 365.

• Path 1: accept Enterprise, simplest operations
• Path 2: split tenants, lower licence flexibility but higher admin complexity
• Path 3: move only mail, potentially cheaper for some cohorts but technically harder than it looks

03Why a domain split is often harder than finance expects

Buyers often hear “just split the domain” and assume this means adding another email domain to the current tenant. Google does support adding secondary domains and domain aliases, and there is no separate domain charge in the product model because billing is per user account, not per added domain: Add a user alias domain or secondary domain, Google Workspace pricing. But this still leaves you inside one tenant and one user count.

A true cap-avoidance split normally means separate tenants. That brings identity and naming questions that should be settled before you touch MX records. Which users keep the existing primary email domain? Do new hires join a new brand or sub-brand domain? Does the old tenant retain the primary domain, or do you change the primary domain and keep the old one as an alias? Google’s own help warns that changing the primary domain is an involved process and suggests considering adding another domain instead: Change your primary domain for Google Workspace.

Then there is collaboration. Google Drive ownership transfer is straightforward only within an organisation boundary. Google’s Drive help says ownership transfer for work or school accounts can only go to someone in your organisation: Make someone else the owner of your file. Once you introduce separate tenants, a lot of “simple” moves stop being admin flips and become migration work, permission rebuilding and user training.

This is why a split often works best only where the organisational boundary is already real, such as a newly acquired business, a separate legal entity, or a division with little shared-document traffic. If everyone still collaborates in the same Drive folders and calendars every day, a split may save licensing and then quietly create an operating tax that IT carries for years.

• A secondary domain is not the same as a second tenant
• Primary-domain changes affect email, sharing and Meet identities
• Cross-tenant Drive and file ownership issues are usually underestimated

04When moving only mail is the smarter compromise

A mail-only or mail-first redesign is usually worth considering when your user base is mixed. Some staff need the full Google collaboration stack. Others mainly need a mailbox, calendar, mobile access, retention and reliable delivery. If you treat all 280 users as identical, you often end up buying the wrong plan for a big slice of the organisation.

This path can be cleaner than a full tenant split because you are not forcing all documents, chats and sharing patterns to move at once. Google’s migration tooling supports Google Workspace to Google Workspace migration for Gmail, Calendar, Drive, Contacts and Groups, with mappings and phased migration approaches documented in Google Workspace Migrate: Supported and unsupported features, Plan your migration phases, How to map data. Those same documents make an important point for buyers: even inside Google’s own ecosystem, coexistence and migration are projects, not licence toggles.

If you move only mail, be strict about which cohorts qualify. Examples include warehouse and field users who need addressable email but do not co-author docs all day, shared-function accounts, operational mailboxes, or acquired teams that will eventually move to a separate platform anyway. The wrong candidates are executives, sales, legal and project-heavy teams who live in shared calendars, delegated mailboxes, Drive links and external collaboration.

The success measure here is not only monthly licence savings. It is whether the users who stay on Google still have a clean identity experience, whether mail flow is stable, and whether the split reduces spend without creating a helpdesk queue. If your organisation already has cloud and routing complexity, bring your cloud infrastructure team or governance and compliance capability into the design early.

• Choose cohorts by work pattern, not job title alone
• Assume coexistence needs routing, identity and migration planning
• Do not move calendar-heavy or document-heavy users lightly

05Questions to answer before you choose a path

Use this checklist before you ask Google, a reseller or an implementation partner for pricing.

Headcount timing: when exactly will you cross 300, and is that before renewal, at renewal, or mid-term? If you are on flexible billing, Google says you are billed monthly for the number of user accounts you have that month. If you are on annual commitments, the commercial decisions are different: Flexible Plan, Google Workspace pricing.

User segmentation: how many users genuinely need Drive-heavy collaboration, advanced admin controls or premium security features, and how many just need dependable mail and calendar?

Domain strategy: do you already own suitable alternative domains? If not, are you prepared for a primary-domain or brand change project? Google’s own guidance says changing the primary domain affects email addresses and other Workspace services and is an involved process: Change your primary domain for Google Workspace.

Migration scope: if you split tenants, are you moving only mail, or also Calendar, Drive, Contacts and Groups? Google’s migration documentation shows these workloads can be mapped and phased, but each workload adds effort and validation: About Google Workspace Migrate, Google Workspace migration requirements.

Support model: who owns routing, DNS, DKIM, DMARC, mailbox cutovers, coexistence testing, mobile reprovisioning and post-cutover support? This is the point where a specialist mail infrastructure team is more useful than a generic licence reseller.

• Map the next 12 months of hires and contractors
• Classify users by workload, not by department chart alone
• Decide whether your problem is licensing, architecture, or both
• Write down who owns cutover and post-cutover support

06A practical decision rule for Australian buyers at 280

Choose Enterprise if three conditions are true. First, you expect to stay well above 300 users, not just briefly cross it. Second, your teams collaborate heavily across the whole organisation in Drive, Calendar and Meet. Third, the internal cost of running two identity or mail worlds would outweigh the licence saving. In that case, paying more for one tenant is often cheaper overall.

Choose a split-tenant design if your business units are already operationally separate and can tolerate cleaner boundaries than shared daily collaboration. This is often sensible after acquisitions, brand separations or legal-entity carve-outs. Do the design before the cap becomes urgent, because naming, routing and migration sequencing are easier when you are not under renewal pressure.

Choose a mail-only redesign if the root issue is that a meaningful user cohort does not need a full Google collaboration seat, but the rest of the business still does. This gives you a narrower migration, a more targeted commercial outcome and less disruption to knowledge workers who rely on Google-native collaboration.

The mistake to avoid is waiting for user 301 and then treating the problem as procurement only. At 280 users, you still have enough runway to classify users, design domains, test coexistence and decide whether the real problem is licence cap, collaboration architecture, or both. That is the point where a short advisory and design engagement is cheaper than an emergency migration later. SyncTrix helps teams assess and redesign mail infrastructure when this exact threshold starts forcing commercial and technical trade-offs.

• If collaboration is organisation-wide, default to one tenant
• If business units are already separate, a split becomes more realistic
• If only some users need full Workspace, redesign mail before you buy more than you need