Gemini Gems Become Skills Only Their Creators Can Switch On

If your company runs real work through Gemini Gems, the automatic migration Google has promised will not keep that work running. Starting no sooner than March 1, 2027, Business and Enterprise users lose access to Gems, and the ones left behind are converted to skills that arrive as "inactive drafts" which their creators must review and activate, according to Google's admin guide to the transition. Workspace Studio flows built on an "Ask a Gem" step stop working on the same timeline. The job for a Workspace admin this quarter is an inventory: which Gems matter, who owns them, and which automations call them.

Skills began rolling out to Rapid Release Workspace domains on October 5, 2026, with Scheduled Release domains starting October 19 and the Gemini app following from October 13, per Google's Workspace Updates announcement of September 30. That gives most organizations about five months between the announcement and the earliest cutoff.

What Google Is Actually Changing

A skill is a reusable set of instructions that Gemini applies when you call it, and it replaces the Gem as Google's way to tailor Gemini for a specific task. The Workspace Updates post describes skills as instructions you can use "any time you're prompting Gemini in the Gemini app and most Workspace apps," and says users can stack several skills in one prompt, which Gems could not do.

Skills also change the file format. They follow the open SKILL.md standard, a Markdown file with a name, a description and instructions, which the Agent Skills project says Anthropic originally developed and released as an open standard. That project lists Gemini CLI, Claude, GitHub Copilot, Cursor and Codex among the clients that read the same format. For an admin, that portability cuts both ways: a skill written for Gemini can be downloaded as a .zip per Google's Gemini Apps help page and loaded into another vendor's assistant, including Claude or Gemini CLI.

The dates, from Google's admin guide:

Date	What happens
October 5, 2026	Skills start rolling out in Workspace (Rapid Release; complete by October 12)
October 13, 2026	Skills start rolling out in the Gemini app
October 19, 2026	Scheduled Release Workspace domains start getting skills
November 17, 2026	Gems move into Settings in the Gemini app
No sooner than March 1, 2027	Business and Enterprise users lose Gems; remaining Gems auto-migrate to draft skills; Ask a Gem flows stop working
No sooner than June 1, 2027	The same for Education users

Android Authority's reading of the timeline adds that after November 17, users can still create, edit and use Gems from the Settings panel, so nothing breaks this year. The pressure arrives in the spring.

---

Why Migrated Gems Will Sit Switched Off

Migrated Gems will not work until a named person turns each one on. Google's admin guide says converted Gems keep their names, descriptions, instructions and knowledge files, and that Drive permissions and sharing settings transfer to the new skills, but each one lands as an inactive draft and its creator must review and activate it.

That design is defensible. A Gem written in 2025 may carry instructions nobody has read since, and a forced review stops stale prompts from spreading through a new surface. The cost is that the migration's success depends on every creator showing up after March 1 and clicking through a list of drafts.

Three groups of Gems are likely to fall through:

1. Gems whose creators have left. Google's transition guide does not say what happens to a Gem whose creator's account is suspended or deleted, and its user deletion guide lists only Drive and Docs files, primary Calendar data and Data Studio data as transferable during deletion. Shared Gems are stored in a Drive folder, and Drive files can be moved with an admin ownership transfer, but no Google document we found confirms that a transferred Gem file becomes a working Gem, or an activatable draft skill, for its new owner. Treat that as unknown until Google says otherwise.
2. Gems used by a team but owned by one person. Viewers of a shared Gem can only use it and see its contents, per Google's Gem sharing help. Google's Workspace Studio transition guide tells someone whose flow used a view-only Gem to "reach out to the owner so they can share the skill with you instead." If that owner is on leave in March, the team waits.
3. Gems nobody remembers. A draft that nobody activates fails quietly: the people who relied on it see different output and no error message.

The fix for all three is the same, and it is cheap while the creators are still around: have each owner of a business-critical Gem transfer ownership to a team account or a second named owner now. Google's sharing help confirms owners can transfer a Gem to anyone who already has access, with one caveat: the new owner can then remove the old owner's access.

Which Workflows Break First?

Workspace Studio flows break first, because migrated skills do not go where those flows run. Google's guide states that "skills don't sync between the Gemini app and Workspace apps," and that to transition Gems used in Workspace, "users must manually recreate them in Google Workspace Studio." The automatic conversion targets the Gemini app. Any Gem feeding an automation has to be rebuilt by hand.

