When migrating knowledge articles into Salesforce Knowledge, which statement is true?

• A. Article numbers change during the migration
• B. Approval Process history migrates to Lightning Knowledge
• C. Attachments and .html files in Classic Knowledge are moved to the Files Object
• D. Each article must be associated with an article type

Answer: (D)

In Salesforce Knowledge, an article exists within a defined structure called an article type. The article type acts like a template that specifies which fields the article has, how it’s laid out, and how it behaves. When migrating content into Lightning Knowledge, the system needs a clear target schema for each article, so every article must be associated with an article type. This association ensures there’s a defined set of fields (title, body, metadata, etc.) and the article can be stored, rendered, and searched correctly in the new environment. Without linking to an article type, the article has no schema to map to, and the migration can’t produce a valid Knowledge article.

Other details, such as whether article numbers change, how approval history is handled, or how attachments migrate to the Files object, can vary depending on the migration tool and process, but the essential requirement for a successful migration is the article-type association.