Knowledge Management v3 migration

Knowledge management has significantly changed with the introduction of knowledge v3 starting with the Fuji release.

Knowledge v3 has several key differences from knowledge v2, the version of knowledge management that was available until Eureka release. The knowledge v3 plugin is activated by default starting with the Fuji release.

The following podcast provides more information on what is new in Knowledge Management v3.

- topic/object https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/278373569&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&visual=truesoundcloudobject:1;28:219file:/mnt/jenkins/workspace/dita/zoominV4_2.4.4_LCodeFreezebranch_004-prod-london-build/doc/source/product/knowledge-management/concept/c_KMv3Migration.dita

When upgrading from Eureka or earlier versions, if you intend to use the new features available in knowledge v3, you have to migrate legacy knowledge content and any customizations you have made to the Knowledge Base applications.

The following video provides more information on how to migrate from Knowledge Management v2 to v3.

<span>Migrating from Knowledge Management v2 to v3</span>

Table 1. Key differences
Legacy Knowledge	Knowledge v3
One knowledge base.	Multiple knowledge bases.
A single lifecycle workflow shared by all articles.	Separate, customizable workflows available for each knowledge base.
Two-level organizational structure with Topic and Category. A single organizational taxonomy shared by all articles.	Category structure with any number of levels. Each knowledge base has a unique category taxonomy.
Permissions defined per article using roles and ACLs.	Permissions defined per knowledge base or article using user criteria.