Requirements to Enable Lightning Knowledge Migration Tool

Lightning Knowledge Migration Tool availability

The Lightning Knowledge Migration Tool was only made available or turned on by default in sandbox organizations.

The feature has not been automatically enabled in production organizations or instances. If your organization has multiple article types, full testing of the tool must be completed in recently refreshed, full sandbox prior to enabling the tool in production environments.

If your organization has only one Article Type, the testing pre-requisites below are still recommended but NOT required. Single article type migrations are low risk in comparison to multiple article type migrations so extensive sandbox testing is not necessary. Support is pre-approved to enable the tool in production orgs that have only 1 article type.

Running the tool in sandbox is necessary to make sure you have fully tested the implications of the multiple article type migration process and identify your organization's unique requirements to develop an implementation plan to minimize potential production-impacting issues. Exact testing prerequisites are outlined in the required questionnaire for approval below.
 

The 'Lightning Knowledge Migration Assistant' setup section is only available:

• In Lightning Experience Setup

• For System Administrators with the 'Customize Application' profile permission and an assigned Knowledge license.

• In orgs where Lightning Knowledge has not been enabled

If you do not have a full copy sandbox available, reach out to your Account Executive to discuss the possibility of temporarily provisioning a full copy to test the tool.

 

Once you have completed testing your multiple article type migration and creation of your implementation plan in sandbox, an Administrator must log a case with Salesforce Support to begin the approval process to request enabling the tool in production.

Note: New approval requests submitted during weekends or holidays will not be reviewed or processed until at least the following business day. Each request needs to be validated to ensure that you're ready for production enablement which may take up to a week so ensure you plan accordingly with enough time for proper review and approval.

 

Include complete answers to the following questions and ask Support to reference the internal article # 000384023 in your case details to help expedite review and evaluation:

• The sandbox where the tool was tested should have been refreshed within the last month.

• Sandbox testing and production migration must occur on the same release.

Note: Please take a screen capture of the migration process Validation step results before accepting (as seen under step 13. of the Migrate Multiple Article Type documentation) for Support's reference and review.

2. Are you prepared to disable users access from editing and creating articles (and related records) during Migration?

3. Have you fully verified the sandbox org after the migration completed?

4. Do you plan to complete a full copy sandbox refresh to maintain as a backup of production's Classic Knowledge data?
 

Note: Leave your full copy sandbox in the post migration state to allow Support to review and validate the migration results as part of the approval request process for production.

If you do not plan to refresh after Support reviews the sandbox migration results, please carefully review the below details as requests without a recent full copy backup or other valid backup will be denied.

Note: The best option is to perform a refresh of a full copy sandbox to use as backup but if your full copy sandbox is not eligible for refresh, Support may temporarily lower the refresh interval at your request in order to allow you to refresh it early for the purpose of creating a backup. If it's not possible to refresh a full sandbox prior to your request to enable in production for any other reason please briefly explain why and verify/confirm at minimum, that you have performed and downloaded a full data export including all objects and both options for attachments and files or content as outlined in the Export Backup Data from Salesforce documentation.

Requests to enable without a recent full copy refresh containing pre-migration Classic Knowledge data or confirmation of completion and download of full data export files to use as backup will be rejected.

A full copy sandbox backup is recommended for multiple article type migrations because the process not only affects Knowledge articles, versions, and translations but may also affect data categories assignments, smart links, article feed posts, case associations, field service work order, work order items, work type links to articles, viewstats, votestats, etc.

5. Have the AppExchange apps and customizations (APEX, using APIs, etc) in your production org been tested in a sandbox?

6. When are you planning to start your production migration and when is your target production go-live date? Our Product Management and Engineering teams would like to be aware of when customers plan to migrate their production organization. If this date changes, please let us know.

7. Do you fully understand the limitations and impact of migration to your existing applications and customizations? (including that you cannot undo after the final Accept)

8. Do you have a detailed plan for the migration, such as, article type field mapping, apps (apex, visualforce, etc), end-to-end migration process, the time and efforts to spend on migration? Please see documentation to help develop this plan.

See also:

Lightning Knowledge Migration Tool FAQ
Lightning Knowledge Migration Tool

Support Video:
Lightning Knowledge Migration Tool