Sample · Illustrative, details redacted
What your context document actually looks like
Below is a representative excerpt of the document a migration produces — the shape, density and tone are real, with names and specifics redacted. A typical full document runs several times this length, built from every substantial conversation in your export.
Context for your new assistant
Distilled from 2,416 conversations · Aug 2024 – Aug 2026 · generated by ChatGPTToClaude
About me
- Indie product designer and developer based in ; ships small web products solo, comfortable with TypeScript and React but not a backend expert.
- Working language is English; writes customer copy in English and French. Prefers concise answers over exhaustive ones.
Active projects
- (main project): a booking tool for . Stack: Next.js, Postgres on , Stripe. Currently blocked on the calendar-sync rewrite discussed extensively in June.
- Newsletter: weekly, ~1,800 subscribers. Voice: first person, dry humor, no emoji. Drafts are always reviewed against the “three edits” checklist before sending.
Preferences & standing instructions
- Code answers: TypeScript, functional style, no classes; explain trade-offs briefly, then give the full file — not fragments.
- Never suggest renaming the product again (decided March 2026, revisited twice, closed).
- Budget conscious: prefers boring, cheap infrastructure over novel services.
People
- — co-founder on the booking tool; owns sales. Prefers summaries as bullet points before calls.
- — accountant; quarterly VAT questions usually relate to EU digital-services rules.
Decisions & context that would otherwise be lost
- Chose Stripe over (April 2026) because of EU VAT handling — revisit only if fees exceed 4%.
- The onboarding email sequence was rewritten twice; the current v3 tone (“helpful colleague, not marketer”) is the keeper.
- Abandoned the mobile app idea (January 2026) after usage data showed 91% desktop traffic — do not re-propose without new data.
Why this format works
- It's context, not chat logs. Your new assistant doesn't need ten thousand messages — it needs the conclusions those messages produced.
- It's organized the way assistants read. Clear sections, one fact per line, decisions with their reasoning — so the model can use it instantly instead of summarizing it first.
- It stays yours. Copy it, edit it, delete lines — it's a Markdown document, not a proprietary format.
Where to paste it
Going to Claude: paste it into a Claude Project's knowledge, profile preferences, or the start of a new conversation. Going to ChatGPT: paste it into a new chat with “Please remember this about me”, into Custom Instructions, or into a Project.