What you can migrate
The skill verifies the recreated records in AX and does not rerun evaluators or make model calls. If AX cannot preserve a dataset-version relationship, it stops instead of importing an incorrect relationship.
Migrate existing Phoenix data
1
Install the migration skill
2
Ask your coding agent to start
Use the Arize Phoenix migration skill. I want to migrate my Phoenix data to AX.The agent inventories Phoenix, proposes fresh AX destination names, and asks what you want to migrate. You can migrate everything supported, traces only, dataset and experiment data only, or selected resources. You can also choose the destination AX project name.
3
Provide connection details privately
Give the agent the path to an existing local
.env, or let it create a secure credential-entry command for you to run in a separate terminal window. Do not paste API keys into agent chat.- Create or find a Phoenix API key. A key is optional only for self-hosted Phoenix with authentication disabled.
- Create or find an AX API key.
4
Review the inventory and migrate
The agent shows what it found, what is excluded, the AX organization and space, and the proposed project and dataset names. Reply
go to accept everything shown, or specify a subset or another project name.A typical small or medium migration takes about 5–20 minutes. Large exports or AX trace indexing can take longer.5
Open the verified results
Wait for the agent to report
verified, not only uploaded. Its final table links directly to the AX trace project, dataset examples and versions, and experiments with stored evaluation results.Send new application traces to AX
Historical migration does not redirect your running application. Update its trace exporter so new spans go to AX.1
Install the AX tracing SDK
2
Register the AX tracer
Keep your existing OpenInference instrumentors and manual spans. Replace the Phoenix registration with AX credentials and a space ID:See Configure your tracer for other frameworks, JavaScript, regions, and manual OpenTelemetry setup.
3
Verify and finish the cutover
For production applications, send traces to Phoenix and AX for one representative traffic cycle. Compare trace counts, span trees, attributes, sessions, and users over the same time window. Once they match, stop the Phoenix export path and remove its credentials from your deployment.
Keep Phoenix running until the historical migration is verified because the skill reads directly from the source instance. See the migration skill source for current behavior and limits.