Bring your data to idapt
Found this helpful? Share it:
Found this helpful? Share it:
Switching tools should not mean starting over. Your chat histories, notes, issues, and code can all move into idapt, and everything can move back out again. This page is the map 📦
Each importer lives right where the data lands:
ChatGPT: upload your export ZIP at Settings → Import and your conversations come over. See Import from ChatGPT.
Markdown and text notes: pick a folder (an Obsidian vault, a Notion export, or any folder of files) with the Knowledge Base's Import folder button. See Import markdown notes.
If your scripts or apps already talk to an AI API, you do not rewrite them. idapt exposes compatible base URLs, so switching is a one-line change:
OpenAI-compatible: see the OpenAI API migration guide.
Anthropic-compatible(including Claude Code): see the Anthropic API migration guide.
OpenRouter-compatible: see the OpenRouter migration guide.
The same key works across all three, and every call runs on idapt's 200+ model catalog.
Imports are not a one-way door. Every resource exports in a standard format:
Any chat exports as Markdown, plain text, JSON, or PDF
The Knowledge Base exports as a ZIP of markdown files
Drive files support bulk download
Two lanes, one rule: whose surface do you live in after the swap? The AI Gateway quickstarts keep your current tool and use idapt as its AI provider: swap the base URL, nothing moves. The migrate guides move you INTO idapt: chats, notes, skills, and files follow you, and you stop using the old tool.
Coding agents do both in sequence: point Claude Code, Codex, or OpenCode at
idapt to evaluate it on your real workload, then run
idapt chat import to bring the session history across when you
switch. See Import chats from
coding agents.
See Export your data for the full list of export paths.
Was this helpful?