If your Google Workspace tenant is sitting around 260 to 295 users, the question is no longer whether the 300-user limit matters. It is when it becomes a procurement problem, and whether you want to solve it with contract timing or infrastructure work. Google’s current documentation says Business editions are for 1 to 300 users, while Enterprise has no minimum or maximum user limit. On the commercial side, Google’s current billing rules say a Flexible Plan bills monthly and lets you remove users at any time, while an Annual or Fixed-Term Plan commits you for one year or more, lets you add licences, but generally only lets you reduce them at renewal. That creates a narrow decision window. At 260 users, you still have room to buy time. At 295 users, one hiring round, acquisition, or domain consolidation can push you into an edition change you may not want yet. For most Australian IT teams, the real choice is this: lock one more annual term if headcount is stable and you still need the full Workspace bundle, or start a phased mail-only exit now if Gmail is the expensive dependency and the rest of Workspace is still fit for purpose. This post focuses on sequencing, trade-offs and what to ask internally before user 301 becomes a contract event. It also sits alongside our related reads on what actually happens at user 301, whether annual or flexible makes sense when headcount may cross 300, and whether moving only mail off first is the cleaner path.
01What changes at 300 users, and what does not
The hard boundary is plan eligibility, not service continuity in the abstract. Google’s Business editions are positioned for 1 to 300 users, and the public pricing page repeats that Business Starter, Standard and Plus can be purchased for a maximum of 300 users. Enterprise is the edition family with no maximum user limit. For an IT and finance team, that means the issue is less about whether Google can technically host mailbox 301, and more about whether your next commercial move forces a different edition or negotiation path.
What does not automatically change is every workload at once. Business Plus still includes Vault at no additional cost, plus 5 TB pooled storage per user and Business-level controls listed on Google’s comparison pages. If your dependency on Workspace is really Gmail, Calendar and retention, then moving only mail first can be a rational response. If your dependency is broader, for example Drive-heavy collaboration, Meet at scale, endpoint management or Vault-centred legal hold processes, the migration case gets more complicated and the annual renewal can still be the cheaper short-term decision.
The practical point is this: the 300 threshold is not just a licensing fact. It is a sequencing trigger. Once you are in the high 200s, procurement, infrastructure, identity, compliance and HR planning all need the same forecast, because the wrong team discovering the problem first usually means a rushed renewal or a rushed migration.
- Treat 300 as a contract and architecture trigger, not just a licence count
- Check whether growth is organic hiring, M&A, seasonal workforce change, or domain consolidation
- Separate Gmail dependency from wider Workspace dependency before you compare options
| If this is true | Annual term is usually stronger | Mail-only exit is usually stronger |
|---|---|---|
| Headcount likely stays below 300 for 9 to 12 months | Yes | No |
| You need Vault, Drive and Meet as an integrated stack | Yes | Possibly later |
| You expect to cross 300 within one or two hiring cycles | Risky | Yes |
| You only need Gmail and calendar to move off first | Not ideal | Yes |
| Finance wants a known one-year cost and no migration project this quarter | Yes | Maybe not |
| Infrastructure can run a staged migration over batches | Maybe | Yes |
02The cost logic behind annual versus flexible
Google’s published billing comparison is blunt. On the Flexible Plan, Business Plus is listed at USD 26.40 per user per month. On the Annual or Fixed-Term Plan, it is USD 22 per user per month, or USD 264 per user per year. Google’s public pricing page similarly presents Business Plus at USD 22 on annual commitment, with all plans billed monthly and Business plans capped at 300 users.
For a tenant in the 260 to 295 range, that difference is material. The published gap between Flexible and Annual for Business Plus is USD 4.40 per user per month. At 280 users, that is about USD 1,232 per month, or about USD 14,784 over 12 months. At 295 users, the gap is about USD 1,298 per month, or about USD 15,576 over a year.
That saving is real, but so is the lock-in. Google states that on an Annual or Fixed-Term Plan, you can add licences as needed, but if you cancel before renewal you are charged for the remaining balance and no refunds are issued. You can reduce licences only when renewing the contract. So the annual option buys unit-price certainty, not agility.
For finance, the question is straightforward: is the annual saving larger than the cost of delay if a mail-only exit is probably needed anyway? For infrastructure, the better question is: do we want the next 12 months to be a controlled migration runway, or an accidental wait state that ends with an Enterprise negotiation under time pressure?
- Use annual pricing to save money only if the commitment period matches a real plan
- Use flexible pricing if headcount could reverse, seasonal seats matter, or the architecture decision is due within months
- Model the saving against the likely cost of a delayed migration, not against zero
03When a mail-only exit is the better move
A mail-only exit becomes attractive when Gmail is the workload pushing spend and plan risk, while Drive, Meet and the broader collaboration layer are still acceptable. This is especially true where the business does not need the Enterprise-only controls that Google markets higher up the stack, such as data regions on Enterprise and other Enterprise-only controls shown on the pricing page, including data loss prevention, context-aware access and Enterprise endpoint management.
In other words, if the organisation mainly needs mail, calendar continuity, legal retention and identity integration, moving email first can reduce urgency without forcing a whole-platform replacement. A mail-only exit also narrows the project. You are not trying to re-home every shared drive, chat space and meeting workflow at the same time. You are isolating the most contract-sensitive workload and deferring broader collaboration change.
This phased model has another benefit. Microsoft documents that Google Workspace migrations to Microsoft 365 can be done in batches, which supports staged cutover by department, domain or risk profile. Microsoft’s migration guidance also lists key limitations, for example shared calendars and event colours are not migrated, a maximum of three email addresses per contact are migrated, and Microsoft recommends disabling MRM and archival policies before migration to avoid apparent data loss. Those caveats matter because they tell you a mail exit is operationally manageable, but not zero-effort.
For teams thinking in phases, this is the right comparison: not annual versus full migration, but annual versus starting the mail work now while keeping collaboration workloads where they are. If you need help designing that split, this is exactly the type of planning covered in our mail infrastructure work and adjacent cloud infrastructure support.
- Choose mail-only exit when Gmail is the cost and cap driver
- Keep Drive and Meet in place if they are not the immediate problem
- Run migration in batches, not big-bang, unless your tenant is unusually simple
04What the project really involves
A mail-only exit is smaller than a whole-suite move, but it still has real engineering and operational tasks. First, identity and routing need to be untangled. You need a clear design for primary mail flow, accepted domains, coexistence, directory sync if used, and mailbox provisioning for each migration batch. Second, retention and legal hold need to be mapped. Business Plus includes Vault, and Google warns that if you delete a user, all data associated with that account is removed. Google’s own recommendation on the Vault page is to suspend user accounts instead of deleting them.
Third, leaver handling needs attention. Google’s admin documentation says Archived User licences are available for Business editions, and on the Flexible Plan you are charged as you archive users, while on the Annual Plan you may need to purchase more Archived User licences. If you transition your Google Workspace subscription, Google also says you need to transition the Archived User subscription to match before archiving more users. That matters in a phased exit because historical retention often survives long after active mail migrates away.
Fourth, migration tooling and verification need to be planned. Microsoft’s guide supports batch migration of mail, rules, calendar and contacts, but with limitations. You need sample users, message-size checks, a rollback decision for failed batches, and a reconciliation method for sent mail, delegated access, mobile reconfiguration and cutover communications.
None of this is huge for a competent team, but it is not something to start four weeks before a renewal deadline. If you are already in the high 280s, the sensible move is to run discovery immediately, even if the board later chooses an annual extension.
- Map routing, domains and coexistence before you pick batch dates
- Define retention and archive handling for leavers before you move active mail
- Test delegated access, mobile clients and large mailboxes early
- Put procurement dates and technical dates on the same timeline
05Questions finance, infrastructure and legal should answer before signing anything
The best decision usually comes from five short internal questions, not a long architecture deck.
One, when will you realistically hit 300 active users, using named headcount assumptions by month, not a static HR estimate. Two, if you sign annual now, is that because it is the right operating model for the next 12 months, or because nobody has scoped the exit. Three, which workloads actually require Workspace after mail moves, and who owns each one. Four, what retention, eDiscovery and former-staff access must be preserved, given that Business Plus includes Vault and archived-user handling has edition-matched licensing rules. Five, can your target platform support staged migration limits and coexistence constraints that Microsoft documents for Google Workspace migrations, including batch-based moves and the listed migration limitations.
If you are using a partner, ask sharper questions than 'Can you migrate us?'. Ask them how they would keep legal hold intact during a phased move. Ask how they would handle users with very large mailboxes, delegated mailboxes, mobile devices and mixed-domain routing. Ask what signals would make them recommend staying annual for one more term. Ask what cannot be migrated cleanly and how they validate success. If they only talk about tools, not sequencing and exceptions, they are probably selling execution before they have understood the risk.
- Do not approve annual terms without a dated headcount forecast
- Do not approve migration without a retention model for former staff
- Do not accept a vendor plan that lacks coexistence, rollback and verification steps
06A practical recommendation for Australian teams at 260 to 295 users
If you are below about 270 users, have stable headcount, and still depend materially on Gmail, Drive, Meet and Vault as one stack, locking one annual term can be reasonable. Google’s annual pricing for Business Plus is lower than flexible, and the published differential is large enough to matter over a year. But that choice only makes sense if you use the term deliberately, for example to align with a later collaboration review, a merger integration date or a broader workplace tooling decision.
If you are above about 280 users and growth is still active, do not treat annual renewal as the default safe option. The closer you are to 300, the more likely it is that a people event, not an IT event, decides your platform timeline. In that zone, a mail-only exit is often the better move because it attacks the workload most tied to plan pressure while avoiding a rushed whole-suite transformation. This is especially true if Enterprise-only controls, such as data regions or context-aware access and DLP, are not what you are actually buying.
The practical sequence for most teams is simple: confirm the month you may cross 300, map your renewal date, scope a mail-only coexistence design, test a small migration batch, then decide whether annual terms are buying meaningful time or just masking delay. If your team wants help running that sequence, SyncTrix can support the mail and surrounding platform work through our mail infrastructure service and, where needed, related governance and compliance planning.
- 260 to 270 users, stable growth: annual can buy a controlled year
- 280 to 295 users, active growth: start the mail-only plan now
- Use the next renewal as a milestone, not a surprise
Sources
- Compare Business editions | Getting started | Google Workspace Help
- Compare Flexible and Annual/Fixed-Term payment plans | Billing & subscriptions | Google Workspace Help
- Compare Flexible Pricing Plan Options | Google Workspace
- Perform a Google Workspace migration to Microsoft 365 or Office 365 | Microsoft Learn
- Google Vault: Data Loss Prevention & Retention | Google Workspace
- Add Archived User licenses | Billing & subscriptions | Google Workspace Help
- Data regions: Control geo-location of data | Google Workspace
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.