> For the complete documentation index, see [llms.txt](https://docs.poweromni.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.poweromni.ai/en/migration.md). # Migration The Power Omni platform is going through an important infrastructure update that supports the platform’s AI agents. Until now, the agents used the classic Microsoft Foundry foundation. This structure served the product well for a long time, but Microsoft is discontinuing it and replacing it with the new generation of Microsoft Foundry Agents. For this reason, the Power Omni agents will need to be migrated to the new infrastructure. This migration keeps Power Omni aligned with Microsoft’s evolution and prepares the platform for more modern features, greater stability, and new possibilities for AI agents. ## Update notice available When the migration is available for your environment, Power Omni will display a notice at the top of the screen: "An important update is available for your environment. Learn more about the benefits." By clicking Learn more, you will be redirected to the New Foundry Migration page. On this page, you can learn about the benefits of the update, review the migration impacts, and start the process. ## New Foundry Migration page On the New Foundry Migration page, you can review the main information about the update before starting the process. This page shows the reason for the migration, the important deadlines defined by Microsoft, the immediate benefits, and the possibilities that the new infrastructure brings to the product. ## Why is this migration necessary? Microsoft is gradually ending support for the older technologies used in the classic version of Foundry. The Assistants API, used as the foundation for agents in previous architectures, will be discontinued on August 26, 2026. After this date, agents that still depend on this technology may stop working. In addition, support for Foundry Classic will end on March 31, 2027. After this date, migration will no longer be possible from the old foundation. For this reason, we recommend completing the migration in advance. ## What changes in practice? The main change happens in Power Omni’s technical layer. Users will continue to access their agents within the platform, but the infrastructure behind them will start using the new Microsoft Foundry foundation. With this, agents will run on a more up-to-date structure, better prepared to handle long conversations, file queries, connectors, and new tools that may be added to the product. ## Immediate benefits With the new infrastructure, agents will provide more fluid responses. The streaming mechanism was rewritten in the new platform, allowing responses to be delivered more continuously, with fewer interruptions in long texts or more complex queries. Another important point is conversation stability. The new architecture handles each conversation in a more isolated way, reducing issues where the history of one session could interfere with another, especially in agents with many files, documents, or active connectors. ## What does this new foundation enable for the future? The migration also opens the door to new possibilities within Power Omni. Among them is support for models beyond the GPT family, including models such as Claude, DeepSeek, Grok, and others available in the Microsoft catalog. It will also be possible to evolve the use of native tools, such as real-time web search and code interpreter, as these resources are evaluated and integrated into the product. Another possibility enabled by this new foundation is agent collaboration. This allows the creation of flows where one agent can trigger another, enabling more advanced and specialized automations. These features depend on the completed migration and may still go through validation before being released in Power Omni. ## How do I start the migration? The process is simple. Access the New Foundry Migration page and review the information displayed. When starting the migration, Power Omni will display a confirmation window called Confirm migration start. This screen shows what will be temporarily blocked, what will be transferred, and which points require attention before continuing. To proceed, click Confirm and Start. If you do not want to start yet, click Cancel. ## Features blocked during the process While the migration is in progress, some actions will be temporarily unavailable in the environment. During this period, it will not be possible to create, edit, or delete agents. It will also not be possible to create, edit, or delete connectors of the following types: Document, OpenAPI, Fabric, N8N, Logic App, and SharePoint. Uploading and deleting files will also be blocked until the migration is completed. This block is temporary and helps prevent changes to the environment while resources are being transferred to the new infrastructure. ## Conversation history The current conversation history of the agents will not be transferred. This means that old threads and interactions will not be migrated to the new infrastructure. After the migration is completed, new conversations will start from zero. The agents will be migrated, but the previous conversation history will not be kept. ## What will be transferred? The main environment resources will be automatically migrated to the new infrastructure. The following items will be transferred: Agents, including settings, instructions, and system prompt. Connectors. Files associated with the agents. The files will be re-uploaded to the new platform during the migration. ## Possible partial failures Some Document connectors may fail during the migration. This can happen, for example, when a file is corrupted, when there is a quota limit, or when the re-upload to the new infrastructure is not completed correctly. In these cases, the agent will be created without the connector that had the issue. After the migration is completed, this connector can be recreated manually. ## Tracking progress After confirming the start of the migration, Power Omni will display the Migration in progress status. You can track the progress on the migration screen or by clicking the View Progress button. While the process is in progress, wait for it to finish before trying to change agents, connectors, or files. ## What should I check after migrating? After completing the migration, validate the following points: Whether the agent responds normally. Whether the connected documents are still being queried. Whether the configured connectors are still working. Whether the responses remain aligned with the agent’s instructions. If you notice any unexpected behavior, contact Power Omni Support. ## Do I need to recreate my agents? Not necessarily. The migration was designed to update the infrastructure that supports the agents without requiring users to rebuild everything from scratch. Even so, we recommend reviewing the most important agents after the migration, especially those that use documents, connectors, or more specific instructions. ## Can I continue using the old version? The old version will remain available only during the transition period. Since Microsoft has already defined the deadlines for ending the older technologies, we recommend migrating as soon as possible to avoid future interruptions. ## Need help? If you have any questions during the process, contact Power Omni Support. Our team can help with the migration, review the environment, and assist with validating the agents after the update.