Migrating off Solutions is mostly an export-transform-import exercise plus a Knowledge taxonomy design phase.
- Inventory legacy Solutions and Categories
Query the Solution object and SolutionCategory. Document how many Solutions exist and how they tag against Categories.
- Design the Knowledge Data Category Groups
Map the single Solution Category tree to one or more Knowledge Data Category Groups. Take the migration as an opportunity to introduce multi-dimensional categorisation.
- Transform Solution content into Knowledge articles
For each Solution, create a Knowledge article with the equivalent content. Map the Solution Categories to Knowledge Data Categories.
- Migrate Case-Solution links
Cases linked to Solutions through CaseSolution should be re-linked to the corresponding Knowledge articles through CaseArticle.
- Retire the Solutions feature
Remove Solution tabs from page layouts, archive Solution data after migration verifies clean, and document the cutover in the org's release notes.
- Category for Solutions references in pre-2020 docs are legacy. Translate to Knowledge Data Category Groups for current implementations.
- Solution content does not migrate automatically. Build or buy a migration tool; manual is feasible only for small volumes.
- Case-Solution links need re-linking to Case-Article. Skipping the step leaves the historical resolution data orphaned.
- Self-Service Portal Solutions had different rendering than the Customer Portal. Both have been retired in favour of Experience Cloud.