Migrate
Migrate from LM Studio
Bring your local conversations along and keep local inference: Ollama pairing routes your machine's models into the workspace.
Launching soon: this surface is rolling out
What moves
| LM Studio | In idapt | How |
|---|---|---|
| Conversations (JSON files on disk) | Chats via the universal chat-JSON importerLM Studio keeps conversations as JSON on disk; map them to the documented shape (a small transform) and upload. | Automatic |
| Downloaded models (GGUF / MLX) | Local AI via Ollama on the same machineOllama manages its own model store: pull the same open models there and pair the machine. | Manual |
| System prompts and presets | Agents | Manual |
| Local OpenAI-compatible server workflows | The hosted gateway's OpenAI-compatible endpointSame protocol, one base-URL change, plus Anthropic- and OpenRouter-compatible endpoints. | Manual |
How to migrate
- 1
Locate your LM Studio conversations
LM Studio stores chats as JSON files on disk; the app's settings show the data folder they live in.
- 2
Convert and upload
Match the documented chat-JSON shape (the help article lists the exact fields), then upload at Settings → Import → "Other apps (JSON)".
- 3
Pair your machine for local models
Install Ollama, pull the models you used, and pair the computer. idapt routes to it as a free local provider, with a hardware-fit filter showing what the machine can serve.
FAQ
Can idapt read LM Studio's GGUF files directly?
No. idapt's local lane runs through Ollama, which manages its own model store: pull the same open models there and the workspace discovers them on your paired machine.
Why move if local already works?
You keep local (private, no per-token price) and add what a desktop app does not have: the cloud catalog in the same chat, files that persist, agents, and automatic fallback when a job outgrows the machine.