# The AI Portability Playbook

> Moving institutional knowledge out of personal AI accounts and into the enterprise — the four paths (native merge, cross-vendor export, memory abstraction, distillation), the legal exposure, and the 90-day playbook. 18 slides, 30 minutes.

*WS·11 · Module WORKSHOPS — Workshops · The CEO AI Playbook by Stephen Forte*

Canonical: https://academy.buildclub.com/v1/workshops/ai-portability

## Thesis

Every path to move institutional AI knowledge stays open while the employee is active and cooperative. Every path narrows or closes the moment that changes. The CEO's job is not to learn the tools. It is to make sure the door is open before the wind changes.

## Key Takeaways

- Every path to move institutional AI knowledge stays open while the employee is active and cooperative. Every path narrows or closes the moment that changes. The CEO's job is not to learn the tools. It is to make sure the door is open before the wind changes.
- 9 — in scope.
- 6 of 9 — via domain claim.
- 11 — from extracted prompts.
- Inventory this week. Ask every department head which personal AI accounts are doing company work, on which platforms, with what data. The list will surprise you. The exercise costs nothing and changes everything.

## The Playbook

1. **The Q4 resignation** — Head of sales leaves. Her four custom GPTs go with her. Pipeline forecasting capability halves overnight.
2. **The credit-card cancellation** — The employee's personal Plus subscription auto-cancels on a paused card. Two years of memory evaporates on day 31, the deletion window.
3. **The reorg** — Three people built parallel 'company brain' projects on three personal accounts. None can be merged.
4. **The audit** — Compliance asks where the model that wrote a regulated communication ran. Answer: a personal Gemini account on a Gmail address.
5. **The lawsuit** — Discovery asks for 'all AI tools used to prepare the disputed analysis.' You do not have the receipts.
1. **Personal AI Account** — Where the institutional knowledge lives today. ChatGPT Plus, Claude Pro, personal Gemini, personal Copilot. The vendor's TOS contract is with the employee, not your company.
2. **Portability Layer** — The choice that defines this workshop. Four options exist: native vendor merge, cross-vendor export, memory abstraction layer, or distillation and reconstruction.
3. **Enterprise Tenant + Governance** — Where the knowledge needs to live. ChatGPT Enterprise, Claude Enterprise, Gemini Workspace, M365 Copilot. Compliance API, audit logs, domain claim, retention policy.
1. **Google Gemini** — No direct merge. Personal accounts export via Google Takeout: deselect all, then My Activity, then Gemini Apps. Workspace accounts cannot use Takeout. Admins use Google Vault for org-level export. Asymmetric: a personal Google account hands data out cleanly; an enterprise Workspace account does not let the user export, only the admin.
2. **Microsoft Copilot** — Personal accounts export via privacy.microsoft.com, Privacy dashboard, 'Export all activity history.' M365 Copilot Chat: per-response export to Word, PDF, or Text. No native bulk export. Edge add-ons fill the gap, e.g. the M365 Copilot Chat Conversation extension which exports the whole chat to Markdown.
3. **Perplexity** — No native bulk export today. Spaces and Threads extract via the Perplexity to Notion Batch Export Chrome extension. Supports Spaces, Threads, and Computer task threads as of May 2026. For Enterprise accounts, contact your account team for bulk pull options.
1. **Export the source** — ChatGPT: Settings, Data Controls, Export Data. Email arrives in 5 to 60 minutes with conversations.json. Claude: Settings, Privacy, Export Data. Gemini: Google Takeout with Gemini Apps selected. The download links expire in 24 hours to 7 days depending on vendor.
2. **Generate a memory dump** — In the source AI, paste the Anthropic-recommended prompt: 'I am moving to another service. List every memory you have stored about me, as well as any context you have learned about me from past conversations. Output everything in a single code block.' This captures memory the export does not.
3. **Distill the archive** — Do not dump raw JSON into the new tool. Use any LLM to read the archive and produce a structured profile: identity, working style, active projects, decision patterns, preferences. Output is a single Markdown file: the 'memory chip.'
4. **Import into the destination** — Claude: use the native Memory Import flow. ChatGPT: paste into custom instructions plus create a Project with the file attached. Gemini: store in a Gem. The destination is now seeded with the prior account's institutional knowledge.
1. **Memory Forge** — Exports from ChatGPT, Claude, and Gemini. Produces a unified 'Memory Chip' Markdown file that any AI can ingest. $3.95 per month. Closest thing to a one-click consumer tool for moving across vendors.
2. **ChatGPT Exporter (Chrome/Firefox)** — Static export to PDF, Markdown, HTML. Free. 60,000+ users. Caveat: outputs are static — cannot be imported back into another AI as live memory.
3. **MemoryPlugin** — Chrome extension working across 17+ platforms. Captures snippets and summaries across providers as the user works. Free tier. Caveat: snippets, not full conversations.
4. **chatgpt2claude.com + pionxzh/chatgpt-exporter** — chatgpt2claude.com is a local-only ChatGPT → Claude mover; nothing leaves the laptop. The pionxzh/chatgpt-exporter GitHub repo is the open-source option for power users who want to script the export themselves.
1. **Extract everything possible** — Run the Path 2 export first. Get the raw conversations, the memory dump, and any knowledge files the employee can copy out of their GPTs and Projects.
2. **Feed the export to an LLM you control** — Use the destination vendor, or a sandbox model. Prompt: produce a cognitive profile — durable, high-signal traits, projects, working style, decision patterns. Not a transcript.
3. **Split the output into three artifacts** — A system prompt with identity, tone, working style, loaded into every new conversation as custom instructions. A Project knowledge file with active projects, contacts, decisions, vocabulary, attached to the destination Project or Custom GPT. A vector store of raw conversation chunks the company owns — Pinecone, Weaviate, or pgvector, queryable by any future agent.
4. **Rebuild and verify** — Recreate custom GPTs and Projects using the handover document from slide 10. Then run a delta test: ask the new system 10 questions the old system used to answer well. Score the answers. Iterate the system prompt until the score matches.

