Provider-to-provider migration guides
Switching AI providers is rarely a find-and-replace job. Endpoints, auth, message formats, streaming, tool/function-calling schemas, token counting, and stop conditions all differ — and the differences hide in details that only surface in production. Each guide below maps one provider's API onto another, field by field, with copy-paste before/after code and a rollout checklist.
Pick your route from the directory. The hard part is almost always whichever side uses Anthropic's Messages API or Gemini's native API; anything that's OpenAI-compatible (DeepSeek, and Gemini's compatibility endpoint) is closer to a config change.
Migration directory — every provider pair
| From | To | Difficulty | Guide |
|---|---|---|---|
| OpenAI | Anthropic | moderate | Read guide → |
| OpenAI | Google Gemini | involved | Read guide → |
| OpenAI | DeepSeek | easy | Read guide → |
| Anthropic | OpenAI | moderate | Read guide → |
| Anthropic | Google Gemini | involved | Read guide → |
| Anthropic | DeepSeek | moderate | Read guide → |
| Google Gemini | OpenAI | involved | Read guide → |
| Google Gemini | Anthropic | involved | Read guide → |
| Google Gemini | DeepSeek | involved | Read guide → |
| DeepSeek | OpenAI | easy | Read guide → |
| DeepSeek | Anthropic | moderate | Read guide → |
| DeepSeek | Google Gemini | involved | Read guide → |
Numbers and model names change — every guide is dated; confirm against current provider docs before migrating. Need your own traffic priced across providers first? Use the cost calculator.