Important: Classic Feedback will be retired on August 1, 2026. If you haven’t already, contact your Pendo representative to update your contract to Pendo Listen. After your contract is updated, you must request a data migration if you want to keep your existing classic Feedback data. We recommend completing your migration by May 1, 2026 to ensure a smooth transition. For more information, see Migrate from classic Feedback to Pendo Listen.
Migrating from classic Feedback to Pendo Listen involves making decisions about the following data:
- Feature requests. Choose whether you want to migrate feature requests in classic Feedback as either feedback items or ideas in Pendo. This choice has implications for how votes appear in Listen.
- Statuses. Choose how you want to map statuses on your feature requests in classic Feedback to feedback items or ideas in Pendo Listen.
You communicate these decisions when you request a migration through Pendo Support. For more information, see Migrate from classic Feedback to Pendo Listen.
You also need to reconfigure any integrations that you currently have for any Listen-specific versions in Pendo Listen, such as Jira or Salesforce. For more information, see the Integrations section in this article and Migrated functionality in Listen.
Feedback requests
You can migrate your feedback requests in classic Feedback as either feedback items or ideas in Pendo Listen.
- If you migrate your feature requests as feedback items in Listen, votes are migrated on the backend, but aren't visible in Pendo yet. For more information, see Migrated functionality in Listen.
- If you migrate your feature requests as ideas in Listen, feature request votes appear as votes on the equivalent ideas in Listen.
In most cases, we recommend migrating your feature requests in classic Feedback as feedback items in Listen, rather than ideas. This is because:
- Ideas in Listen represent proposed solutions and product directions that are defined by your organization, whereas individual pieces of feedback represent the problem space as defined by your end users, consisting of varied, granular input.
- Feedback items in Listen are the raw data that you can extract themes from and then link to fewer but more formulated ideas. Linked feedback items are treated as "votes" (evidence) for these ideas, rather than representing the ideas themselves.
- Ideas should be high quality because they are curated and managed by you, the Pendo user. You can then present particular ideas in an ideas portal or an ideas test based on your product plans.
For the above reasons, there are typically far more feedback items than ideas, with several feedback items linked to an idea. For more information, see Gather evidence for ideas.
Statuses
Before migrating to Listen, you must decide how to map each status in classic Feedback to a corresponding status for feedback items or ideas in Listen.
In classic Feedback, feature requests have six default statuses. In Listen, feedback items have three default statuses, and ideas have six default statuses. The default statuses are:
- For classic Feedback: Not Reviewed, Awaiting Feedback, Planned, Building, Released, and Declined.
- For feedback items in Listen: New, Under review, and Reviewed.
- For ideas in Listen: New, Under consideration, In discovery, In development, Now available, and Archived.
You can customize and create new statuses in Listen to allow direct mapping from classic Feedback statuses, or you can map multiple statuses in classic Feedback to a single status in Listen.
However, we recommend you consider how your workflow will change when migrating to Listen, and aligning your statuses to match this new workflow. It’s not recommended to manually review all items in Listen, so your statuses should reflect this. See Prepare your organization for migrating to Listen for more detail.
You can also choose to exclude feedback with certain statuses from the migration by leaving those statuses unmapped. For example, you might decide not to migrate any feature requests with a status of Released. If you decide not to migrate a status, let us know when you request a migration so that we know this is intentional and not an oversight.
Integrations
Any integrations that you've set up with classic Feedback aren't preserved when you migrate to Pendo Listen. You must set up integrations separately for Pendo Listen. For information about the data created through these integrations and how you can distinguish this data from data created through integrations with classic Feedback, see Migrated functionality in Listen.