How to migrate an existing Content Understanding analyzer from Foundry (classic) to Content Understanding Studio?

1. Importing or loading an existing analyzer definition into Content Understanding Studio

The provided information describes two main experiences:

• Foundry (classic), which uses the 2025-05-01-preview API.
• Content Understanding Studio and the updated Foundry (new) portal, which are aligned with the GA 2025-11-01 API and are positioned as the recommended path for building and refining analyzers.

The migration guidance explicitly recommends rebuilding preview analyzers in the GA environment rather than migrating them in-place. The available analyzer lifecycle operations in GA (copy, delete, replace) are described for GA analyzers and for moving analyzers between Content Understanding resources and Foundry resources, not for importing preview analyzers into Studio.

From the available information, there is no documented mechanism to:

• Export a Foundry (classic) 2025-05-01-preview analyzer definition and
• Directly import that definition into Content Understanding Studio as a GA (2025-11-01) analyzer.

Instead, the recommended pattern is:

• Use Content Understanding Studio to rebuild the analyzer (schema, fields, and logic) on the GA pipeline.
• Then use analyzer lifecycle APIs (copy, replace) to manage versions and move GA analyzers across resources once created.

2. Known issues when opening Foundry (classic) projects in Content Understanding Studio

The documentation distinguishes the environments and APIs but does not describe a supported workflow where a Foundry (classic) project is “opened” directly in Content Understanding Studio, nor does it list specific issues such as:

• Training data not transferring
• Labeled samples not transferring
• Field schemas not transferring

Instead, it emphasizes that:

• Foundry (classic) supports the preview API 2025-05-01-preview and includes some preview-only features.
• Content Understanding Studio is a complementary UX designed for GA and for Document Intelligence customers transitioning to Content Understanding, with its own guided workflows for labeling, testing, and refinement.
• Analyzer lifecycle APIs (copy, delete, replace) apply in the GA (2025-11-01) context and are referenced in the GA migration guidance.

Given this, the documented guidance is to treat preview analyzers and GA analyzers as separate and to rebuild in Studio for GA, rather than relying on automatic transfer of training data, labels, or schemas from Foundry (classic). No specific cross-environment transfer issues are enumerated; the risk is implicitly avoided by recommending a rebuild.

References:

• Compare Content Understanding in Foundry and Content Understanding Studio
• Migrate from Azure Content Understanding Preview to GA
• What's new in Azure Content Understanding in Foundry Tools?
• Copy custom analyzers (programming-language-rest)
• Copy custom analyzers (programming-language-python)
• Copy custom analyzers (programming-language-csharp)
• Copy custom analyzers (programming-language-javascript)
• Copy custom analyzers (programming-language-typescript)