Migrate
Migrate from Chatbox
One JSON export moves your chats; your provider keys reconnect as BYOK in the gateway.
Launching soon: this surface is rolling out
What moves
| Chatbox | In idapt | How |
|---|---|---|
| Conversations (JSON export) | Chats via the universal chat-JSON importerChatbox exports conversations to a file; the JSON maps onto the documented shape. | Automatic |
| Provider API keys | BYOK provider connections in the Gateway tabMatching models bill straight to your provider accounts. | Manual |
| Custom model endpoints | Custom models on an OpenAI-compatible connection | Manual |
| Prompts and assistants | Agents | Manual |
How to migrate
- 1
Export your Chatbox data
In Chatbox, export your conversations from the settings; you get a JSON file with your chat history.
- 2
Upload in idapt
Settings → Import → "Other apps (JSON)". The help article documents the exact chat-JSON fields if your export needs a small transform.
- 3
Reconnect your keys
Add the same provider keys as BYOK in the Gateway tab, or skip keys entirely and use idapt's routed catalog with one bill.
Bring the API keys you already pay for
Connect your own provider keys (OpenAI, Anthropic, OpenRouter, Google AI Studio, xAI, DeepSeek, and more) and matching calls bill straight to your provider account instead of idapt credits. Local models run free via Ollama on your paired computers. Your existing spend comes with you. Nothing is locked to ours.
FAQ
Do my API keys still work?
Yes. Connect them as BYOK keys and matching models bill straight to your provider accounts; custom OpenAI-compatible endpoints come along as custom models.
What changes day to day?
Routing and failover replace per-provider setup, history lives in the workspace instead of one device, and files, agents, and computers sit around the chat.