AI Content School · Live Beginner Workshop

CustomGPT to Skills & Plugins

Your Custom GPTs are going away. I'll show you what to do with them.

Mike Wayne · [Day, Date] · [Time] ET · Live on Zoom

Today's plan

In 90 minutes, you'll know what to do with your GPTs

01

Which GPTs to migrate first

02

How the migration works

03

Where your instructions go

04

Where your knowledge files go

05

What a Skill actually is

06

What a Plugin actually is

07

What does not move

08

How to test the replacement

Part 1

Custom GPTs are going away

What happens to everything you already built.

The dates

You have time. Don't wait until the last week.

Migration rolling out now

The Migrate to plugin option is appearing account by account.

Oct 26, 2026

Planned end of creating new Custom GPTs.

Dec 11, 2026

Custom GPTs are scheduled to retire.

Feb 11, 2027

Later date for Enterprise workspaces with an approved deferral.

OpenAI's current schedule. Dates can change, so follow the notice in your own account.

If you built Custom GPTs

Good. You're not starting over.

Your GPT already holds the hard part: what you wanted the AI to know and how you wanted it to behave. The new system organizes those pieces differently.

What moves

Where each part of your GPT lands

In your Custom GPTIn the new Plugin
Your GPT instructions→A Skill inside the plugin
Your knowledge files→The plugin's reference files
Your connected apps→Apps inside the plugin

Migration uses your GPT's latest published version. Drafts and unpublished edits stay behind.

What doesn't move

Clicking Migrate is not the whole job

Custom actions

They don't transfer. Anything built on them stops working until you set up a replacement.

Your old conversations

Chat history with the GPT stays with the GPT.

The model you picked

The plugin doesn't carry your GPT's selected model.

Sharing settings

The new plugin starts private. Nobody you shared the GPT with gets it automatically.

Part 2

The new system, in plain English

Plugins, Skills, reference files and apps.

The four pieces

How the parts fit together

Plugin

The container that holds your Skills, files and connected apps.

Skill

Reusable instructions telling ChatGPT how to handle one specific job.

Reference files

The information a Skill can use while it does that job.

Apps

Services and data your Plugin can connect to.

Same work, new shape

Your GPT is changing shape

Before

Custom GPT

  • Instructions
  • Knowledge
  • Tools
  • Actions

After

Plugin

  • Skills
  • Reference files
  • Apps

If your GPT uses custom actions, those connections get rebuilt separately.

The piece that matters most

What a Skill actually is

A prompt

Typed once. Gets one result. Lives in your notes and depends on you remembering it.

A Skill

Saved once. Runs the same process every time. ChatGPT loads it when the job matches its description.

Your GPT instructions become a Skill, so the clearer those instructions are, the better the replacement behaves.

Part 3

Watch me migrate one

A real Custom GPT, start to finish.

The process

Seven steps, every time

01

Open the migration tool

02

Move the GPT into a Plugin

03

Find the new Skill

04

Check the transferred files

05

Review what did not move

06

Edit the Skill

07

Test the Plugin

Live walkthrough

Where the migration lives

In ChatGPT

My GPTs → pick the GPT → Migrate to plugin

Review the migration details, then follow the prompts to create the plugin.

Two things to know

  • It uses the latest published version
  • The new plugin starts private

Before you migrate

Five minutes that save you an afternoon

Publish your edits

Drafts and unpublished changes don't come across.

Copy the instructions

Keep your own copy outside ChatGPT.

List the knowledge files

So you can check nothing is missing afterward.

Save three real prompts

You'll run these against the plugin to compare results.

After you migrate

Test it before you rely on it

Check that it

  • Picks the right Skill and follows your instructions
  • Uses the reference material you expect
  • Returns complete answers in the format you need
  • Has the tools the job needs

Keep in mind

After migrating, the original GPT still works until retirement, but it becomes read-only. Make future changes in the plugin.

Your turn

Migrate the GPT you brought

Have this ready

  • One GPT you actually use
  • Its instructions, copied somewhere safe
  • Three requests you normally give it
  • A note of any custom actions it uses

No migration option yet? Do the prep now and migrate the day it appears.

Part 4

Loose ends and what's next

Actions, sharing, priorities and building the new way.

Priorities

Which GPTs to migrate first

The ones you use weekly

Your daily drivers earn the first slot.

Anything clients or customers use

They need time to switch over too.

GPTs holding files you can't rebuild

Protect the knowledge you'd hate to lose.

Leave the experiments

Half-finished GPTs can retire quietly.

Troubleshooting

No "Migrate to plugin" option?

It's still rolling out

Access arrives account by account and workspace by workspace.

Check which account built it

You have to be in the account or workspace where the GPT was created.

The GPT must be published

Drafts can't be migrated.

On a work account, ask your admin

Plugins have to be enabled for the workspace.

The one that needs work

If your GPT uses custom actions

01

Check for an app first

An available app may already cover what the action did.

02

Otherwise it gets rebuilt

A replacement connection may need a custom MCP server and some technical setup.

03

Test the connection on its own

Don't assume a rebuilt integration does everything the old action did.

This is the part to start early, especially for anything a client depends on.

Sharing

Your plugin starts private

Sharing settings don't carry over

People who used your GPT get nothing automatically.

Share it again on purpose

Give access, then ask one person to install and test it.

Public listing is separate

A public plugin goes through its own submission process.

If you sell or deliver a GPT to clients, plan the switch before the retirement date.

Going forward

Two things to walk out with

01

Migrate what you already built

Preserve the useful parts of the GPTs you spent hours on and move them into the new system.

02

Build the new way from here

For new projects, start with Skills and Plugins instead of a system that is being retired.

Don't wait until the last week

Move your GPTs before you're forced to rush.

Custom GPTs are currently scheduled to retire on December 11, 2026. That is time to prepare, not time to forget about it.

Keep going

Your next step after today

Optional add-on

Skills Starter Pack

$50

  • Ready-made Skill examples
  • Templates and creation prompts
  • Migration framework

Membership

AI Content School

$50/mo

  • This workshop included
  • Other classes and workshops
  • Replay library and community

Q&A

Questions?

Migrate one GPT this week. Bring your questions to the community.

Mike Wayne · AI Content School · [email protected]