As part of migrating articles to Lightning Knowledge, which factor should a consultant consider?

• A. Convert any articles containing HTML into plain text before importing because HTML is NOT supported in any article field types.
• B. Prepare a single .csv file that can be used to migrate all article types at once and include with a .properties file in a .zip for Import.
• C. Verify that each article type has field-level security on all fields set to read-only prior to import, in order to prevent any loss of data.
• D. Ensure that each existing article type has a corresponding Salesforce knowledge article record type that matches its structure and content.

Answer: (D)

When migrating articles to Lightning Knowledge, the key step is to map each existing article type to a corresponding Salesforce Knowledge article record type that matches its structure and content. Lightning Knowledge uses knowledge article types to define what fields exist, how the article is organized, and how it behaves across channels. If every source article type has a matching knowledge article record type, the import can place each field into the correct place, preserve the content and metadata, and maintain consistent how the articles are displayed and managed after import. Without this alignment, fields may not map correctly, layouts can be broken, and data integrity is at risk.

Other considerations described in the options aren’t as central to a successful migration. HTML formatting isn’t universally prohibited in all article fields, so converting everything to plain text isn’t a default requirement. Import processes typically require understanding that different article types may need separate imports or mappings rather than one universal CSV, and pre-import field-level security isn’t the primary factor for preserving data during the migration; proper mapping and creation of matching record types is what safeguards structure and content.