GPT Migrator
Agency, business and monetization

Bulk migrating Custom GPTs for a workspace

Last checked October 18, 2026
Short answerAdmins should inventory every GPT, rank by use, migrate in batches, then share each plugin, since reports indicate bulk migration does not copy sharing settings. Verify admin tooling details in OpenAI's own admin documentation.

Plan

  1. Inventory all GPTs with owner, usage and status (template).
  2. Rank by recent use; migrate the most-used first.
  3. Migrate in batches and test each: testing.
  4. Share the replacements to the right groups and tell users.

What OpenAI's guide says about admin tooling

OpenAI's migration guide says admins can migrate selected GPTs in bulk through the ChatGPT Admin plugin by giving GPT IDs or a description of the group; it shows the selection and asks for confirmation. Replacements start private and originals become read-only. Bulk migration does not copy sharing settings, so admins share each replacement or ask the creator to. The admin plugin can also produce a GPT report ordered by use over the last 30 days with owners, migration status and custom actions, exportable to a spreadsheet. Permissions named in the guide include Share plugins and Publish plugins to workspace; Upload plugins is not required for the built-in migration. Read the guide for current wording: official docs map.

Track it

Use the tracker template and the countdown plan. Org-level risks: risk register.

Not sure it is simple enough to do yourself?

Tell us what your GPT does, whether it uses Actions and how many files it has. We will say what will break and what a rebuild involves. The audit is free.

Request a free audit

Related guides

Sources

Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.