Moving work off personal AI accounts starts with an inventory and a decision about where business work belongs. Identify the useful instructions, files, connections and recurring tasks; separate personal material; choose an appropriate organisational setup; then verify access and operation before closing or merging anything.
A new seat does not answer every question about existing content, personal subscriptions, shared links or connected services. Joining a workspace, transferring material and cancelling a subscription are separate decisions to check for the actual product and account.
This is a planning guide, not a sequence of account-migration clicks. Provider options change and some actions cannot be reversed. The linked official guidance was checked on 2 November 2026; read the current instructions and the options shown in your account before making a change.
Find out what work depends on the accounts
Ask people which tasks they use AI for and what they would miss if their account became unavailable. Focus the inventory on business dependencies rather than asking employees to disclose personal conversations or hand over passwords.
Useful work might live in a project instruction, a reference file, a conversation that developed a reusable method or an output someone has shared with a colleague. A recurring task may also depend on a connection to an external application.
Record the business purpose and ownership of each item. Access to something in a personal account does not by itself establish that it may be moved into a company workspace or supplied to another provider. Resolve permissions for the actual material.
Use a work and account inventory
Copy this worksheet into the business's approved record system. Record descriptions and owners; keep credentials in their existing secure stores.
If columns don't fit, scroll sideways. Keyboard: focus the table and use the arrow keys.
| Item to inspect | What to record | Decision needed |
|---|---|---|
| Business task | What the person prepares and who uses it | Which tasks belong in the team setup? |
| Instructions or reusable method | Owner and approved source version | Retain, improve or recreate with permission? |
| Files and reference material | Business owner, sensitivity and permitted use | May the destination process this material? |
| Chats containing useful work | Business output to preserve and any personal content mixed in | What needs retaining, and by which permitted method? |
| Shared outputs and links | Intended users and current dependency | Will access remain available after a change? |
| Connected services | Service owner, account used and actions permitted | Who approves and verifies the destination connection? |
| Subscription and billing | Payer, billing channel and responsible person | What continues, changes or ends? |
| Operating responsibility | Who maintains the task and handles exceptions | Can another authorised person run it? |
The inventory should lead to a small, explicit move plan. It should not become an instruction to copy every chat or file indiscriminately.
Keep personal material and business work distinct
A practical option is to establish the agreed destination for new business work while separately deciding what, if anything, should happen to older material. That can reduce pressure to merge an entire personal history merely to start using a team workspace.
Where the product and organisational requirements permit keeping accounts separate, explain which account people should use for each type of work. Make the destination recognisable and include an account check in the task instructions. A person should not have to guess where a customer file belongs.
For mixed material, identify the business result that needs preserving. An approved instruction or final work product may be more useful than an entire exploratory conversation. Any transfer still needs permission and a supported method. Do not assume a copied chat preserves the original system's context, tools or access settings.
What the current vendor guidance establishes
OpenAI's workspace migration guidance distinguishes joining a workspace from migrating personal content. For ChatGPT Business it describes keeping the personal workspace separate or merging, subject to the available options. It also explains that migration does not offer an undo path back to the personal workspace, that supported content varies, and that losing organisational access can affect access to migrated material. Check the current guide for retention, export and subscription consequences before choosing.
Anthropic's account migration guidance describes keeping accounts separate or moving supported personal content where eligible. It calls the move into an organisation one-way and lists exclusions, including connected-service sign-ins and some shared or published material. The available options depend on the account and destination. Do not assume an existing connection, public link or useful local output will work unchanged after a move.
These summaries do not imply that either product must be migrated in a particular way. Use the exact provider guidance, account prompts and your organisation's requirements to decide. If a required item or option is unclear, resolve it with the provider before an irreversible action.
A fictional example: preserve the method, review the history
This example is invented and is not a migration performed for a client. Suppose an office coordinator has used a personal account to develop a helpful enquiry-summary instruction. The account also contains private conversations. A shared output link is included in a colleague's checklist, and a connected application supplies customer information.
The team first records the useful business instruction, its permitted source material and the people who use the output. It decides that new enquiry work should happen in an agreed organisational setup. It evaluates whether the approved instruction can be recreated there using a supported method.
The team separately checks the shared-link dependency and the required application access. A representative task test confirms the correct source and reviewer can be reached in the destination. Personal history is not swept into the move by default, and no one assumes that setting up the instruction has resolved the connection or billing questions.
The useful result is continuity of the agreed work, with clear responsibility for the remaining decisions.
Verify the destination with real task boundaries
Before relying on the new setup, ask an intended operator to perform a representative permitted task. Check the account, source material, output and reviewer. Include a missing-information case and a case the operator should decline or escalate.
Verify access as the relevant users, within your authorised testing scope. An owner being able to open a project does not establish that the intended colleague can use it, or that unrelated people cannot. Record the checks appropriate to the actual workspace and connected services.
Where external systems are involved, confirm both the connection and its allowed actions. Reading a record, updating it and sending a message are separate responsibilities. Use a safe test scope rather than creating a real customer communication to prove a connection works.
The team rollout guide adds practical training and ongoing ownership. The company-knowledge guide helps review source versions and permitted use.
Plan departures and support before closing the move
Ask what happens if the person who created the working setup changes role or leaves. Name someone responsible for business continuity, access removal, source maintenance and billing. Check which transfers, exports or reassignment options the selected product actually supports.
Keep business instructions and operating records in an agreed location that authorised colleagues can use. Do not make an employee's personal password the business's recovery plan. Provider account recovery and business handover are different tasks.
Also check subscriptions in the place they were purchased. OpenAI's billing guidance distinguishes ChatGPT and API billing and notes that subscriptions across platforms can create separate charges. A new organisational seat is not evidence that an older charge has stopped. Record the actual receiving state after any authorised billing change.
Finish with an operating handover
The move is ready to rely on when the agreed work, permitted access, source material, necessary connections and operating responsibility have been checked in the destination. Keep unresolved items visible and leave an appropriate way to continue the work while they are resolved.
Build n Bloom's ChatGPT + Claude Implementation service can help scope the setup, task method, training and verification. Account changes, subscriptions and provider access remain subject to the actual contracts, permissions and agreed work.
Start with a free 25-minute Fit Call and a plain-language description of what your team uses today. No confidential files are required. You keep a short reviewed provisional Fit Note, with delivery timing agreed during the call. If you are still choosing the type of implementation, compare tool use, configured projects and a custom build.