Moving Personal ChatGPT Use into a Company Workspace

Moving personal ChatGPT use into a company workspace is two separate steps on OpenAI's help pages: an employee joins the ChatGPT Business workspace (formerly ChatGPT Team) with the email already on their personal account, and then chooses whether to keep the personal workspace separate or merge it. In Business the employee makes that choice; admins cannot require a merge. A merge moves the employee's own conversations, files, custom GPTs, projects and saved memories into the workspace, is permanent, deactivates the personal workspace and cancels a web-billed Plus or Pro subscription with a prorated refund. This guide covers what transfers, what does not, and the steps a workspace owner should run, as of October 2026.

It assumes the plan decision is made; if not, start with ChatGPT Business vs Plus and Pro. The workspace itself should already be configured per the ChatGPT Business setup checklist, with the data controls from the security settings checklist in place, because everything that merges falls under those settings.

What transfers from a personal ChatGPT account into a Business workspace?

From OpenAI's workspace lifecycle and migration article, the merge moves the following and leaves the rest behind:

Should employees keep personal work separate or merge?

Joining and merging are different actions. After joining a Business workspace, a person can keep the personal workspace and switch between the two, with the personal subscription continuing until they cancel it, or merge. OpenAI's Business SSO article is explicit that admins cannot require someone to merge or delete a personal workspace; on Enterprise, OpenAI says the organization's onboarding requirements determine whether a personal workspace can stay separate. OpenAI's onboarding guidance recommends that staff keep a separate personal account on a personally owned email for personal use.

A workable rule for a company: merge when the personal account was used mainly for work and that work needs to stay with the company; keep it separate and start clean when the account mixes personal and work content, because everything that merges comes under workspace access and retention and an owner can export it. Write the decision down per person, because it cannot be reversed.

What is irreversible?

• The merge itself. OpenAI says it is permanent with no undo. The personal workspace is deactivated, though OpenAI says its data is not deleted.
• Access and retention. Migrated content falls under the workspace's access rules and retention settings from that moment.
• Export. Self-service data export is not available in Business or Enterprise, so anything a person wants a personal copy of must be exported from the personal account before merging.
• The subscription. A web-billed Plus or Pro subscription is cancelled on merge. OpenAI's Business FAQ adds that a Premium seat is a Business seat type, not a rename of a personal Pro subscription, so a Pro user who merges needs a Premium seat assigned if they still need the usage.
• Residency. OpenAI notes that data-residency requirements may prevent personal chats from transferring.

Two related limits at the workspace level, from OpenAI's Business FAQ: two Business workspaces cannot be merged into one, and moving a Business workspace to Enterprise while keeping its data is done through sales.

How does a workspace owner run the migration?

1. Inventory. List everyone who uses ChatGPT for work, the email on their personal account, their plan, and the GPTs, projects and automations they rely on.
2. Buy seats and invite with the exact existing email. Under Workspace settings, Members, Invite member, enter the addresses or upload a CSV with email, role and seat type. OpenAI warns that inviting a different address than the one on the personal account creates a separate account and makes history appear missing.
3. Give each person the decision rule and the export instruction. Keep separate or merge, decided in writing, and an export from the personal account first.
4. Merge. The person switches to the Business workspace, opens Settings, Data Controls, chooses Merge data from your personal workspace and confirms.
5. Reconnect and re-share. Reauthenticate connected apps, recreate custom plugins and custom MCP server connections, re-share GPTs that arrived private, and move shared projects to a workspace owner where the team depends on them.
6. Confirm the subscription. Check that a web-billed Plus or Pro was cancelled and refunded; cancel App Store or Google Play subscriptions by hand.
7. Record acceptance. Each person confirms in writing that what they expected to move is there.

What happens when an employee leaves?

This is the reason to migrate at all. When a member is removed from a Business workspace, OpenAI's retention article says their chats, files and canvas documents are retained indefinitely and restored if the person is re-added, and their projects and GPTs are reassigned to a workspace owner (ownership only; the owner does not gain access to the conversations). With SSO in place, disabling the directory account ends sign-in the same day. The seat is freed but the paid count does not drop until an owner schedules a reduction. Compare that with work done on a personal account, where the company keeps nothing.

Migration decision and acceptance checklist

1. Inventory complete: every work user, their account email, plan and the assets they need to keep.
2. Decision per person written down: keep separate and start clean, or merge.
3. Export done from the personal account for anything a person cannot lose.
4. Invitations sent to the exact existing email, with roles and seat types set.
5. Personal subscriptions: cancellation date and refund confirmed, app-store subscriptions cancelled by hand.
6. Shared GPTs and projects re-shared from the workspace so they survive the person leaving.
7. Acceptance recorded per person.
8. Leaver rehearsal done on a test account, with the result filed.

Frequently asked questions

Can I transfer my ChatGPT chat history to a business account?

Yes, by merging your personal workspace into the Business workspace from Settings, Data Controls. Supported conversations, files, your own GPTs and projects move together; you cannot select individual chats, and the merge cannot be undone.

Can I move a custom GPT into the company workspace?

GPTs you created move with a merge and arrive as private GPTs; GPTs other people own do not. Plan their replacement, because OpenAI has scheduled custom GPTs to retire on December 11, 2026 in favor of plugins.

Can I keep a personal and a business ChatGPT workspace on the same account?

Yes. After joining a Business workspace you can keep the personal workspace and switch between them, and the personal subscription continues until you cancel it. Business admins cannot require a merge.

Will the company see my old personal chats after a merge?

Migrated content falls under workspace access and retention. OpenAI's Business data sharing article says admins and owners cannot see all private member chats by default, while its enterprise privacy page says workspace admins can view, access, export and delete end-user conversations. Assume anything you merge can be produced by an owner.

Do I need to cancel ChatGPT Plus when I join the workspace?

If you merge, a web-billed Plus or Pro subscription is cancelled automatically with a prorated refund; subscriptions through Apple or Google must be cancelled separately. If you keep the personal workspace, the subscription continues until you cancel it.

Can two Business workspaces be merged?

No. OpenAI does not support Business-to-Business merges. A company with several workspaces consolidates by moving people and re-sharing assets, or by moving to Enterprise through sales.

How NetSys plans a workspace migration

A migration under our ChatGPT Business setup service starts with the inventory: who already uses ChatGPT for work, on which account, with which GPTs and projects they would miss. A NetSys engineer writes the keep-or-merge decision for each person, schedules the moves around the pilot, confirms what transferred and records acceptance, and the same engagement sets the workspace's data controls and SSO before anyone merges. Afterward, managed AI services handles joiners, leavers and the ownership questions that come up when someone changes role.

NetSys engineers run the inventory and the per-person decisions before anyone clicks Merge, so plan a company workspace migration before staff start moving accounts on their own.