What changes occur when migrating from Classic to Lightning Experience (LEX) knowledge?

When migrating from Classic to Lightning Experience (LEX) knowledge, Classic knowledge article types are indeed mapped to record types in the new environment. This is an important change because it allows organizations to maintain their existing article structure while adapting to the different functionality and features available in LEX.

Mapping Classic article types to record types ensures that the categories and formats of the articles are preserved during the transition. In LEX, record types provide flexibility in defining and managing the articles, allowing different page layouts and processes based on the specific record type used. This capability is crucial for organizations that want to continue using tailored article formats suited to their different types of content or audiences.

The other options do not correctly reflect the changes that occur during this migration. For instance, Classic article types are not deleted entirely; they are transformed into record types. Additionally, while CRUD (Create, Read, Update, Delete) permissions become more robust in LEX, they are not inherently functional per article type prior to migration. Moreover, not all fields from Classic are automatically retained without changes, as some may not have equivalents in LEX or may require adjustments to fit the new model. Therefore, the mapping to record types is a key feature that supports a smooth transition while preserving existing knowledge article structures