Category, Solutions
Category for Solutions is the legacy Salesforce Solutions feature taxonomy that organised the Solution object's records into a hierarchical category tree, letting service agents browse and search for canned solutions when resolving Cases.
Definition
Category for Solutions is the legacy Salesforce Solutions feature taxonomy that organised the Solution object's records into a hierarchical category tree, letting service agents browse and search for canned solutions when resolving Cases. The Solutions feature predates Salesforce Knowledge and shipped with Salesforce Service Cloud's earliest releases. Each Solution record represented a documented answer to a recurring customer issue; Solution Categories organised the solutions for faster discovery. Like Answers and Ideas before it, the Solutions feature has been deprecated in favour of Salesforce Knowledge, with most orgs migrating between 2015 and 2020.
Category for Solutions matters mainly as a historical reference. The Solution object remains queryable in older orgs and partner blogs from the 2008 to 2015 era reference it extensively. Modern Salesforce Service Cloud documentation steers customers to Lightning Knowledge for canned-answer content, with Knowledge's Data Category Groups serving the same organisational role that Solution Categories once did. New orgs do not get the Solutions UI as a primary feature; the schema persists for backward compatibility but Salesforce no longer recommends building service operations around it. Reading any pre-2020 Salesforce documentation that mentions Category for Solutions should translate the concept to Data Category Groups for Knowledge.
Category for Solutions and the migration to Knowledge
The Solution object
Solution is a standard object with Title, Solution Note (the content), Status, Public flag, and category assignments through SolutionCategory. Solutions are linked to Cases through the CaseSolution junction. The object remains queryable; the UI is mostly retired.
How Solution Categories organised content
Solution Categories formed a single hierarchical tree per org. Admins built the tree in Setup; authors tagged solutions against categories. Service agents browsing for solutions navigated the tree to find candidates relevant to a Case.
Public Solutions and self-service
Solutions flagged Public could be exposed on a Self-Service Portal (the predecessor to Experience Cloud) where customers searched for answers without contacting support. The Self-Service Portal is also retired; the parallel feature today is Experience Cloud Help Center with Knowledge articles.
Why Salesforce moved to Knowledge
Knowledge offered richer content (rich text, attachments, multiple article types, version history), better search, multi-channel delivery, and modern Lightning UI. Solutions remained simple but limited. Salesforce gradually deprecated Solutions in favour of Knowledge, with Lightning Knowledge as the current recommended product.
Migration from Solutions to Knowledge
Most migrations export Solutions, transform the content into Knowledge article shape, and import as Knowledge articles tagged against Data Categories. Custom or partner-supplied migration tools handle the conversion; Salesforce provides migration documentation rather than a turnkey tool.
Solution Categories versus Data Category Groups
Both are hierarchical taxonomies. Data Category Groups in Knowledge are richer: multiple parallel groups, per-profile visibility, multi-dimensional categorisation. Solution Categories were a single tree with no per-profile visibility. Migration upgrades the model in the process.
Surviving Solution data
Orgs that never migrated still have Solution records and Solution Categories queryable. The data lives until explicitly archived. Modern Salesforce documentation no longer covers the Solutions feature; partner blogs from the 2010s remain the main reference.
When the term still appears today
Category for Solutions appears in pre-2020 partner blogs, certification material, and migration documentation. Current Salesforce documentation references Knowledge Data Category Groups exclusively. Translate the legacy term when reading older content.
How to migrate from Category for Solutions to Knowledge
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.
Trust & references
Cross-checked against the following references.
- Solutions OverviewSalesforce Help
- Knowledge OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Category, Solutions.
- Migrate to Lightning KnowledgeSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What are Solution Categories used for?
Q2. Is Solutions a current or legacy feature?
Q3. What should you do with Solution Categories during a Knowledge migration?
Discussion
Loading discussion…