Moving Staff From Personal AI Accounts to Business Plans: A Checklist

To move staff off personal AI accounts, choose one business plan, write a short account policy, find out what people already use and have built, set up company accounts, migrate the useful prompts and context into shared files, then set a date after which company work happens only in company accounts. Do it with thanks, not blame.

Why move staff off personal AI accounts?

Personal accounts put company data outside the business's control, run under consumer terms rather than commercial ones, and keep whatever staff build with the individual. Company accounts fix all three. They also make shared projects, shared skills and consistent work possible, which personal accounts cannot offer.

The scale of personal use is large. According to Microsoft and LinkedIn's 2024 Work Trend Index, 78% of people who use AI at work bring their own tools. MIT NANDA's 2025 study found workers at over 90% of companies used personal AI tools, while only 40% of companies had bought an official subscription.

Terms matter too. In August 2025 Anthropic updated its consumer terms so Free, Pro and Max users choose whether chats are used for training, and stated the change does not apply to services under its Commercial Terms. Other vendors have their own distinctions, so check each one.

What should happen before the switch?

Decide on the plan, write the policy, and find out what people already use. Choosing the plan first avoids a messy mix of tools. Writing the policy first means everyone moves onto clear rules. Asking what people use first means you can migrate the useful work rather than lose it.

Three decisions come first:

• The plan. One main assistant on a business plan, chosen for the team's needs and admin requirements.
• The policy. One page on approved tools, data rules, approval and accounts. The guide to writing an AI policy includes a template.
• The owner. One person runs the switch and answers questions.

What is the step-by-step checklist?

Ten steps cover most businesses: choose the plan, write the policy, name an owner, survey current use, set up accounts and single sign-on, create shared projects, migrate useful prompts and context, train each team, set the switch date, then remove company data from personal accounts. Expect it to take a few weeks.

1. Choose the business plan and the admin settings.
2. Write the one-page policy.
3. Name an owner for the switch.
4. Survey current use: which tools, for what, on whose account. Keep it no-blame.
5. Set up company accounts, with single sign-on where available.
6. Create shared projects for main clients and initiatives.
7. Migrate useful work: prompts, instructions and context people built.
8. Train each team on the company setup, using their own tasks.
9. Set the switch date after which company work happens only in company accounts.
10. Clean up: ask staff to remove company data from personal accounts.

How do you keep what people built in personal accounts?

Ask staff to share the prompts, instructions, templates and context they rely on, then fold the useful parts into shared files: methods become skills, facts go into the company's shared knowledge, and client context goes into the relevant project. This turns individual know-how into company knowledge.

This step is where the real value lies. People who have used AI for months have quietly built good methods: a proposal prompt that works, a way of summarising calls, a checklist for reports. Left in personal accounts, all of it is lost when they move on.

A short template helps people share. Ask four questions: what do you use AI for, which prompts or instructions work best, what files or facts do you give it, and what would you want a new colleague's AI to know? The answers seed the shared company brain.

What happens after the switch?

After the switch date, company work happens in company accounts, the policy is reviewed every few months, new starters are set up on day one, and leavers' accounts are closed with their useful work already captured. A monthly clinic helps people with questions as they settle into the new setup.

Two habits keep it working. First, onboarding includes AI setup, so new staff never start on personal tools. Second, offboarding checks that nothing important remains only in the leaver's account. The guide to offboarding in the AI era covers that step.

Privacy obligations continue too. Australia's privacy regulator recommends, as best practice, not entering personal information into publicly available generative AI tools. A company plan with clear data rules makes that much easier to follow.

Skein helps leadership teams plan and run this move, from the rules and the rollout to the shared knowledge people's work is migrated into. That suits a business where many staff use their own AI. A team of three may manage the switch in an afternoon with the checklist above.

Frequently asked questions

How do I move employees from personal ChatGPT or Claude accounts to a business plan?

Choose one business plan, write a short policy, survey what people use and have built, set up company accounts, migrate useful prompts and context into shared files and projects, train each team, then set a date after which company work happens only in company accounts.

Should employees delete company data from personal AI accounts?

Yes, once their useful work has been captured in company accounts. Ask staff to remove company and customer information from personal AI tools after the switch date, and include it in the policy. Do it without blame, since most personal use was well intentioned.

What should an AI account policy include?

It should name the approved tools and plan, say company work happens only in company accounts, set rules on what data may go into AI, require a person's approval for anything external, name an owner, and set a review date. Keep it to one page.

How long does it take to move a team to a business AI plan?

For most businesses of 10 to 200 people, a few weeks: a week to choose the plan and write the policy, a week or two to survey use, set up accounts and migrate work, then training and a switch date. Small teams can do it faster.

What if staff prefer their personal AI tools?

Make the company setup better. Give the company assistant the business's own knowledge, shared projects and skills, so it outperforms a personal account. Thank early adopters, use their prompts in the shared setup, and explain why company accounts protect them and the business.

Related reading