# Migration overview Coming from another tool? These guides cover the major patterns.


From LangSmith	Port datasets, judges, eval configs.	Read
From Braintrust	Port datasets and scoring.	Read
From Galileo	Port hallucination metrics.	Read
From Promptfoo	Port test/assertion configs.	Read
From MLflow	Port runs and metrics.	Read
From Arize	Port traces and observations.	Read

## General migration approach 1. Inventory what you have in the source tool 2. Pilot a single team / feature for \~2 weeks 3. Run dual (Stratix + old tool) for one full release cycle 4. Decommission old tool when scores correlate See [Plan a migration](https://github.com/LayerLens/gitbook-full/blob/main/06-build/migration/guides/plan-migration.md) and [Dual-run migration](https://github.com/LayerLens/gitbook-full/blob/main/06-build/migration/guides/dual-run-migration.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.layerlens.ai/6.-build-wire-your-code/migration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.