Move More to Lightning Knowledge—Communities Topics and Article Search Data (Beta)

The Lightning Migration Knowledge tool takes the guesswork out of moving from Salesforce Knowledge to the new Lightning Knowledge data model. Follow the tool’s prompts to unify your data under a powerful new Knowledge object and to use Knowledge with the Lightning Experience user interface. During the migration process, if your org has any related cases, data categories, communities topics, work order items, field service work orders—or report data for article views, votes, or searches—those items work properly after the migration.


As a beta feature, the Lightning Knowledge Migration Tool is a preview and isn’t part of the “Services” under your master subscription agreement with Salesforce. Use this feature at your sole discretion, and make your purchase decisions only on the basis of generally available products and features. Salesforce doesn’t guarantee general availability of this feature within any particular time frame or at all, and we can discontinue it at any time. This feature is for evaluation purposes only, not for production use. It’s offered as is and isn’t supported, and Salesforce has no liability for any harm or damage arising out of or in connection with it. All restrictions, Salesforce reservation of rights, obligations concerning the Services, and terms for related Non-Salesforce Applications and Content apply equally to your use of this feature. For information on enabling this feature in your org, contact Salesforce.

Where: This change applies to Lightning Knowledge in Professional, Enterprise, Performance, Unlimited, and Developer editions with Service Cloud.

Who: Users with Admin permissions can run the migration tool. A Salesforce product manager must enable the Lightning Knowledge Migration Tool for you. For details, contact your Salesforce representative.

How: After some initial preparation, follow the prompts and let the migration tool do the heavy lifting. The Knowledge object is optimized for Lightning by using record types instead of article types, and files instead of file fields. After you change the data model, you can use either Lightning Experience or Salesforce Classic. After migration, an admin manually revises customizations to use the new Knowledge object.