You built a Custom GPT on your personal ChatGPT Plus account — instructions tuned over weeks, knowledge files uploaded, Actions wired to an internal API. Now the company bought a ChatGPT workspace and wants the GPT there so colleagues can use it under the company’s data-handling terms. You go looking for Share → Transfer ownership, expecting to pick the workspace from a dropdown, and there is no such option. Or you find an old screenshot of one, click through, and it silently fails, sits on Pending, or shows Transfer not available for this GPT.
Here is the part most guides get wrong: as of June 2026 there is no per-GPT “transfer to workspace” button that moves a single Custom GPT from a personal account into a workspace. That flow does not exist. There are exactly two real paths, and which one applies depends on where the GPT lives now:
- Personal account -> workspace: the only supported route is a full workspace merge (Settings -> Data Controls ->
Merge data from your personal workspace), which moves everything — chats, memories, and all your Custom GPTs — into the workspace at once. It is permanent and deletes the personal workspace. - Already inside a workspace -> another member: an Owner reassigns the GPT under
Manage workspace -> GPTs. This is the “transfer ownership” most stale docs are actually describing.
Naming note: OpenAI renamed ChatGPT Team to ChatGPT Business on 29 August 2025. You will still see “Team” in older menus, community posts, and invoices; the workspace and these steps are the same product. Enterprise and Edu are separate, sales-managed workspaces with the same GPT-ownership model.
Which path are you on?
| Where the GPT lives now | What you actually want | Supported route (June 2026) |
|---|---|---|
| Personal Free/Plus/Pro account | Move it (and your stuff) into your Business workspace | Workspace merge — see Path A |
| Personal account, only the one GPT should move | Same | Not supported as a single-GPT move; you merge the whole workspace, or rebuild the GPT inside the workspace |
| Already created inside a Business/Enterprise workspace | Hand it to a teammate / a service account | Owner reassigns it — see Path B |
| Built in workspace A, want it in workspace B | Move workspace -> workspace | Not supported; GPTs cannot transfer between workspaces. Rebuild, or contact sales for Enterprise migration |
| Creator left the workspace, GPT now orphaned | Recover / reassign it | Enterprise/Edu auto-marks it unassigned; an Owner reassigns under Manage workspace -> GPTs |
If your row says “not supported as a single-GPT move,” stop hunting for a button — you are looking for something OpenAI does not ship. Skip to Path A (merge) or rebuild the GPT in the workspace using your backup (Path C).
Path A — Move a personal GPT into a workspace via merge
This is the supported personal-account-to-workspace route. It is a whole-account merge, not a per-GPT move, so read the warnings before you click.
What the merge does (and undoes)
- Moves: all your conversations, memories, and all Custom GPTs from the personal workspace into the Business workspace, under the organization’s control.
- Drops: personal custom instructions and any legacy plugins are not carried over.
- Deletes: the personal workspace itself is deleted after migration. The merge cannot be undone.
- Billing: an active personal Plus/Pro subscription is auto-canceled and prorated, with a refund for the unused period — except subscriptions bought through the Apple App Store or Google Play, which you must cancel yourself.
- Export caveat: data export is not available from inside a Business workspace, so export anything you want a personal copy of before merging.
Step A1: Back up the GPT configuration first
Even though the merge moves GPTs automatically, take a snapshot — it is your only safety net once the personal workspace is gone. Open the GPT in Configure and capture:
- Name
- Description
- Instructions (copy the full text into a .txt file)
- Conversation starters (list)
- Knowledge files (download each one)
- Capabilities (Web Search, Image generation, Code Interpreter & Data Analysis — note toggles)
- Actions (export the OpenAPI schema for each)
- Authentication for each Action (store keys/secrets in a password manager, NOT the schema)A single gpt-backup-<name>.md plus a folder of knowledge files plus an actions/ folder of OpenAPI YAMLs is your recovery kit and the input to Path C if you decide not to merge.
Step A2: Export anything you want a personal copy of
From the personal account, go to Settings -> Data Controls -> Export data and request the archive. You receive an email with a download link (usually within minutes to a day). Do this before the merge — the option disappears once you are inside the Business workspace.
Step A3: Get a seat in the destination workspace
You must be a confirmed member of the Business workspace before you can merge into it.
1. Owner/Admin: Manage workspace -> Members -> Invite members
2. Enter your personal account email (the one that owns the GPT)
3. You: open the invite email, click Accept
4. Log in, click the workspace switcher (top-left/profile), confirm the workspace is listedIf the workspace appears in your switcher, you are in. If it does not, the invite was sent to a different email or was never accepted — fix that first.
Step A4: Run the merge from inside the workspace
1. Click the workspace switcher and select the Business workspace.
2. Profile/Settings -> Data Controls.
3. Click "Merge data from your personal workspace".
4. Read the confirmation (it lists what moves and that the action is permanent), then confirm.The merge processes in the background. Large accounts (many GBs of knowledge files across GPTs) take longer; small ones finish in minutes. When it completes, your Custom GPTs appear in the workspace and the personal workspace is gone.
Step A5: Repair Actions for the workspace
Actions whose auth was tied to your personal account will not magically work under the org. For each Action that uses external auth:
1. Have the Owner/IT register an OAuth app or API key under the workspace's domain.
2. Open the migrated GPT -> Configure -> Actions.
3. Replace the personal client_id / client_secret / API key with the workspace credentials.
4. Click "Test" on each Action and run a prompt that exercises it.If an Action hits an internal API behind SSO, confirm the workspace’s SSO/IP allowlist can reach it; otherwise the GPT returns 401 Unauthorized for everyone.
Path B — Reassign a GPT already inside a workspace
If the GPT was built inside the Business/Enterprise workspace and you just need a different member (or a shared/service account) to own it, this is the real “transfer ownership” flow.
- Who can do it: only a workspace Owner. Regular members and Admins cannot reassign a GPT they did not create unless they are an Owner.
- Where:
Manage workspace -> GPTs, then pick the GPT and reassign the owner to another workspace member. - When a creator leaves (Enterprise/Edu): the GPT is automatically marked unassigned and stays in the workspace; an Owner can review and reassign it under the same
Manage workspace -> GPTslist. If the original creator is later re-added, ownership can be restored to them automatically.
This keeps the GPT, its knowledge, and its g-<id> URL intact — only the owner field changes.
Path C — Rebuild in the workspace (when you should NOT merge)
Merging is permanent and moves your entire personal account, including private chats you may not want under the org. If only one GPT needs to live in the workspace, rebuilding from your backup is often cleaner than merging your whole personal life into the company’s data scope.
1. In the Business workspace, create a new GPT (Configure mode).
2. Paste the backed-up Name, Description, Instructions, Conversation starters.
3. Re-upload the knowledge files from your backup folder.
4. Re-add each Action from the saved OpenAPI schema; wire workspace-owned auth.
5. Set Capabilities to match the original toggles.
6. Publish with the workspace's chosen visibility.The rebuilt GPT gets a new g-<id>, so update any links your team has saved. Trade-off: you keep your personal account and chats; you lose the original GPT’s URL.
Common blockers and how to spot them
Ordered by how often each one actually stops people.
| Symptom | Real cause | Fix |
|---|---|---|
| No “transfer to workspace” option anywhere | That feature does not exist for personal->workspace | Use Path A (merge) or Path C (rebuild) |
| Workspace not in the switcher / merge greyed out | Your personal email is not a confirmed member | Step A3 — accept the invite to the right email |
Transfer not available for this GPT (in-workspace) | You are not an Owner | Path B — an Owner reassigns it |
| Merge button missing under Data Controls | You are not inside the Business workspace, or not signed in to the personal account that owns the GPTs | Switch to the workspace; confirm the GPT-owning email is the one signed in |
| GPT moved but Actions return 401 | Auth still points at personal-account credentials/SSO | Step A5 — re-issue workspace-owned credentials |
| Knowledge answers look stale/wrong after move | Re-uploaded files instead of letting the merge move them, creating duplicates | Delete the duplicate uploads; keep the migrated copies |
| Want to move workspace A -> workspace B | Cross-workspace GPT transfer is not supported | Rebuild (Path C) or contact OpenAI sales for Enterprise migration |
Before you merge: a short checklist
- Confirm you are signed into the personal account that owns the GPTs (not a second login).
- Confirm you are a confirmed member of the destination workspace (Step A3), not just invited.
- Export anything you want a personal copy of (Step A2) — there is no export inside a Business workspace.
- Cancel any App Store / Google Play ChatGPT subscription yourself; the auto-refund does not cover those.
- Decide consciously: merge moves all personal chats into org control. If that is not acceptable, use Path C instead.
How to confirm it’s fixed
- After a merge (Path A): switch to the Business workspace, open
My GPTs/ the workspace GPT library, and confirm the GPT is listed there. Your personal workspace no longer appears in the switcher. - Actions: open a chat with the migrated GPT and run a prompt that triggers each Action — it should return a
200and the GPT should cite the response, not a401. - Knowledge: ask a question that should hit a specific uploaded file and confirm the citation references the migrated copy (not a re-uploaded duplicate).
- After a reassignment (Path B): in
Manage workspace -> GPTs, the GPT’s owner field shows the new member; that member can open it inConfigureand save an edit. - Visibility: confirm the workspace’s publish setting (everyone in workspace / link only / private) is what you intended.
Long-term prevention
- For anything the company will rely on, build it inside the workspace from day one. Migrations and merges are always more brittle than a fresh build in the right place.
- Keep a weekly snapshot of important GPT configs (instructions + knowledge + Action schemas) so a backup is never the bottleneck.
- Document each Action’s auth provisioning before you need it — a merge should not be the first time anyone asks who owns the API key.
- Pin GPT versions in team docs by linking the
g-<id>URL; orphaned links erode trust. - Test a merge or reassignment on a throwaway GPT/account first, especially after any workspace policy change.
Common pitfalls
- Hunting for a single-GPT “transfer to workspace” button — it does not exist; you either merge the whole account or rebuild.
- Merging without exporting first — data export is unavailable inside a Business workspace, so personal copies are gone afterward.
- Assuming the merge is reversible — it deletes the personal workspace permanently.
- Forgetting that App Store / Google Play subscriptions are not auto-refunded by the merge.
- Re-uploading knowledge files after a merge already moved them — duplicates confuse retrieval.
- Trying to reassign a workspace GPT as a non-Owner — only an Owner can do it under
Manage workspace -> GPTs. - Expecting GPT Store ratings/installs to carry over — they do not; a rebuilt or moved GPT starts at zero.
FAQ
Q: Is there really no way to transfer just one Custom GPT from my personal account to the workspace?
Correct, as of June 2026. The only personal-to-workspace route is the full account merge, which moves all your chats and GPTs at once. If you want only the GPT (and not your personal chats) in the workspace, rebuild it there from your backup (Path C).
Q: Does my conversation history with the GPT move?
After a merge, your own chats move into the Business workspace under the org’s control. Other users’ chats with a GPT are always tied to those users, not to the GPT’s owner — reassigning ownership (Path B) does not touch anyone’s chat history.
Q: Can I undo a merge?
No. The merge is permanent and the personal workspace is deleted afterward. Export anything you want to keep a personal copy of beforehand.
Q: What happens to my Plus subscription when I merge?
OpenAI auto-cancels the remaining period and refunds it pro rata — except subscriptions purchased through the Apple App Store or Google Play, which you must cancel yourself to stop billing.
Q: The GPT’s creator left the company. Is the GPT lost?
No. In Enterprise/Edu the GPT is automatically marked unassigned and stays in the workspace; an Owner reassigns it under Manage workspace -> GPTs. If the creator is later re-added, ownership can be restored to them automatically.
Q: Can I move a GPT from one Business workspace to another?
No. GPTs cannot be transferred between workspaces. Rebuild it in the destination, or contact OpenAI sales if you are migrating an entire Business workspace to Enterprise.
Q: How is merging different from just sharing the GPT with the workspace?
Sharing keeps you as the owner on your personal account; revoke access and it is gone, and the GPT depends on your account staying active. A merge (or an in-workspace reassignment) hands control to the organization and removes that single-person dependency. For company-critical GPTs, that independence is the point. See also ChatGPT team seat not active if the destination workspace seat is not ready.
Related
- ChatGPT team seat not active
- ChatGPT account switch not working
- ChatGPT org switch not saving
- ChatGPT enterprise sso fail
- ChatGPT projects shared with team not visible
External references: OpenAI Help Center — Merging a personal workspace into ChatGPT Business and Managing GPT access in Enterprise and Edu workspaces.
Tags: #Troubleshooting #ChatGPT #custom-gpt #team #ownership