Gemini Gems Are Becoming Skills: What to Migrate Before Your Deadline

By Si Fisher · Published October 1, 2026

Google is replacing Gemini Gems with Skills. A Skill can reuse your instructions in the chat you are already in and combine them—say, a brand voice plus a report format. If your best Gem is quietly keeping a team workflow from turning into interpretive dance, that flexibility sounds good. First list where each Gem runs, save its instructions and files, then try a replacement in each place you actually use it. The Gemini app and Workspace need separate Skills, and several Gem tools still lack Skill support. Google’s transition guide and Workspace announcement explain the change.

When are Gems going away?

The current Gemini Help page gives removal months by account type, not a precise personal-account shutdown date:

Earlier are rollout milestones in Google’s September 30 announcement: Workspace rapid-release Skills start October 5, scheduled-release October 19, and Gemini-app rollout October 13. It also says Gems move into Settings November 17, where they remain usable. Current Help already reports personal-account Skills availability, so check your own account rather than treating the announced start as a universal switch-on date.

For a team, the first deadline is less useful than the question “Which work would fail if this Gem vanished tomorrow?” I would note the owner, account type, destination, critical files and a safe fallback next to every important Gem. The result can be a short checklist, not a migration war room.

One Gem can need two replacements

Skills are reusable instructions that Gemini can apply in a chat, and Google’s announcement says they can be used across supported Workspace apps. But a Skill made in the Gemini app does not currently sync into Workspace. If you use one Gem both on gemini.google.com and inside Docs, Gmail or a Studio flow, plan two destinations and test each. “I can see it in Gemini” does not mean the teammate drafting in Docs can use it.

A Skill is instruction reuse, not a new power button. Google’s Workspace Studio guidance says it cannot grant a tool a capability it does not already have. Keep the question concrete: can this version still complete the job, with the right files and access, for the people who need it?

If Workspace access or limits are the part holding up your plan, my Google Workspace Gemini limits guide covers that separate account decision. This page handles what happens to the Gem workflow itself.

How I would migrate a useful Gem

1. List and save: record the Gem’s instructions, who owns it, where it is used, who shares it, attached knowledge files, and one real example of a good answer.
2. Choose early manual or later automatic: Google says remaining Gems will be recreated as Skills when Gems go away. The Workspace announcement calls the eventual Gemini-app results draft Skills. That is not the same as an active, tested replacement or a Workspace copy.
3. For an early manual rebuild: on Gemini web, open the Gem and download each knowledge file individually. Create a Skill with its name, description and instructions. If it has no files, that finishes the basic rebuild. If it has files, download the new Skill’s ZIP, extract SKILL.md, place it with the saved supported files in a matching lowercase-hyphen folder, then use Replace skill → folder to upload the collection. Google gives the current steps. Manual creation in the Gemini mobile app currently has a save issue, so use web for this route.
4. Build a Workspace copy separately if the work lives there. Check your edition, admin availability, sharing and the actual app before promising it to the team.
5. Try the same sample task: compare factual accuracy, formatting, file use and permission boundaries between old and new. Keep the Gem until the new path works for its real users.

This is an editorial migration checklist based on Google’s documentation, not a claim that I tested a real Gem portfolio. For a low-stakes personal Gem, manual rebuilding now may be simple. For a shared workflow or regulated client material, assign a human owner and preserve the fallback.

What might not carry over?

Google says supported files can be moved when it automatically transitions Gems, but GitHub files are not currently supported in Skills. For manual migration, each Gem knowledge file must first be downloaded individually, though the prepared folder can be uploaded together. Its transition Help also says most default Gem tools do not yet work with Skills, including Canvas, Deep Research, Create video, Create music and Guided Learning. Google expects additional features later; there is no reliable parity date for every workflow.

Do not delete the original after a pretty-looking first answer if it relied on one of those tools. Document the unsupported step, choose a manual or alternate-tool fallback, and retest when Google changes support. A Skill with the same name may still produce a different result.

If you use Workspace Studio flows, check this separately

Google’s Studio migration Help says you can no longer add an Ask a Gem step to a new or existing flow. Existing steps still run for now, but that Help says flows with an Ask a Gem step stop working starting March 2027. Google’s September 30 announcement gives education accounts a later, no-sooner-than-June-1 milestone that also includes Studio flows. Education admins should confirm the applicable notice rather than assume the March date is universal. Replace Ask a Gem with Ask Gemini; if Skills are available, attach the relevant Workspace Skill. Test the replacement and update any later steps that used the old Ask a Gem output variable. Otherwise the flow can break even when its new answer looks fine.

If Workspace Skills have not appeared for your account, Google’s guidance also describes replacing Ask a Gem with a standard Ask Gemini step. That is a fallback worth testing, not automatic proof that the old Gem’s custom behavior survived.

Quick questions

Will Google automatically turn my Gems into Skills?

Google says it will recreate remaining Gems as Skills when Gems are removed. Its Workspace announcement describes those Gemini-app results as drafts. Review files, behavior and activation, and rebuild separately in Workspace if needed.

When will my Gems disappear?

Google’s current Help lists November 2026 for personal accounts, March 2027 for business, enterprise and nonprofit accounts, and June 2027 for education accounts. The exact personal November day is not published in that Help page; check your account and admin notices.

Does a Gemini-app Skill appear automatically in Workspace?

No. Google’s Workspace announcement says Skills currently do not sync between the Gemini app and Workspace apps. Recreate and test a separate Workspace Skill where your team’s work happens.

Sources and method

I checked Google’s current Help pages and its dated September 30 Workspace announcement on October 1, 2026. Current Help controls the manual steps and account visibility; the announcement supplies planned rollout milestones. This guide is documentation-based; I did not migrate a Gem portfolio or test feature parity. Corrections: hello@theprotoolkit.com.

• Google Gemini Help, Gems-to-Skills transition (checked October 1)
• Google Gemini Help, create and manage Skills (checked October 1)
• Google Workspace Updates, Skills and Gems announcement (dated September 30)
• Google Workspace Studio Help, replace Ask a Gem flows (checked October 1)

Update log: October 1, 2026 — initial migration guide. Recheck rollout, account deadlines, unsupported features and Studio guidance before a team cutover.