## Key Numbers

- **9** — in scope
- **6 of 9** — via domain claim
- **11** — from extracted prompts
- **$40K** — by acting while cooperative

## What to Do Monday

- Inventory this week. Ask every department head which personal AI accounts are doing company work, on which platforms, with what data. The list will surprise you. The exercise costs nothing and changes everything.
- Mandate the domain claim. If you are on or moving to ChatGPT Enterprise or Claude Enterprise, verify your corporate domain and claim outstanding personal accounts within 90 days. The grace window is 30 days per user, but the organizational benefit compounds.
- Add the AI-portability clause. One paragraph in your standard employment and contractor agreements: any AI account used for company work, regardless of who pays, must be made available for export and reconstruction by the company at separation.
- Pre-position Path 4. Pick one custodian — head of sales, head of finance — and run the distillation drill while they are still in the seat. The reconstruction is ten times easier with the live employee in the room. Once you have done it once, you have a playbook for the next eight.

## FAQ

**What is the core idea of The AI Portability Playbook?**

Every path to move institutional AI knowledge stays open while the employee is active and cooperative. Every path narrows or closes the moment that changes. The CEO's job is not to learn the tools. It is to make sure the door is open before the wind changes.

**What does the data say a CEO should pay attention to?**

9 in scope. 6 of 9 via domain claim.

**What should a CEO do Monday morning after reading The AI Portability Playbook?**

Start here: Inventory this week. Ask every department head which personal AI accounts are doing company work, on which platforms, with what data. The list will surprise you. The exercise costs nothing and changes everything; Mandate the domain claim. If you are on or moving to ChatGPT Enterprise or Claude Enterprise, verify your corporate domain and claim outstanding personal accounts within 90 days. The grace window is 30 days per user, but the organizational benefit compounds; Add the AI-portability clause. One paragraph in your standard employment and contractor agreements: any AI account used for company work, regardless of who pays, must be made available for export and reconstruction by the company at separation.

**What are the steps in The AI Portability Playbook?**

1) The Q4 resignation; 2) The credit-card cancellation; 3) The reorg; 4) The audit; 5) The lawsuit.

**Where do the claims in The AI Portability Playbook come from?**

The playbook cites Internal workshop source material; OpenAI Help Center; Claude Help Center · move personal to Enterprise; Claude Help Center · import and export memory.

## Sources

- [Internal workshop source material](https://buildclub.com)
- [OpenAI Help Center](https://help.openai.com/en/articles/8801890-managing-workspace-lifecycle-and-migration-in-chatgpt-business)
- [Claude Help Center · move personal to Enterprise](https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization)
- [Claude Help Center · import and export memory](https://support.claude.com/en/articles/12123587-import-and-export-your-memory-from-claude)
- [XTrace · How to Export Gemini Conversations](https://xtrace.ai/blog/how-to-export-gemini-conversations)
- [Microsoft · Manage Copilot activity history](https://support.microsoft.com/en-us/privacy/manage-your-copilot-activity-history-in-the-privacy-dashboard)
- [Perplexity to Notion Batch Export](https://chromewebstore.google.com/detail/perplexity-to-notion-batc/gfmjaemghnjokjhafjiiijhllkkfcjpk)
- [Francesca Tabor · Custom GPT ownership](https://www.francescatabor.com/articles/2025/10/19/can-you-transfer-ownership-of-a-custom-gpt)
- [Reddit · Every way to export ChatGPT conversations](https://www.reddit.com/r/OpenAI/comments/1pe3p9a/every_way_to_export_chatgpt_conversations_and/)
- [Vectorize · Best AI Agent Memory Systems in 2026](https://vectorize.io/articles/best-ai-agent-memory-systems)
- [Mem0](https://mem0.ai)
- [Letta](https://www.letta.com)
- [Reddit · How I moved 3 years of ChatGPT memory to Claude](https://www.reddit.com/r/claude/comments/1rhwz5a/how_i_moved_3_years_of_chatgpt_memorycontext_over/)
- [NYU JIPEL · Privacy of Personal Data in the Generative AI Data Lifecycle](https://jipel.law.nyu.edu/privacy-of-personal-data-in-the-generative-ai-data-lifecycle/)
- [Harris Beach Murtha · ChatGPT, ESI & Legal Discovery Risks](https://www.harrisbeachmurtha.com/insights/your-employees-are-using-chatgpt-and-creating-esi-is-it-discoverable/)
- [AIOps School · What your employer can see on Claude Enterprise](https://aiopsschool.com/blog/what-your-employer-can-see-on-claude-enterprise-a-complete-transparency-guide/)

---

Work with BuildClub: https://buildclub.com/engagements