Software & productivity · Inquory Research

Google starts the Gems-to-skills rollout: identify the account and flow before migrating

Map the account, application surface and downstream flow before migrating Gems to Gemini skills; rollout dates and conversion rules differ.

· Announcement September 30 · Sources checked October 7 · AI-assisted research and drafting · Editorially reviewed · No tested migration or account availability

Three separate trays hold a personal notebook, an office folder and a paused chain of task cards beside an open review notebook.
Account, application and workflow changes need separate checks. This conceptual illustration does not depict Google software, a tested migration or a customer outcome.

A conceptual planning desk separates a personal account, a managed Workspace surface and a paused downstream flow. It does not depict Google software, an account test, a completed migration or a customer outcome.

AI-generated editorial illustration · Inquory

By Inquory Research

Published October 7, 2026. Announcement date: September 30, 2026. Sources checked: October 7, 2026. AI-assisted research and drafting with editorial review. Inquory has not tested this migration or verified availability in a customer account.

Google's transition from Gems to reusable Gemini skills now has an active Workspace rollout. For a small business using custom instructions and automated flows, the immediate job is to identify which account and workflow each deadline belongs to. A converted instruction set is only one part of that inventory.

The rollout is under way, with different calendars

Google's September 30 Workspace announcement says Rapid Release rollout began October 5, with expected completion October 12. Scheduled Release starts October 19 and is expected to finish by mid-November. The Gemini app rollout for Workspace accounts starts October 13, also targeting mid-November. These are rollout windows, not proof that a particular account has access. The announcement says skills in the Gemini app and Workspace currently do not synchronize. Google Workspace announcement

Google's separate consumer announcement says personal-account Gems will start disappearing in November. It also says Opal will turn down in November and, separately, that Gems by Google Labs will not migrate to skills. Those notices should not be used as the deadline for a company's Workspace account. Google's consumer announcement

For business and enterprise Workspace users, the administrator guide sets removal no sooner than March 1, 2027; for education, no sooner than June 1, 2027. Gems move into Gemini app Settings on November 17 while remaining usable. The guide says automatic conversion produces inactive draft skills, which creators must review and activate. Google says names, descriptions, instructions and uploaded knowledge files will be preserved, with existing Drive sharing permissions carried over. These are documented migration plans, not observed results from Inquory. Administrator transition guide

A working flow needs its own check

Workspace Studio's help page says new Ask a Gem steps can no longer be added, including to existing flows. Existing steps remain functional and editable until deprecation. It warns that flows using them will stop working starting March 2027 and describes replacing the step with Ask Gemini, then updating later steps that reference its output. Its general March warning is less specific than the administrator guide's account-specific dates; confirm the applicable notice before planning a change. Workspace Studio transition instructions

Inquory interpretation: an instruction migration and an automation migration need separate acceptance records. A successful answer in a chat does not establish that the next action in a flow receives the correct value, reaches the intended recipient or respects the same review boundary.

For a Canadian service business, this could matter when a flow prepares an estimate, labels an incoming enquiry or drafts a customer reply. The relevant consequence is operational: an unnoticed dependency can interrupt that handoff. We have no measured failure rate, time savings or customer-outcome evidence for this transition.

Build a private transition ledger

Keep this inventory in a document you control. Use neutral labels instead of customer names, live prompts, email addresses or confidential files.

Evidence to capture before changing an account, application surface or workflow
RecordEvidence to captureDecision it supports
Account and ownerPersonal or managed account; named responsible roleWhich notice applies, and who can check it?
Application surfaceGemini app, Workspace side panel or Studio flowDoes another surface require a separate copy?
Current instructionVersion label and approved reference-file listWhat must the reviewed replacement retain?
Downstream dependencyStep names and expected output fieldsWhat might break after the instruction changes?
Controlled acceptanceFictional input, expected result and actual observationHas the replacement met the task's criteria?
Recovery decisionOriginal version, authorized restorer and stop conditionHow will work continue if the test fails?

This is an editorial planning aid. It does not authorize anyone to edit a production flow, change sharing or activate a skill. Use an approved test copy with external actions disabled where your organization's controls allow one, and keep the working version available until its responsible owner accepts the replacement.

Fictional example: one prompt, two unfinished checks

Mara runs a fictional repair business. She has a personal Gem for writing ideas and a managed Studio flow that drafts enquiry responses for human approval. She records them as two entries. After a replacement draft produces a plausible reply, she still marks the flow check incomplete: the next step needs the correct output field, and no customer message may leave the test. Her acceptance criterion is a draft reaching the designated internal reviewer with the fictional case details intact. This example is not a real customer, migration or successful test.

What remains uncertain

The Workspace announcement lists Enterprise Starter for Workspace skills; the administrator guide's edition list omits it. Inquory has not resolved that discrepancy. Check the current edition-specific documentation and your administrator before assuming access or purchasing anything. The administrator page has a September 30 content date and an October 7 UTC footer update; neither proves account rollout completion.

Studio's sharing instructions also say a copied skill can include referenced files, text, email addresses and flows, and that a link exposes the creator's email address. Inspect the actual share contents and intended audience before distributing a migration aid.

All four sources are Google publications. They explain Google's announced behaviour; they are not independent evidence of reliability or completed migration. This report makes no pricing, universal availability or performance claim.

Related reading