Most orgs migrated off legacy Ideas years ago. Remaining migrations involve preserving historical idea data and choosing a modern equivalent.
- Inventory legacy Idea data
Query Idea, IdeaComment, Vote. Document idea count, categories, and submission history. Decide whether to migrate the data or preserve it in place.
- Choose a modern replacement
Experience Cloud Q&A with Topics, Chatter Questions, custom Idea object, or a third-party integration (Pendo, ProductBoard). Each fits different use cases.
- Rebuild category structure
Whatever the replacement, recreate the Category structure as Topics, custom picklists, or third-party tags. The taxonomy was useful; do not lose it in migration.
- Migrate historical ideas
Map legacy Idea records to the new surface. The conversion is one-time; plan it before retiring the legacy Ideas zones.
- Retire the legacy Idea Zone
Once data is migrated and the replacement surface is live, retire the legacy Idea Zone. Keep the Idea object data queryable for audit but stop accepting new submissions there.
- Category for Ideas references in pre-2020 docs are historical. Treat them as such.
- The legacy Idea object still queries but the UI is largely retired. Plan replacement before relying on it.
- Categories preserved poorly during migration to flat Topic models. Plan the taxonomy carefully.
- Voting and comment data has no direct equivalent on Chatter Questions. Custom-object replacements preserve the model better.