Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free trial
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Agents
  • Computers
  • Drive
  • Automations
  • AI Gateway
  • All features →
  • LLM cost calculator
  • Token counter
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Benchmarks
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Help Center
📥

Import from Claude

Found this helpful? Share it:

Moving from claude.ai? Import your export ZIP and your conversations, Projects, and project instructions all find a home in idapt 📥

Import your Claude history

  1. On claude.ai, go to Settings → Privacy → Export data. The export ZIP arrives by email.

  2. In idapt, open Settings → Import, choose Claude, select the destination workspace, then pick the ZIP.

  3. Review your projects: each one lands as a Drive folder, and projects with instructions also become agents you can chat with right away.

How Projects come over

Each Claude Project becomes a folder in your Drive at Claude Import/Projects/<name>, holding the project's text documents.

A project that has instructions also becomes an agent: its system prompt is those instructions, and it gets its own memory Notes box. Your project setup keeps working as a persona you can keep talking to.

What to expect

  • Conversations are linear. Claude's export doesn't include branch structure, so each chat imports as a single thread.

  • File uploads survive as text. The export contains no binary files, so anything you uploaded to a conversation appears as its extracted text, inline on the turn where you attached it.

  • No model tags. Claude's export doesn't record which model wrote each reply, so imported messages don't carry a model attribution.

Importing again

Re-imports are deduped. Conversations are matched by Claude id and normalized content, project documents by file content, and project agents by name, so running the importer twice does not create doubles.

That makes it safe to import a fresh export later. The completion summary separates new, already imported, and skipped content.

Related articles

📥

Import from ChatGPT

Move your ChatGPT history into idapt: conversations, branches, tool calls, and attachments included.

📦

Bring your data to idapt

Import your chats, files, and issues from the tools you already use, and get everything back out in standard formats.

🤖

Agents

Create AI personas with custom instructions, their own memory, and their own default model.

Up next

How we score models

Understand the capability score, the named public benchmarks, and the speed, reliability, and cost numbers on every model page.

Was this helpful?