Is it possible to duplicate a Knowledge Base?

[Suzanne Vinson]

One my customers would like to split their knowledge base into two knowledge bases; however they have an extensive list of Categories and subCategories that are assigned to the articles. They do not want to recreate all the Categories and subCategories and reassign them (due to time restrictions). 

Thanks!

[Varsha21]

Hi Creating duplicate kB articles is not good practice, But if your requirement is to create duplicate and if there is no any other way to achieve it then you can create using import (data source,load data)the knowledge arrivals again. But only newly created kB sysid will generate new than previous. Actually I was also face same thing which was related to catalog items.my client requirements was to create duplicate (read only, only image and description) catalog item and newly created items will be available for end user. Thanks

[Suzanne Vinson]

Thanks for the responses!  The use case is that currently there is one kb created for both end users and end user support. We have a flag that allows the end users to only see their articles; however, if we want to take advantage of future capabilities, it would be best to split the two. So the question is referring to duplicating the knowledge base, rename one of them and retire/remove the articles that don't belong via a script (to prevent article duplication).   I think that creating a script to create the articles may work because that is the main issue. I think we could use a script to move the articles (and retain the categories/sub-categories). 

[Sarup Paul]

Please clarify the following -- "however, if we want to take advantage of future capabilities, it would be best to split the two". From product, we do not recommend to duplicate articles, one each for internal vs external. It should be in the same KB. You can use Article templates combined with field level security, so that the same article is shared, with each role seeing what they are supposed to.

See more details here -

Templates

Field level security

[Suzanne Vinson]

Thanks Sarup. I don't want to duplicate any articles. Think of it this way... at the moment, both tier 1 (for the end users) and Tier 3 documentation (for the support personnel) is in the same knowledge base.  Features like attaching articles to incidents that go to the end users would be great; however, we can't do this because the technical documentation should not go to the end user.  So I need to split the two types up. I only want to duplicate the Categories/Sub-Categories, etc. I have a way forward (i.e. to create a new KB and migrate the articles needed in the new KB, then remove them from the old KB). A lot of background work, but doable. 🙂