The Gemini Gems to Skills migration gives business customers until at least March 1, 2027, but one part of it should go on your list now. Google says Workspace Studio flows can no longer add an "Ask a Gem" step, and existing ones stop working at that cutoff. On November 17, Gems also move to the Settings panel of the Gemini app. They keep working. If your team built processes around them, the time to plan is while nothing is on fire.
What is changing, and when?
Google laid out the timeline in its Workspace Updates post, first published September 30 and updated October 13.
- Now. You can still create and use Gems in the Gemini app. Workspace Studio flows can't add a new "Ask a Gem" step. Existing ones keep running.
- November 17, 2026. Gems move into the Settings panel of the Gemini app. Users can still create, edit and use them.
- No sooner than March 1, 2027, for business and enterprise. Gems can no longer be created, edited or used. They disappear from Settings. "Ask a Gem" flows stop working. Remaining Gems are auto-migrated to draft skills.
- No sooner than June 1, 2027, for education. The same changes apply. Gems also leave Google Classroom and Gemini LTI integrations.
Google says admins will get at least 30 days' notice before auto-migration.
One caution on timing. The same October 13 update says the Workspace Studio and Workspace app launch of skills is delayed. The Gemini app rollout is under way and expected to finish by mid-November. Check what your domain actually has before you promise anyone a date.
What is a skill, in plain terms?
A skill is a set of reusable custom instructions. You call it inline in a chat thread, and you can stack several in one prompt or use them at different points in a conversation. Skills can be created in the skill builder in Google Docs. They use the open SKILL.md standard, so skills from other platforms can be copied in.
The real change is the shape. A Gem was a separate assistant you went to. A skill is a step you pull into the work you are already doing.
What does this mean for your business?
Your Gems are probably undocumented processes. Someone wrote a Gem that drafts client replies or checks proposals. It works. Nobody else knows the exact instructions, who owns it, or which flows call it. This move forces the question. That is useful, even if the deadline is months away.
The risky part is the flows, not the chat. A person using a Gem in chat will notice when it moves. A flow with an "Ask a Gem" step runs quietly until it doesn't. If anything downstream depends on that step, such as a ticket, an email or a report, the failure could go unnoticed for a while. Find those first.
Auto-migration is a safety net, not a plan. Google says remaining Gems become draft skills. A draft is not a tested process. Nobody should assume a migrated skill behaves the same way in a real workflow until someone has tried it.
You may need two copies. Google says skills do not sync between the Gemini app and Workspace apps. If a team uses the same instructions in both, you will create and maintain them twice. That argues for keeping the source text in one owned place.
How should a business handle the move?
This is the order we would use.
- Inventory. List every shared Gem and every Workspace Studio flow with an "Ask a Gem" step. Add an owner and what breaks if it stops.
- Sort. Keep what people use. Retire the rest. Many Gems were experiments. Don't migrate them.
- Write the instructions down. Copy each keeper into a controlled document. Add its purpose, inputs and an example of a good result.
- Rebuild the highest-value ones as skills manually. Google allows this before auto-migration. Doing it by hand means someone reads the instructions again.
- Test against old outputs. Run the same five inputs through the Gem and the skill. Compare the results with the person who owns the process.
- Replace the flow steps last. Wait until skills are actually available in Workspace for your domain. Then change one flow, watch it, and move on.
- Tell people the dates. Google recommends admins share the key transition dates. A short note before November 17 prevents a wave of "where did my Gem go" questions.
Where are the honest limits?
This is not an emergency. Business customers have months, and the March date is a "no sooner than" date, so it may move.
The post also does not describe the admin controls in detail. It links to a separate help article. Read that against your own console before you plan rollout rights. And a portable format does not mean portable results. A SKILL.md file can move between platforms, but the model and tools behind it differ, so test any skill you bring in.
Finally, if a process matters enough to run a business on, it may not belong inside one chat feature at all. A stable workflow with clear steps, logs and a named owner will survive the next product rename.
Frequently asked questions
Google says no sooner than March 1, 2027, for business and enterprise customers. Admins get at least 30 days' notice before auto-migration.
Gems move to the Settings panel of the Gemini app. Users can still create, edit and use them.
Google says remaining Gems in the Gemini app are auto-migrated to draft skills at the cutoff. Test any migrated skill before relying on it.
You can't add that step now. Existing flows keep working until the cutoff, then stop working.
No. Google says you must create them separately in each.
Sources
Have Gems become part of how work gets done?
We help teams turn loose prompts into workflows with owners, checks and logs. We'll help you sort what to keep, what to rebuild and what to automate properly.
Book an AI Workflow Review
