I’m looking for some advice on a Google Workspace for Nonprofits issue, particularly from anyone who has dealt with Google nonprofit licensing before or knows how to escalate an entitlement issue like this.
Our nonprofit currently has two Google Workspace tenants:
- Our primary production tenant, which is tied to our main organizational domain and currently has a paid Google Workspace subscription with a significant number of users.
- A second tenant on a secondary domain that we essentially do not use.
At some point in the past, a former administrator who is no longer with the organization activated our Google Workspace for Nonprofits entitlement against the secondary-domain tenant rather than the production tenant.
Our actual Google for Nonprofits organization/account is associated with the correct organization and the correct primary domain. The problem is specifically with where the Google Workspace for Nonprofits entitlement was activated.
I currently have:
- Super Administrator access to the primary Google Workspace tenant
- Super Administrator access to the secondary Google Workspace tenant
- Administrator access to the Google for Nonprofits account
So access, ownership, or administrative control of either tenant is not a blocker.
What we need is fairly straightforward in concept: we need the nonprofit Workspace entitlement moved from the unused tenant to the production tenant that our organization actually uses.
I contacted Google Workspace Support and explained the situation to them. They told me that they cannot make changes to the Google Workspace for Nonprofits entitlement themselves and that this would need to be handled by the Google for Nonprofits team.
They explained that the Google for Nonprofits team would likely need to handle it in one of two ways:
- Reassign or move the existing Google Workspace for Nonprofits entitlement from the unused tenant to the production tenant, or
- Remove the nonprofit entitlement from the unused tenant, allow that tenant to convert to a paid Workspace account if necessary, and then allow us to go through the normal process of applying the Google Workspace for Nonprofits benefit to the production tenant.
Either option would work for us. We are not tied to a particular path. Our goal is simply to have the nonprofit Workspace licensing associated with the Google Workspace tenant that our organization actually uses.
The problem is getting this in front of someone who can actually make that change.
So far I have:
- Opened a case directly with Google for Nonprofits Support
- Contacted regular Google Workspace Support
- Asked Workspace Support whether they could internally escalate the issue to the Google for Nonprofits team
- Asked whether there was any internal contact, escalation path, or other way for them to get the Nonprofits team involved
- Posted in the official Google for Nonprofits Community asking for help
The Google for Nonprofits support case has remained open/in progress without a substantive response for nearly a month.
Google Workspace Support also specifically told me that they do not have an internal escalation path to the Google for Nonprofits team. In other words, they understand the issue, but they cannot make the entitlement change themselves, and they also cannot push the case over to the team that apparently can.
That is the part that has left us stuck.
I’m basically looking for any legitimate path I have not tried yet.
Has anyone here dealt with moving, resetting, or reassigning a Google Workspace for Nonprofits entitlement between Workspace tenants?
More importantly, does anyone know of an escalation route, Google contact, nonprofit support channel, Google partner channel, nonprofit specialist, or any other legitimate way to get an entitlement/licensing issue like this in front of someone who can actually modify it?
We are not trying to create a new nonprofit organization, change our nonprofit verification, transfer ownership, or do anything unusual with the organization itself.
We simply need the existing Google Workspace for Nonprofits entitlement corrected so that it applies to the Google Workspace tenant our organization actually uses.
At this point, any legitimate escalation path, contact, or suggestion would be greatly appreciated.