In this guide
The change today
Google's published Workspace timeline marks November 17, 2026 as the day Gems move into the Gemini app's Settings panel. Users can continue creating, editing and using them. A missing shortcut should not be mistaken for the immediate loss of a team's custom assistant.
The transition announcement sets later replacement windows: no sooner than March 1, 2027 for business and enterprise, and June 1 for education. These are earliest dates, not a promise that every account will change on those days. Check the guidance for your account type; do not apply a Workspace date to an unrelated consumer product such as Opal.
This is a November 17 analysis of Google's published schedule. We have not observed the change inside a customer account.
What replaces the old workflow
Google describes skills as reusable instructions that can be combined within a conversation. Its administrator guidance says skills do not automatically carry between the Gemini app, Workspace and Gemini Enterprise. Plan for separate copies where necessary.
The guidance also distinguishes migration from activation: automatically converted Gems are expected to become drafts that need review. Workspace Studio flows using Ask a Gem need their own transition work. Do not assume that moving a set of instructions repairs every connected workflow.
Start with an inventory, not a mass rewrite
Our recommendation is to list the custom assistants people actually use, the person responsible for each, and the task it performs. Separate a weekly client-report helper from a one-off experiment nobody needs again. Preserve the important instruction text and note any files or dependencies it expects.
For each essential assistant, write a small acceptance example. A report helper might need to retain three supplied figures, flag a missing date and avoid inventing an explanation for declining results. Run the same example before and after recreating the instructions. Compare the substance, not whether the new answer uses identical sentences.
Assign an owner to resolve conflicting copies. If two teams maintain different versions of a brand instruction, a platform migration is a good moment to discover that disagreement before it becomes customer-facing copy.
What needs attention first
Prioritize flows tied to deadlines or external communication. Keep a manual fallback and record where the replacement lives. A team should be able to find the current instructions without depending on the person who originally wrote them.
Use the workflow planner to document the handoff and the subscription audit if the transition prompts a wider tool review. There is no reason to buy another assistant merely because a menu moved. The practical job is to preserve useful behavior and verify that it still works where your team needs it.
Transparency
How this guide was checked
About this article
How this article was prepared
- Evaluation type
- Source-based research
- Last reviewed
- Evidence
- 2 listed sources
We label hands-on testing separately. Research-based articles draw on product documentation and other cited sources, rather than direct use of every plan. Read the full methodology.
Editorial basis
Sources and testing
- Editorial basis
- Source-based research
- Primary references
- 2
- Products covered
- 0
- Last checked
- 2026-11-17
Important limits
- • Features, availability and prices can change. Check the provider’s current terms before buying.
Sources and references
References cited by this article. Check the original source for scope, dates and current terms.
Frequently asked questions
Are Workspace Gems shut down on November 17?
The published timeline says they move to Settings and remain usable.
Do skills automatically sync across Google products?
The checked guidance says they must be built separately across the named surfaces.