The agency relationship ends on Friday. On Monday, the owner learns that three years of prompts, accepted drafts, customer exceptions, and reporting notes live in the agency's Notion workspace and two employees' ChatGPT accounts. A shared ZIP arrives. Nobody can tell which offer is current, which client note was corrected, or how the monthly report got made.
The files were delivered. The operation was not transferred.
What forgets, taxes you. What remembers, owns you. Vendor memory is real, and it is useful. It is not your memory when you cannot read all of it, correct it, export it, or move it.
Leaving vendor AI memory means moving durable business work out of a provider account or agency archive into files the business can read, review, back up, test, and hand to another operator. You are not recreating every conversation. You preserve the evidence, promote the current records, rebuild one recurring job, and prove the next authorized worker can run it without the old account.
The method works for ChatGPT, Claude, Notion, agency portals, shared drives, and mixed archives. Export formats differ by product. Custody, classification, promotion, and acceptance stay the same.
Start at your exit stage
- No exports yet: define the exit and preserve raw copies before changing access.
- Exports received: inventory, reconcile coverage, and classify before promoting anything.
- Deadline approaching: protect access, rebuild the survival job, and test the handoff before cancellation.
Follow the stages:
- Define the exit
- Preserve raw exports
- Inventory the archive
- Classify records
- Rebuild one job
- Test acceptance
- Rehearse the handoff
- Record the result
Define the exit before exporting
An export is a collection of data. An exit is an accepted operating state.
Write the finish line first. Name the archive in scope, the business owner, the recurring job that must survive, the required records, the allowed exclusions, the test, and the stopping boundary. In my own builds, a handoff is done when the client's team runs the function without me. Hold your exit to the same test.
# migration/exit-brief.yaml
migration_id: vendor-exit-2026-08
owner: operations director
sources:
- ChatGPT account export
- Claude account export
- Notion workspace export
- agency final archive
survival_job: monthly-client-report
required_result:
- immutable raw copies
- readable inventory
- reviewed current records
- task brief and source order
- acceptance fixture
- runbook and receipts
stopping_point: independent draft and handoff receipt
must_not:
- delete provider data
- close accounts
- rotate credentials
- publish or send a report
The brief keeps the size of the archive from defining the project. The broader guide to moving AI work out of a vendor archive uses one recurring job as the unit of migration. The article on what a working session returns shows the smaller result when the owner needs one job worked through, with an owned context path and one tested output, rather than a full transfer.
Preserve the raw exports
Request exports through the official account or workspace controls. Keep the original packages unchanged. Record who requested each export, the account, request time, delivery time, filename, size, and cryptographic hash. The hash is how you prove later that nobody touched the package. I check one before I install any rewrite of my own files, because another writer may have changed the file since I read it.
OpenAI documents a data export through ChatGPT's Data Controls and Privacy Portal. The export includes chat history and other account data, with availability and delivery rules defined by the provider. OpenAI: How do I export my ChatGPT history and data?
Anthropic documents exporting Claude data from account settings, with organization controls and product-specific availability. Anthropic: Export your Claude data
Notion documents workspace export options for HTML, Markdown and CSV, and PDF, subject to workspace settings and plan limits. Notion: Export your content
Check the delivery limits before you schedule the exit. As checked September 19, 2026, OpenAI says an export can take up to 7 days to arrive, and the ChatGPT and Claude download links expire 24 hours after delivery. Anthropic limits organization exports to the Primary Owner and does not offer export in its mobile apps. Notion says a workspace export excludes pages the exporter cannot access, such as other users' private pages, so an agency workspace export can omit private material.
A finished download does not prove a complete export. Record what the provider says the export covers. Then compare it with the accounts, workspaces, dates, attachments, and databases you expected.
# migration/raw/export-register.yaml
exports:
- source: chatgpt
account: owner@example.com
requested_at: 2026-08-21T09:00:00-04:00
received_at: 2026-08-21T09:18:00-04:00
file: raw/chatgpt/export-2026-08-21.zip
bytes: 18422091
sha256: 3bd6...
coverage_claim: provider account export
verified_open: true
- source: notion
workspace: agency-client-space
file: raw/notion/export-2026-08-21.zip
sha256: 81ac...
coverage_claim: workspace export selected by administrator
verified_open: true
Store raw files read-only where you can. Do not normalize in place. Conversion errors and later disputes both need an unchanged baseline.
Build an inventory before reading everything
Inventory by metadata first. Capture the source system, original identifier, title, date range, participants when known, attachment count, file type, business or client scope, and review state.
Do not let generated summaries stand in as the inventory. Keep stable links back to raw items. A reviewer must be able to walk from a promoted decision to the original conversation or document.
source,item_id,title,created,modified,scope,type,attachments,review_state,raw_path
chatgpt,conv-4481,Client North renewal,2026-03-04,2026-04-03,client-north,conversation,2,unreviewed,raw/chatgpt/conversations.json
notion,page-182,Monthly report SOP,2025-11-10,2026-07-15,reporting,page,4,unreviewed,raw/notion/Monthly report SOP.md
agency,file-991,Offer notes,2026-01-02,2026-06-11,company,document,0,unreviewed,raw/agency/offer-notes.docx
Count records by source. Compare them with the account or workspace counts when the provider shows them. Note each gap. Do not fill it with an assumption.
The inventory is a map, not business memory. It serves review and deduplication. Authority comes later.
Convert into a readable archive
Build a readable layer next to the raw layer, never on top of it. Keep titles, timestamps, speakers where they are clear, source IDs, and attachment references. Label uncertain authorship as uncertain.
For ChatGPT exports, the guide to converting a ChatGPT export to Markdown separates the immutable JSON or HTML package from readable conversation files and promoted records. The broader ChatGPT-history migration method covers inventory, classification, review, and the first cold run.
Use a conversion manifest:
# migration/converted/conversion-receipt.yaml
tool: convert-chat-export
tool_version: 1.3.0
input: raw/chatgpt/export-2026-08-21.zip
input_sha256: 3bd6...
output_root: converted/chatgpt/
conversations_seen: 428
conversations_written: 428
attachments_referenced: 91
parse_errors: 0
speaker_uncertain: 7
completed_at: 2026-08-21T11:42:00-04:00
The receipt makes conversion repeatable. It also flags the records that need a person. Do not assign a named speaker when the export does not mark turns reliably.
Plain Markdown, text, CSV, JSON, and standard image or document formats make a durable layer when they keep the structure you need. The clay tablet outlasted the hands that pressed it. A text file is the same instinct on a faster surface. Why plain text is useful for AI memory covers readability and portability without claiming every business record belongs in one text file.
Classify before promoting
Every archive item starts as evidence. A candidate moves to one of three states: keep as a current record, reject as noise or superseded material, or hold for an authorized reviewer.
Keep items that carry a confirmed current fact, accepted decision, stable procedure, approved example, accepted correction, or open work item. Reject duplicates, generic model advice, abandoned drafts, obsolete instructions, and claims with no traceable source. Send ambiguity, sensitivity, and conflicting authority to review.
The guide to what to keep, reject, or review from a chat archive gives the triage fields. It guards against two opposite errors: throwing out useful evidence, and promoting every polished answer into policy.
# migration/review/REV-000184.yaml
candidate_id: REV-000184
source_item: chatgpt:conv-4481
source_locator: message-19
proposed_record: Client North renews on 2026-10-01
proposed_class: contractual fact
scope: client-north
status: needs-review
reason: conversation references a signed agreement not present in export
review_owner: account director
promotion_blocker: obtain agreement and verify section
The model may extract candidates. It does not approve its own extraction as business truth. These models are built to persuade, and an extraction that reads well is not a checked one. Assume nothing is correct until you check it. Promotion needs the named source and the named owner.
Deduplicate without erasing provenance
One decision may show up in a chat, a Notion summary, an email, and an agency report. Do not keep four competing current records. Pick one canonical record. List the others as evidence or superseded copies.
Use exact hashes for identical files. Use titles, dates, source IDs, and a person's review for near-duplicates. Similar wording does not prove two records carry the same authority or scope.
# owned/decisions/DEC-2026-081.yaml
record_id: DEC-2026-081
statement: Client North renews on 2026-10-01
status: accepted
authority: contractual
canonical_source: contracts/client-north-signed.pdf#section-4.2
supporting_evidence:
- chatgpt:conv-4481#message-19
- notion:page-182#renewal-note
supersedes:
- agency:file-771
owner: account director
scope: client-north
Supersession keeps history. Deletion is a separate action under retention, legal, security, and business rules.
Reconcile export coverage and missing material
Treat coverage as a claim you can test. Build an expected-source list from invoices, account rosters, workspace membership, project lists, old links, browser bookmarks, and the people who did the work. Compare it with the exports you received.
For each source, record the earliest and latest item dates, record count, attachment count, database or page count where available, and known exclusions. Ask whether shared projects, deleted items, archived spaces, custom instructions, saved memories, uploaded files, comments, and automation settings came across. The provider's documentation answers some of this. Only the package itself shows what arrived for this account.
A missing record does not become an inferred one. "It is not there" is an answer. A reconstruction is a guess. If the archive cites a signed agreement that is missing, open a coverage gap with an owner and a recovery action. If an agency says a workflow lived in a private tool it cannot export, record the dependency. Then decide whether screenshots, a walkthrough, a configuration copy, API extraction, or a clean rebuild can meet acceptance.
Use explicit states: confirmed-present, expected-missing, not-applicable, provider-excluded, access-blocked, and unknown. A migration can go around a noncritical gap. The handoff receipt still records the gap and its effect on the survival job.
Protect sensitive data during the move
An export can pack years of customer data, private conversations, files, and credentials into one package. Limit who can request, download, extract, and review it. Use approved storage with access logging and encryption that fits the business. Keep raw packages out of widely shared repositories.
Scan for secrets before converted content goes into version control or a folder an agent can read. A transcript may hold an API key, a reset link, a home address, a health detail, or payment information that was never meant to be durable context. Quarantine suspected secrets and sensitive records for an authorized owner. My own keys live in one environment file outside the working folders, never in a note.
Keep enough provenance to decide, without copying sensitive content into every derivative. An inventory can use an item ID, classification, owner, and restricted path. A receipt can record a file hash and a result. Neither needs the private source text.
Decide retention for temporary extraction folders and review copies. Keep the raw package only where the business has decided it belongs. Delete temporary copies only after the canonical destination, backup, and proof are accepted. When the material is sensitive or the contract asks for proof, the deletion gets its own receipt.
Use a parallel-run window for important jobs
For a high-value recurring job, run the owned path beside the vendor path before cutover. Use the same approved input. Compare facts, required sections, source citations, stopping behavior, and action count. Do not require matching prose.
Investigate every material difference. The old system may hold an undocumented rule. The new one may be missing a current source. The old result may be wrong. Parallel output is evidence for review. It does not mean the vendor version wins.
Set the window in advance. Two or three cycles can be enough for a monthly report, but only if fixtures cover the failure cases between live runs. A daily workflow gives more repetitions on its own. Name who reviews differences, what blocks cutover, and what evidence closes each gap.
Keep both paths draft-only during comparison when an external action would happen twice. If the old system stays the live executor, the new path does not get the same send or write access. The test compares preparation. One controlled path owns execution.
Close the window with an acceptance decision. Record the last accepted old-system run, the first accepted owned run, open exceptions, the rollback window, and the owner. Do not drift into two systems that run forever, with corrections split between them.
Rebuild one recurring job
The migration is real when one job runs from owned records with no vendor archive in reach.
Write a task brief that names the result, reader, allowed sources, source order, output, acceptance checks, approval owner, and stop. Then build a small context packet from promoted records. Do not point the new agent at the whole converted archive.
# owned/jobs/monthly-client-report/brief.yaml
job: prepare monthly Client North report draft
allowed_sources:
- owned/clients/client-north/current.md
- owned/decisions/
- owned/procedures/monthly-report.md
- owned/corrections/accepted.md
source_order:
- accepted contractual and business decisions
- current client facts
- accepted procedure
- accepted corrections
archive_role: evidence only
output: owned/drafts/client-north/monthly-report.md
acceptance:
- every status claim cites an owned source
- current renewal date is correct
- no other client data appears
- no external send occurs
stopping_point: draft and receipt written
The archive can stay searchable for investigation. It stays out of routine runs. Retrieval should pull the slice the job needs, not the pile. A small packet cuts stale-source collisions and makes missing records obvious.
Carry corrections and open work separately
Agency archives tend to bury corrections in comments and later chat turns. Extract the wrong behavior, the accepted replacement, scope, owner, effective date, and test. Keep proposed corrections apart from accepted ones.
The article on how corrections become system memory makes the next run the proof. A correction is not migrated until the fixture that previously failed now passes.
Open work needs its own register. A tentative plan does not become a procedure because it was the last message in a thread. Record the owner, next action, blocker, source, and review date. The new operator can then tell commitments from ideas.
Build the acceptance test before cutting access
Run the survival job from a clean session, with no old conversation and no vendor search.
# owned/jobs/monthly-client-report/acceptance.fixture
SETUP clean directory and fresh model session
DENY access to ChatGPT, Claude, Notion, and agency archive
GIVE only brief.yaml and allowed owned sources
EXPECT current renewal date from DEC-2026-081
EXPECT current reporting procedure
EXPECT accepted correction COR-2026-014
EXPECT zero cross-client canary strings
EXPECT draft at defined path
EXPECT no send or CRM write
EXPECT receipt with source paths, versions, tests, and stop
Run the test with the incoming operator. A migration done only by the outgoing agency proves nothing about handoff. The buyer or the replacement worker finds the runbook, runs the fixture, explains any blocked state, and shows where corrections enter.
The AI system ownership transfer checklist expands this into controlled change, rollback, credential rotation, and independent operation. Your AI system is not yours until it can transfer distinguishes file delivery from a working handoff.
Separate model replacement from record migration
The business records stay still while provider adapters change. Put message roles, tool schemas, model identifiers, API parsing, and provider authentication in adapter files. Keep decisions, procedures, correction rules, and acceptance fixtures outside them. Own the memory, the rules, and the data. Rent the model.
Run the same fixture with the replacement model. The prose may differ. The facts, boundaries, required sections, and stop do not.
When I retired one model provider from my own setup, the business rules did not move. Its procedure stayed in the vault, marked superseded with the date, and the root file points to it as history. The work went to other workers under the same review rule.
The guide to switching models without losing business context covers the cross-model fixture. Replacing the model while keeping business memory shows the stable-record and variable-adapter split.
An export existing is no reason to cancel. The AI subscription shutdown test inventories account dependencies, moves durable records, tests the replacement, and distinguishes cancellation from deletion.
Document credentials without copying secrets
The handoff needs an account and credential map. It names each system, owner, role, recovery path, storage location, rotation requirement, and deprovisioning owner. API keys and passwords stay out of the archive and the runbook.
# owned/handoff/access-map.yaml
systems:
- system: reporting repository
owner: operations director
required_role: maintainer
secret_location: company password manager/reporting-repo
rotation_after_handoff: true
- system: email sender
owner: sales owner
required_role: none for draft-only job
secret_location: not provisioned
rotation_after_handoff: false
Transfer access through the business's approved identity and secret systems. Test that the incoming operator can run the accepted job with least privilege. Remove outgoing access only after the owner approves the exact account changes and the recovery paths are proven.
Rehearse the handoff with a person who did not build it
Give the incoming operator what a future replacement would get: root path, inventory, record map, runbook, task brief, fixtures, access map, and support boundary. The outgoing builder's remembered shortcuts stay out of the rehearsal.
Ask the operator to find the canonical record for one important claim, explain which source wins, run the survival fixture, diagnose a staged missing-source failure, push a proposed correction through review, and point to where a consequential action needs approval.
Watch where the operator guesses. A path that makes sense only to its creator needs a clearer index. A test that needs an undocumented environment variable needs setup instructions. A correction path that ends in a private vendor queue has not transferred. Fix the owned files and repeat the failed step.
The rehearsal ends with two receipts. The operator records what they read, ran, changed, and could not finish. The reviewer records acceptance item by item. Open support needs go down as bounded work, not as a promise that the outgoing vendor stays available.
Verify the system after the exit
After the approved account changes, run the survival fixture again. Confirm the owned job no longer calls the old provider, reads the old workspace, depends on the outgoing agency's identity, or writes receipts somewhere nobody can open.
Inspect scheduled jobs, webhooks, API keys, browser extensions, shared links, email forwarding, and automation accounts that might hold the old dependency. Search the live configuration and the runtime logs. A document that says "migrated" does not prove a scheduled process changed. Runtime output outranks it.
Run a backup restore after cutover. Confirm the latest accepted records, runbook, fixtures, and receipts restore together. Check that the incoming owner controls repository administration, storage billing, domain or account recovery, and the credential manager entries the job needs.
Set a short review date after the exit. Look at blocked runs, repeat corrections, missing sources, and unexpected calls to retired systems. Close the migration only when the owner accepts the remaining exceptions and knows who maintains the new path.
Record the final handoff
The final receipt should list raw export hashes, inventory counts, conversion errors, promoted records, rejected or pending candidates, survival-job result, restore result, incoming operator, open risks, and actions still awaiting approval.
The build acceptance list gives a format for files, tests, receipts, permissions, failure cases, and handoff proof. Each item passes or fails. "Mostly migrated" hides which dependency still lives in the old system.
Keep the raw export, the readable derivative, and the maintained record as three separate layers. The raw export serves audit and reprocessing. The readable derivative serves review. The maintained record serves current work. You keep all three when you change models or vendors.
Approval and stopping boundary for vendor AI memory migration guide
Migration work may request approved exports, copy files, hash packages, inventory records, create readable derivatives, extract review candidates, prepare owned records, run offline fixtures, and write receipts.
It stops before deleting provider or agency data, closing accounts, revoking users, rotating credentials, changing retention periods, widening access, sending customer communications, publishing, deploying, or replacing a current system. Each of those needs a named target, owner, recovery path, timing, and fresh approval.
It also stops when export coverage is unknown, a sensitive record has no approved destination, sources conflict on authority, the incoming operator cannot pass the fixture, or the business cannot reach a required account. The receipt names the open dependency.
Where to start for vendor AI memory migration guide
Start with the smallest exit that proves something. Pick one recurring job, preserve the exports it depends on, and run the acceptance fixture from owned records.
Prove one valuable job survives without the old account before you fund a larger archive migration.
