Migration Feature Checklist

Use this checklist to identify which parts of an existing gateway integration can move unchanged and which need explicit validation. It was last reviewed on August 23, 2026.

Core request compatibility

Capability	Phaseo support	Migration action
OpenAI-compatible authentication	Supported	Change the base URL and API key, then run one authenticated request.
Chat Completions	Supported	Test normal, streaming, tool-calling, and structured-output requests.
Responses	Supported	Test input formats, streaming events, tools, and response parsing.
Anthropic Messages	Supported	Verify Anthropic-specific headers, system prompts, and streaming events.
Model identifiers	Phaseo catalog IDs	Validate every production ID with `GET /v1/models`; do not assume aliases match.
Embeddings, image, and audio endpoints	Supported by model and provider	Verify the model supports the required operation before cutover.

Routing and policy controls

Capability	Phaseo support	Migration action
Provider ordering	`provider.order`	Recreate only the ordering rules the workload still needs.
Provider allow and ignore lists	`provider.only` and `provider.ignore`	Validate provider IDs and confirm at least one route remains available.
Price, latency, or throughput sorting	`provider.sort`	Inspect the selected provider in Gateway usage after testing.
Zero data retention	`provider.require_zero_data_retention`	Confirm the model has a matching provider before enforcing the requirement.
Regional execution and data residency	Request fields and workspace privacy defaults	Test both successful routing and the no-matching-provider failure path.
Reusable prompts and defaults	Presets	Move shared configuration into a preset instead of duplicating it across callers.

Operations and rollout

Capability	Phaseo support	Migration action
Request attribution	App ID, name, URL, and categories	Keep attribution headers during migration and verify app grouping in the dashboard.
Request and provider details	Gateway usage and generation records	Compare provider, latency, token usage, and pricing for representative prompts.
Batch and async jobs	Batch, file, video, webhook, and websocket APIs	Validate status transitions, terminal billing, cancellation, and result retrieval.
Replay support	Generation records expose replay metadata when available	Confirm the original endpoint and payload can be recovered for failed requests.
Gradual rollout	Client or infrastructure traffic splitting	Keep rollback as a base URL and credential change until the cutover is stable.

Features that require workload-specific validation

Do not treat API compatibility as proof that these behaviors are identical:

automatic provider selection and fallback order
prompt-cache affinity and cache pricing
provider-specific request fields
response-only metadata
rate limits and retry timing
data retention, residency, and training policies
exact model availability and price

Run production-like prompts and failure cases before moving meaningful traffic.

Overview

Models & Routing

Features

Integrations

Workspace & Access

Reliability & Operations

Platform & Research

Migration Guides

Community

Migration Feature Checklist

Migration Feature Checklist

Core request compatibility

Routing and policy controls

Operations and rollout

Features that require workload-specific validation

​Migration Feature Checklist

​Core request compatibility

​Routing and policy controls

​Operations and rollout

​Features that require workload-specific validation

​Related guides

Migration Feature Checklist

Core request compatibility

Routing and policy controls

Operations and rollout

Features that require workload-specific validation

Related guides