Cross-Provider Migration to Mistral

Overview

Treat migration as behavior and operations redesign, not field renaming. Preserve the application contract while re-evaluating models, prompts, streams, tools, safety, state, data, spend, and incidents.

Prerequisites

• A source workload inventory and application-owned adapter.
• Golden/adversarial evaluation sets with governed data.
• Current Mistral access, dual-run budget, canary, rollback, and exit owners.

Current Contract

Chat, embeddings, classifiers, files/OCR, audio, batch, Workflows, and Public Preview stateful APIs are provider-specific. No source feature, model, tool, safety result, or state object is automatically equivalent.

Authentication

Keep source and Mistral credentials in separate secret references with independent owners. Dual-run data must be approved for both providers.