---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Knowledge content migration from v2 to v3

# Knowledge content migration from v2 to v3 {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To use the new functionality available in knowledge v3 with legacy articles, you must
migrate these articles out of the default knowledge base.
To migrate knowledge content, move articles out of the default knowledge base by
changing the Knowledge Base value for each article. The state
of the article remains unchanged when moving articles. After selecting a new
knowledge base, assign a category to each article using the category structure
defined in the new knowledge base.

After you migrate a knowledge article, the legacy feedback functionality is
automatically replaced with the new knowledge feedback mechanisms. Legacy feedback
is copied to the Live Feed Message \[live_message\] table to ensure previously
submitted feedback is available for knowledge v3 articles.
**Zugehörige Konzepte**   

* [Migrate to Knowledge Management v3](https://servicenow-prod.fluidtopics.net/ZxV6xrvj36GZwgOqTNKiJg "When you migrate to Knowledge Management v3 from v2, you must migrate legacy knowledge content and any customizations you have made to the Knowledge Base applications.")  
**Zugehörige Tasks**   

* [Move a knowledge article](https://servicenow-prod.fluidtopics.net/aMfMC4hgkyyKYPHF5dCmhQ "You can move articles between knowledge bases.")  
**Zugehörige Verweise**   

* [Knowledge workflows](https://servicenow-prod.fluidtopics.net/SZj7_xuHdnlVADCo9u7Vhg#r_KnowledgeWorkflows "The publishing and retirement processes for a knowledge article are controlled by workflows defined for the knowledge base that the article belongs to.")

