How the Google Partner Advantage program is structured, what a Google Partner can resell and manage on your behalf, how billing transfer works without disrupting your team, and an honest comparison of buying direct versus through a partner. This covers Google Workspace, Google Cloud, Google Maps Platform and Chrome Enterprise, written for the person at a company who owns or should own the Google relationship.
Most companies buy Google Workspace through the admin console and never think about it again until a billing question comes up or a migration looms. This guide explains the alternative: the commercial structure behind the Google Partner program, what it means for pricing and support, and the practical mechanics of moving your Google billing under a partner without disrupting anything your team uses day to day.
Google Partner Advantage is Google's reseller and partner program. It governs which companies can resell Google products, under what conditions, and with what obligations toward end customers. There are three tiers in the program: Member, Partner and Premier.
Member is the entry tier. A Member company has completed some basic product training and is authorized to resell, but has not yet built a customer base or demonstrated support capability to Google's satisfaction.
Partner is the mid tier and requires meeting concrete thresholds: a minimum number of Google Workspace or Cloud customers under management, certifications held by staff, and demonstrated customer retention. Scalarly is at the Partner level in the program.
Premier is the top tier, requiring substantially larger customer portfolios, additional certifications, and a track record with Google's more complex product areas. Premier Partners have access to additional Google resources and are typically larger resellers.
What matters to you as a buyer is not primarily the tier. What matters is whether the partner you choose meets the minimum requirements to be authorized, has the technical staff to handle your products, and can support you in your language. The tier is a proxy for these things, but it is worth verifying directly rather than assuming a higher tier automatically means better service for your specific situation.
The program also defines two engagement models: Sell and Service. Sell covers the commercial relationship: the partner handles your licensing, billing and renewals. Service covers implementation work: migration, deployment, configuration and ongoing support. A partner can operate in both modes simultaneously, which is the model we use.
A Google Partner authorized for resell can handle licensing and billing for the following product lines:
Partner-managed billing can also include promotional credits and negotiated terms where Google makes them available to partners for distribution to customers. These are not guaranteed and vary by product, region and Google's current programs. What is guaranteed is that you never pay more than Google list price through an authorized partner.
Google Workspace is Google's productivity suite: Gmail, Drive, Docs, Sheets, Slides, Meet, Calendar, Chat and the underlying Google identity (accounts.google.com). It comes in several editions, and the edition decision is often the first thing a partner should review for a new customer.
The Business tier runs from Starter through Standard and Plus to Enterprise. The qualitative difference as you move up the tier is storage per user, Meet recording and participant limits, security and compliance features, and admin controls. Business Starter is sufficient for small teams that primarily want Gmail and Drive. Business Standard adds Meet recordings and more storage, which matters for distributed teams using video heavily. Business Plus adds audit and eDiscovery capabilities, which is relevant for regulated industries. Enterprise adds more advanced data loss prevention, security center access and custom admin controls.
One of the most common findings when auditing a Workspace subscription is over-provisioning: companies on Business Plus or Enterprise because they hit a feature limit years ago, when the actual usage profile would comfortably fit Standard. The reverse also happens: companies on Starter running out of storage or hitting Meet limits. An honest edition review is the first thing a partner should do, before any migration or support structure is discussed.
Most Workspace migrations come from one of three sources: Microsoft 365, Exchange on-premises, or a legacy shared hosting mail setup. The method differs by source, but the preparation is the same in every case.
Before any mail moves, we inventory the source: mailbox count, size per mailbox, shared calendars, distribution groups, contacts, public folders if any, and any delegated access relationships. This produces a migration specification that gets reviewed and signed off before we touch anything. Migrations that skip this step often hit surprises mid-transfer.
The DNS cutover is the most visible step for end users. Before cutover, new Workspace accounts are provisioned and the pilot batch has been validated. On cutover day, MX records point to Google and new mail routes to Workspace. Historical mail from the source continues transferring in the background for days after cutover. This means users are on Google immediately but continue to see their historical mail appearing in their inbox as it transfers. We communicate this timeline to users in advance so it does not come as a surprise.
For companies migrating from Microsoft 365 specifically: OneDrive and SharePoint content is a separate migration from mailboxes. We handle both, but they are planned and executed separately because the data formats and migration tools differ. Calendar and contacts migrate alongside mail. Teams channel history does not migrate to Google Chat natively; that decision and its implications should be made before the migration plan is agreed.
A freshly provisioned Google Workspace tenant has sensible defaults but not necessarily the right ones for your organization. The minimum we configure on every deployment: 2-Step Verification enforcement across all users, third-party app access policies (which apps can request access to Google data), email routing rules, context-aware access policies for sensitive data, and DLP rules appropriate to the edition. Companies in regulated industries typically need more, but this baseline protects the majority of deployments.
After deployment, the admin work does not stop. Users leave and join, aliases need creating, groups need updating, storage limits need monitoring, and Google pushes product updates that occasionally change default behaviors. Under a Managed engagement, we handle these requests as they come, conduct quarterly reviews of the license count and edition appropriateness, and monitor for security alerts in the admin console that warrant attention.
Google Cloud is a different commercial structure from Workspace. Workspace is a subscription with a fixed per-user price. Cloud is consumption-based: you pay for what you use across compute, storage, networking, databases, machine learning services and dozens of other products. The billing complexity is proportionally higher.
A Google Cloud billing account sits above one or more projects. Each project has resources: virtual machines, storage buckets, Cloud Run services, BigQuery datasets, whatever your workload requires. The billing account accumulates charges from all its projects and pays the invoice. When you move to partner billing, your billing account is transferred to the partner's reseller billing relationship, or a new billing account under the partner is set up and your projects are migrated to it. Either way, your projects, resources, and running services remain live throughout.
Unmanaged Cloud spend is the common problem. A team spins up infrastructure for a project, the project ends, and the resources keep running because no one has visibility into what is still active. Budget alerts at the project level are the first line of defense. Google Cloud's native Billing Budgets feature lets you set a spend threshold per project or per billing account and receive alerts when spend approaches or exceeds it. Setting these up is one of the first things we do when we take over a Cloud billing relationship.
Beyond alerts, cost monitoring involves looking at the right-sizing recommendations Cloud provides in the console for Compute Engine instances, the Committed Use Discount opportunities for predictable workloads, and the Spot or Preemptible instance options for workloads that can tolerate interruption. None of these require architecture changes; they are commercial optimizations on existing infrastructure.
For companies spending on Cloud without a defined architecture, we provide a review: what is running, what is it for, is it appropriately sized, are there obvious waste sources, and what would a cleaner architecture look like. This is not a multi-week engagement. For a typical SMB Cloud setup, a competent review takes two to three days and produces a documented current state plus a prioritized list of changes. The implementation of those changes is a separate engagement, scoped from the review findings.
When does partner billing make most sense for Cloud? When you have Cloud spend you are not actively managing, when you want it on the same invoice as Workspace, or when you need someone who can call Google's technical support on your behalf for infrastructure issues. If you have a dedicated Cloud team and are already using GCP's advanced features with defined cost management processes, direct billing is fine.
Google Maps Platform is the set of APIs that lets developers embed maps, search for places, calculate routes, geocode addresses and do related location work in applications. It is billed on consumption: each API call has a price, and free tier limits apply up to a monthly threshold before charges begin.
The common problems in unmanaged Maps usage: production API keys with no usage caps, leading to surprise billing when traffic spikes; development API keys that were never restricted to development environments and are publicly visible in source code; and multiple API keys across projects with no central view of total spend.
Managing Maps Platform through a partner consolidates the billing and gives you a single contact for quota increases, usage cap configuration, and license questions. If you are building a product on Maps and your usage is growing, having a partner manage the license means you have someone who can engage Google on quota limits without navigating the self-serve quota request process when you hit a wall at a critical moment.
Common Maps API products we see in use: Maps JavaScript API for embedded maps in web apps, Geocoding API for address-to-coordinate conversion, Places API for business search and address autocomplete, Routes API (formerly Directions and Distance Matrix) for route planning, and Maps Static API for map images in emails and PDFs. Each is priced independently and has its own free tier. A usage audit across active keys often reveals consumption from inactive projects that could be shut down.
Chrome Enterprise comes in two distinct forms that serve different needs, and they are often conflated.
Chrome Browser Cloud Management manages the Chrome browser itself on employee devices, whether those devices run Windows, macOS, Linux or ChromeOS. It allows IT to set browser policies centrally: which extensions are allowed, which sites are blocked, certificate management, proxy configuration, data protection settings. The license is per managed user. For companies in regulated industries, where the browser is the primary access point for sensitive systems, managed Chrome is the right tool.
ChromeOS devices are Chromebook hardware or Chrome OS Flex on older hardware. Managing a ChromeOS fleet requires a Chrome Enterprise Upgrade license per device, which enables device-level management: enrollment, kiosk mode, forced app installation, device audit logs. This is a different product from browser management and is licensed separately.
The common starting point is a company running Workspace and wanting to manage the Chrome browser on employee devices without replacing the devices. Chrome Browser Cloud Management achieves this. The setup involves creating a Google Admin console organizational unit for managed browsers, pushing the enrollment configuration via group policy or MDM, and then configuring policies in the admin console. Under a partner engagement, we handle the licensing purchase and the technical setup.
Buying direct from Google is a legitimate choice and there are situations where it makes more sense than a partner relationship. Here is an honest assessment of both sides.
If you are a small team with a single Google product, no migration planned, someone technically comfortable managing the admin console, and you primarily need English-language support, buying direct is simpler. The self-serve admin console is well-documented, Google's support for Business editions is adequate for routine issues, and you avoid adding a commercial intermediary to the relationship.
Pure self-serve Cloud projects with a dedicated DevOps or infrastructure team also work better direct. If you have engineers who live in the Cloud console, understand the billing structure, and have already set up cost management tooling, a partner adds overhead rather than value.
The situations where the partner model consistently outperforms direct buying:
The switch is reversible. If you start with a partner and decide later that direct billing suits you better, Google's transfer process works in both directions. There is no long-term lock-in at the Google product level.
The billing transfer is the step that most companies are nervous about, usually because they assume it involves downtime or disruption. It does not. Here is what actually happens.
The partner initiates a transfer request through Google's Reseller API or partner console. This generates a transfer token. The current Workspace admin accepts the transfer in their admin console. Once accepted, Google moves the billing account to the partner's reseller account. The whole process takes under 24 hours after the admin accepts. Users notice nothing. Gmail, Drive, Meet, Calendar, all running. The only change is that the next invoice comes from the partner instead of directly from Google.
There is a waiting period to be aware of: Google requires that a Workspace customer has been on their current billing arrangement for at least 30 days before a transfer can be initiated. If you just signed up directly and want to move to partner billing immediately, you wait out the 30-day period. This is a Google policy, not something a partner can override.
Cloud billing transfer works differently depending on your setup. If you have a single billing account with projects under it, the partner sets up a new reseller billing account and you move your projects to it. If you have multiple billing accounts, each needs to be transferred or consolidated. The mechanics are slightly more involved than Workspace but still do not affect running services. A virtual machine running on a project that moves billing accounts keeps running. The project ID does not change. Resources do not restart. Only the billing relationship changes.
We document the current state of your projects and billing structure before any transfer, produce a transfer plan, and execute it in a window agreed in advance. For most SMB setups, the transfer completes in a few hours.
This point is worth repeating because it is the question we get most often. The billing transfer is invisible to end users. They open Gmail and it works. They open Drive and it works. Cloud services stay up. Maps API calls go through. The change is entirely in the commercial layer, not in the product layer. The only thing that changes for users is that the invoice their finance team receives is now from Scalarly rather than from Google.
Need Google Cloud and Workspace wired into your CRM and data stack? This guide covers licensing and the partner commercial relationship. If you are looking to integrate Google Workspace with Zoho or Salesforce, or connect BigQuery to your analytics stack, see our Google integration service instead.
That covers the full picture. When you want a specific view of your current Google setup and what a partner relationship would look like for your organization, the next step is a short conversation. No audit process or access required upfront, just a call.
Consolidated billing, the right licenses, migration managed, support in your language. Talk to a Google Partner today.
Talk to a Google Partner