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.

Sharing updates with teammates via a feed on a case is enabled by Chatter feed tracking on the case. This feature attaches a collaborative feed to the case record, allowing agents to post updates, comments, and status changes, and to @mention teammates so everyone stays informed in real time. It also creates an ongoing history of activity for the case. The other options don’t provide a case-specific collaboration feed: the Knowledge sidebar is for quick access to articles, escalation rules determine when a case should be escalated, and email-to-case automation creates cases from emails and routes them.

Escalation rules automate what happens when an SLA milestone is breached. In Service Cloud, SLAs are tracked through entitlements and milestones, and escalation rules kick in when a milestone expires or is about to expire. They can automatically reassign the case to another user or queue, trigger notifications, and escalate to supervisors to ensure timely follow-up. This makes them the right automation for re-assigning cases after an SLA has expired, because you’re explicitly defining the ownership transfer as part of the breach response. The other options focus on user interface, collaboration, or activity tracking, not automatic reallocation based on SLA timing.

The main idea here is making self-service content easy to find for customers. Salesforce Knowledge stores installation guides, FAQs, and warranty information as articles, and the way to ensure customers actually see the most relevant ones is to surface recommended articles automatically. Implementing Recommended Articles helps present the right documents to customers based on context, so they can quickly access the guides and FAQs they need without extra searching. The other options don’t directly address how to surface or prioritize the content: a Customer Community provides the channel to access articles, but the specific feature that boosts findability and relevance is the Recommended Articles capability; Web-To-Case is for submitting cases, and Partner Control Community is intended for partners, not customers.