Dependencies to be taken care of while migrating knowledge articles from one instance to anotherIssue Customers who want to migrate articles from one instance to another should consider and move all the dependency tables information as well. This article provides high-level details of which tables need to be considered when moving from one instance to the other. Dependency Tables Knowledge bases - kb_knowledge_base tableCategories - kb_category tableCan Read/Cannot Read/ Can Contribute/Cannot Contribute user criteria - kb_uc_can_read_mtom_list tableKnowledge Author, Approver users - sysapproval_approver_list tableArticle Domain if not global - sys_domain tableWorkflow - workflow tableworkflow context - wf_context tableKnowledge Feedback - kb_feedback tableKnowledge Feedback Tasks Attachments - Sys_attachment tableRelated Products -Attach to Task entries - m2m_kb_task tableKnowledge Keywords - meta KB Use - kb_use table If the i18n Plugin is Active, then make sure these tables are migrated Translated Articleskb_department entries If the Knowledge Advanced plugin is Active, make sure these tables are migrated Knowledge VersionsKnowledge Summary ReleaseAllRelated LinksThe dependency tables information provided on this article is only high level information. There can be more tables involved depending on the plugins activated on the customer's instance. A thorough testing is needed once all the tables are migrated properly.