ChatGPT Plugins vs Copilot Agents: Where Should GPTs Go?
OpenAI moves custom GPTs into ChatGPT plugins. Here is what carries over, what doesn't, and when rebuilding them as Microsoft Copilot agents makes more sense.
OpenAI has scheduled custom GPTs to retire on December 11, 2026, across all ChatGPT plans, and Enterprise workspaces with an approved deferral have until February 11, 2027. Every company with GPTs now has a choice to make: follow OpenAI's own path and move them into ChatGPT plugins, or rebuild them somewhere else. For companies that run on Microsoft 365, the most common "somewhere else" is a Microsoft Copilot agent.
Neither answer is right for everyone. This guide lays out what each path keeps, what it loses, and the questions that usually decide it.
What OpenAI's plugin migration does
OpenAI's path moves each GPT into a ChatGPT plugin:
- The GPT's instructions become a skill.
- Its knowledge files are copied into the plugin.
- Connected apps are added.
Some things don't come along:
- Custom actions (the API calls a GPT made to other systems).
- The GPT's selected model.
- Sharing settings. A migrated personal plugin starts out private.
- Drafts. Only the latest published version of a GPT moves.
Existing conversations with GPTs stay accessible after the retirement.
So the plugin route keeps the core of a simple GPT, instructions and files, with little effort. GPTs that call other systems or are shared across teams need work either way.
What a Copilot agent looks like
A custom GPT maps closely to a Copilot agent:
| Custom GPT | ChatGPT plugin | Microsoft Copilot agent |
|---|---|---|
| Instructions | Become a skill | Agent instructions, up to 8,000 characters in Agent Builder |
| Knowledge files | Copied into the plugin | Uploaded (up to 20) or read from SharePoint and OneDrive, with existing permissions |
| Custom actions | Don't carry over | Copilot Studio connectors or MCP servers |
| Sharing | Starts private for personal plugins | Shared with specific people; organization-wide through Copilot Studio with admin approval |
| Where people use it | ChatGPT | Copilot Chat and the Microsoft 365 apps |
The biggest difference is where the knowledge lives. In Copilot, an agent can read a SharePoint library directly, and it only shows each person what they already have permission to see. Nobody uploads a second copy of the files, and the agent doesn't go stale when someone updates the rate card.
Questions that decide it
Where does your team work all day? If it's Outlook, Teams, Word and Excel, an agent that lives there is where people will reach for it. An assistant in a separate tab is easier to forget.
Are you paying for two AI tools? Microsoft Copilot Chat comes with Microsoft 365 business subscriptions at no extra cost, and agents that use only instructions or public websites run on it for free. Agents that use company data such as SharePoint are metered in Copilot Credits for Copilot Chat users, and the paid Microsoft Copilot license covers people who need Copilot across the apps with company data. If most of your GPTs would work as Copilot agents, the ChatGPT seats are worth a second look. Our AI cost calculator compares the two with your numbers.
Do your GPTs call other systems? Custom actions don't carry over to plugins. In Copilot they become Copilot Studio connectors or MCP servers. Either way it's real work, so it's worth doing once, in the platform you plan to keep.
Who controls the data? Copilot runs inside your Microsoft 365 tenant, with your existing permissions, sensitivity labels and admin controls, and Microsoft says prompts, responses and data accessed through Microsoft Graph aren't used to train its foundation models. OpenAI says it does not use business data from ChatGPT Business, Enterprise and Edu to train its models by default. The difference is mostly about where the controls live and who manages them.
When the plugin route makes sense
Keeping your GPTs in ChatGPT as plugins is reasonable when ChatGPT is your company's main AI tool and will stay that way, your GPTs are simple (instructions and a few files, no actions), and you aren't on Microsoft 365 or don't plan to use Copilot.
When rebuilding in Copilot makes sense
Rebuilding as Copilot agents is usually the better move when your company already runs on Microsoft 365, the GPTs depend on documents that live in SharePoint or OneDrive, you want one AI tool under one set of admin controls instead of two, or your GPTs need actions you'd have to rebuild anyway.
A mixed answer is fine
You can keep a handful of plugins for a team that lives in ChatGPT and move everything else to Copilot. The point is to decide per GPT instead of migrating everything by default before December 11. That starts with knowing what you have: which GPTs exist, who owns them, who uses them and what they connect to.
Our step-by-step guide to rebuilding a GPT in Agent Builder covers the Copilot side, and the AI Migration Assessment inventories every GPT and recommends a home for each one.