Egnyte Knowledge Bases are being retired and replaced by Agents. This is an upgrade and not a loss of capability. Existing Knowledge Bases are being automatically converted to Agents with the same file sources, behavior, and settings preserved.
For most users, nothing changes in day-to-day work. Agents answer questions the same way Knowledge Bases did. The only visible difference is their location as they now appear under the Agents section of the AI Assistant page, not a separate Knowledge Bases section.
Teams that have built integrations against the Knowledge Base API or use the Egnyte MCP Server will need to update those integrations. This article explains the associated changes.
Timeline at a Glance
Date |
What happens? |
| July 16, 2026 | In-product banner on the Knowledge Bases page announcing the migration. Helpdesk article was published. |
| August 5, 2026 | Release notes announced that creating a new Knowledge Base now opens the Create Agent flow with a Knowledge Base template pre-selected. |
| By October 22nd, 2026 |
Existing Knowledge Bases automatically converted to Agents, domain by domain. The Knowledge Bases section in the UI is removed. Knowledge Base API endpoints stop accepting requests on the domain. MCP tools ask_knowledge_base and list_knowledge_bases stop working on the domain. |
Changes for End Users
Location of Migrated Knowledge Bases
After migration, Knowledge Bases appear in the Agents section of the AI Assistant page, under agents whose names match the former Knowledge Bases. The behavior is the same as users can ask a question and receive an answer grounded in their Egnyte content.
Required Actions for Users
None. Knowledge Bases are migrated automatically. Users do not need to recreate them, reconfigure them, or re-upload content. The files and folder paths previously connected remain connected.
Creating a New Knowledge Base Going Forward
Use Create New Agent and select the Knowledge Base template. This template is pre-configured with the same behavior Knowledge Bases had. It searches the selected Egnyte content and cites its sources. The instructions can be customized further if needed.
Shared Knowledge Base Links
Shared links for Knowledge Bases are updated to point to the corresponding Agent during migration. Old links should redirect correctly. If a link is broken after the domain migrates, users should create a new share link from the Agent.
Answer Behavior After Migration
The core behavior is the same - the agent searches the configured Egnyte content and answers based on what it finds.
Agents use a more capable reasoning engine, so answers may be slightly more detailed or better-sourced. The agent only answers from the sources configured into it.
For API and Integration Developers
The KB API endpoints are deprecated and will stop working after the domain is migrated. The integration code needs to be updated. Refer here for more details.
Frequently Asked Questions
Will Existing Knowledge Base Content be Preserved?
Yes. The file sources and folder paths configured in a Knowledge Base are carried over to the Agent automatically. No content is lost and no re-indexing is needed.
What if a Domain has Agents Turned Off?
If Agents are not enabled on a domain, migrated Knowledge Bases will not be visible in the AI Assistant interface after migration. Admins should contact the Egnyte Customer Success Manager or Egnyte Support to coordinate enabling Agents before the domain migrates.
Can the Knowledge Base API still be Used after Migration if the Code has not been Updated Yet?
No. After a domain migrates, calls to the deprecated KB API endpoints will fail. The deprecation warning headers currently in API responses indicate the endpoint is going away; those responses serve as a signal.
Does the Agent behave Exactly like the Knowledge Base?
The core behavior is preserved: the Agent searches the connected Egnyte content and answers questions based on what it finds. It will not answer questions outside the scope of that content. The Agent uses an updated instruction set that matches the Knowledge Base behavior by design.
If a Knowledge Base was set up to Transcribe Audio and Video files, does that Still Work after Migration?
Yes. Audio and video transcription is tied to the files configured as sources in the Knowledge Base (now Agent), not to the domain as a whole. After migration, files in the Agent's source folders continue to be transcribed, exactly as they were when it was a Knowledge Base.
A few points worth knowing:
- Transcription applies to files within the Agent's configured sources. Files outside those folders are not transcribed, regardless of the migration.
- Transcription happens for files in Agent sources even if the Agent is never queried. This matches the previous Knowledge Base behavior.
- This is not a domain-level capability. Enabling Agents on a domain does not enable transcription for all files across the domain.
What Should be Done With a Power Automate Flow or Custom Connector that Uses the KB APIs?
Update the flow to call the Agent endpoints instead. The agentId is the same UUID as the kb-id. The main code change is adopting the async pattern: call the Agent ask endpoint, save the executionId, and poll for the result rather than reading it from the initial response.
Are there API Reference Docs for the New Agent Endpoints?
Yes. The Egnyte Developer Portal contains the Agent API reference, including the ask and status endpoints. Those docs can be used alongside this guide.
What Happens to the Shared Link for a Knowledge Base after Migration?
Shared links for Knowledge Bases are updated to Agent links during migration. Egnyte recommends testing shared links on the domain after migration and recreating any that do not resolve correctly.
Will there be Any Further Deprecations of AI APIs?
The ask_ai_assistant MCP tool and its corresponding API are being updated to use an async model (returning an executionId and requiring a status poll), consistent with the Agent pattern. The tool itself is not being removed - only the underlying call mechanism is being modernized. Updated documentation will be published separately.