The Ask a Gem step only arrived in April. Google announced it on April 22, 2026 as a way to have flows "send a prompt to private Gems to automate tasks like creating summaries or writing documents," though Gems with Google Photos or other non-Drive files in their knowledge base never appeared in Studio. Six months later it is already closed to new flows, per the Workspace Updates post. The Workspace Studio guide says existing flows "remain fully functional and editable until deprecation," and from March 2027 they stop working.

The replacement is mechanical. Per that guide, a flow owner copies the prompt, adds an Ask Gemini step above the old one, attaches a Workspace Studio skill if they have skills access, deletes the Ask a Gem step, and then repoints every later step that read the old step's output variable to the new one. That last step is where flows fail silently. A summary step that still points at a deleted variable will run and produce nothing useful.

Admins also control whether anyone can build Workspace skills at all. The setting lives under Apps, Google Workspace, Workspace Studio, Skills in the Admin console, can be scoped by organizational unit or configuration group, and takes up to 24 hours to propagate, per Google's skills admin page. The same page says that when the setting is off, "users can't use any existing skills." If a pilot group owns your critical flows, check that it has skills turned on before asking it to rebuild.

---

Five Months Is Short by Google's Own Standard

Google gave Jamboard users fifteen months; it is giving Gems users about five. When Google announced the Jamboard wind-down on September 28, 2023, editing ended October 1, 2024 and files were deleted December 31, 2024, and Google promised paths to migrate into FigJam, Lucidspark or Miro. The Gems notice runs from September 30, 2026 to no sooner than March 1, 2027.

The steel-man for Google is real. Gems are prompts and a few files, not years of whiteboards, and the auto-migration keeps the content. "No sooner than" also means the date can slip later, never earlier. And moving to SKILL.md puts Google on the same format as other assistants, which lowers your switching cost, a point worth remembering next time you compare Gemini Enterprise and ChatGPT Work.

What the short window does is shift work onto the customer. The migration preserves instructions but leaves activation to individuals and leaves Workspace automations to be rebuilt by hand. The same gap showed up when OpenAI rolled out skills in ChatGPT, and in how ChatGPT Space handles inherited access: the vendor ships the object model, and ownership hygiene is left to you. It also fits the pattern in our look at model deprecation notice windows, where the notice period is whatever the vendor decides unless your contract says otherwise.

What to Do Before the March Cutoff

The work splits cleanly into inventory now, rebuilds this winter, and verification before March.

This Week:

1. Confirm whether your domain is on Rapid or Scheduled Release, and check the Workspace Studio skills setting for the organizational units that own your automations.
2. Ask Workspace Studio flow owners to list every flow with an Ask a Gem step. New ones cannot be created, so the list is closed and finite.
3. Send the dates to users in plain language. Google's own admin checklist starts there.

This Month:

1. Build a register of business-critical Gems: name, creator, current users, whether it feeds a flow, and whether the creator is still employed. Ask team leads, because there is no single admin report of Gems in the documentation we found.
2. For every Gem whose creator is leaving or has left, get ownership moved to an active account while that is still possible, and test whether the new owner can edit it.
3. Rebuild the top ten flows with an Ask Gemini step plus a Workspace Studio skill, and re-check every downstream variable reference.

Before March 1, 2027:

1. Add "transfer Gem and skill ownership" to your offboarding checklist next to Drive transfer, which has to happen before or, for super admins, during deletion.
2. Ask your Google account team, in writing, what happens to a migrated draft whose creator is suspended or deleted. Put the answer in the register.
3. Export the instructions for your critical skills as SKILL.md and keep them in a repository you control. If you ever need them in another assistant, or the same problem recurs, the file is already portable. Our AI vendor exit clauses guide covers what to ask for on renewal.

The Bottom Line

Google is moving its custom assistants onto a portable file format, and the move is sensible. The risk is in the handoff: drafts that wait for a creator, and flows that have to be rebuilt in another tool. Organizations that treated Gems as personal productivity toys will lose little. Teams that wired Gems into Workspace Studio automations, like the ones IBM found hard to upgrade across an agent fleet, have a hard date and no automatic rescue.

Start the register with the Gems owned by people who have already left.

Continue Reading

• OpenAI Ends ChatGPT's $670K Shadow AI Tax: Skills Decoded
• ChatGPT Space Revokes a Page Invite but Not the Inherited Access
• Model Deprecation: Bedrock Keeps Claude 4 Months Past Anthropic
• AI Vendor Exit Clauses: Standard Terms Give 0 to 90 Days to Get Out
• Google Gemini Enterprise vs. ChatGPT Work: Pick Wisely
• Antigravity's Allowlist Isn't Honored. Use Your Proxy.