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 ChatGPT

Found this helpful? Share it:

Moving from ChatGPT? Bring your whole history with you. The importer recreates your conversations in idapt, branches, tool calls, and attachments included, so you can pick up any thread right where you left off πŸ“₯

Import your ChatGPT history

  1. In ChatGPT, open Settings β†’ Data controls β†’ Export data. OpenAI emails you a link to a ZIP file. The link expires in 24 hours, so download it promptly.

  2. In idapt, open Settings β†’ Import, choose ChatGPT, select the destination workspace, and pick the ZIP. Progress streams live: conversations first, then attachments.

  3. Open any imported chat and keep talking. Your default agent responds, on any model you pick.

What survives the import

Conversations come over as real idapt chats, not flat transcripts:

  • Branches, if you edited a message or regenerated a response in ChatGPT, those alternatives import as real branches, and the branch you had active is restored. Navigate them like any idapt branch. See Editing messages and branching.

  • Tool calls, turns where ChatGPT ran Python, generated images with DALLΒ·E, or browsed the web keep those steps visible in the conversation.

  • Attachments, images and other files land in a ChatGPT Import folder in the selected workspace and are linked from the right messages. Provider transport ids are removed from filenames, and same-name files receive a numbered suffix when their contents differ.

Size limits and skipped files

The upload accepts export ZIPs up to 1 GB compressed. Imported attachments count against your storage, so the import also needs enough remaining space.

Individual attachments can be skipped when they're too large, over your storage quota, or empty. Every skip is reported per file at the end, so you know exactly what didn't make it.

Importing the same export twice

Running an import again with the same ZIP is safe. Conversations are matched by their ChatGPT id and normalized content, while files are matched by content. Matches are reported as already imported instead of creating copies.

Import a fresh export whenever you want to add newer conversations. The completion summary separates new, already imported, and skipped conversations and attachments.

FAQs

Related articles

πŸ“¦

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.

✏️

Editing messages and branching

Edit sent messages, regenerate responses, and navigate conversation branches.

πŸ’¬

Managing conversations

Pin, rename, archive, export, share, and delete your conversations.

Up next

Import from Claude

Bring your claude.ai conversations and Projects into idapt. Project docs become Drive folders and project instructions become agents.

Was this helpful?