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.
This article summarizes the data functionality that is and isn't migrated from classic Feedback to Pendo Listen. This article also covers the differences in integrations data between classic Feedback and Listen. With Listen, integrations are set up separately and feedback data is imported. Therefore, there's a distinction between integrations data from classic Feedback and Listen.
Migrated
When you migrate feature requests to Listen, the following information is preserved whether the requests become feedback items or ideas:
- User information. Information about who the user is and when they submitted the feature request is moved to the feedback item or idea in Pendo Listen.
- Attachments. PNG and JPG files attached to feature requests are migrated to feedback items or ideas in Pendo Listen.
- Tags. Tags given to feature requests appear as labels associated with your feedback items or ideas in Pendo Listen.
- Product Areas. Product Areas assigned to feature requests are assigned to your feedback items or ideas in Pendo Listen.
- The content supplied on the feedback form. The custom questions you include in the form and responses to these questions provided by your visitors. Informational text blocks aren't included. This is to avoid migrated content having repetitive, unnecessary information.
- Comments. Comments on feature requests will appear in the Comments tab for the feedback item that they belong to. New visitor comments aren't supported in Listen, but visitor comments from classic Feedback will be migrated and visible in Listen. For more information about the commenting functionality, see Collaborate in Listen. If the comment is from a visitor that was removed from the subscription before you migrated to Listen, the comment shows without visitor details.
-
Votes on feature requests.
- If you migrate feature requests from classic Feedback as ideas in Listen, they appear in the Evidence tab of the individual ideas in Listen. For more information about this tab, see Create and manage ideas.
- If you migrate feature requests from classic Feedback as feedback items in Listen, we add a Votes tab to individual feedback items in Listen. Listen doesn't add votes to individual feedback items as standard, and so this tab only includes information about votes added from classic Feedback. Any votes attached to a feedback item that is then linked to an idea in Listen are also counted in the idea.
Not migrated
The following information isn't migrated to Listen:
- Feedback roadmaps. Listen has its own roadmap functionality that allows you to choose between different roadmap templates, create and nest features within initiatives, and add ideas to your roadmap. For more information, see Roadmaps in Listen.
- Feedback portal. Rather than showing every feedback item to your visitors, Listen allows you to curate ideas based on this feedback. You can then share and validate these ideas through an ideas portal that you can customize to suit your business vision and strategy. For more information, see Engage users through an ideas portal.
- Request priority. Feedback is migrated with a default assigned importance level of "nice to have". If feedback was snoozed in classic Feedback, it's instead assigned an importance level of "not interested".
- Status. Statuses aren’t migrated from classic Feedback to Listen. Instead, you map each status to a new status that's been created in Listen ahead of migration. For more information, see Prepare your data for migration to Listen.
- Status updates through email. Updates sent to subscribers in classic Feedback won't be visible in Listen.
- Opportunities. Listen doesn't support Salesforce opportunities, so data associated with Opportunities in classic Feedback won't be migrated.
- Feedback 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 more information, see Integrations in this article.
Ideas portal
After migration, visitors won't see a historical list of their original feedback submissions in the My Priorities section of the Listen ideas portal. This is because Listen doesn't distinguish between private and public feedback in the way classic Feedback does.
What visitors see in My Priorities depends on how their feature requests were migrated:
- Migrated as feedback items and linked to ideas. Visitors see the linked ideas in My Priorities, provided those ideas are visible in the portal. Visitors appear to have voted on those ideas.
- Migrated directly as ideas. Visitors see those ideas in My Priorities under the Evidence tab on the idea.
This applies to feedback that visitors submitted themselves and to feedback that they voted on but was submitted by other visitors.
Integrations
The data from some of your integrations with classic Feedback is preserved, but not the integrations themselves. We've built the following equivalent integrations, which you must set up separately for Pendo Listen.
Jira
The Jira integration with Listen allows you to link Jira tickets to ideas in Listen. Links between Jira tickets and feature requests in classic Feedback aren’t migrated over to Listen. For more information about this integration, see Jira integration with Pendo Listen.
Salesforce
The Salesforce integration with Listen allows you to submit feedback items to Listen from Salesforce on behalf of visitors. This is similar to the functionality of the Salesforce integration with classic Feedback, which allowed you to submit feature requests to classic Feedback from Salesforce on behalf of accounts. The visitor who made the request was added to the request as a vote rather than the creator. The creators of these feature requests were displayed as Salesforce in classic Feedback (rather than the visitor who relayed the request to the Salesforce user).
After you migrate to Listen, the creator of any feature requests that were created through the Salesforce integration with classic Feedback is displayed as System user (instead of Salesforce) in Listen. For more information about this integration, see Salesforce integration with Pendo Listen.
Zendesk
The Zendesk integration with Listen allows you to submit feedback items to Listen from Zendesk on behalf of visitors. This is similar to the functionality of the Zendesk integration with classic Feedback, which allowed you to submit feature requests to classic Feedback from Zendesk on behalf of visitors, and to associate the Zendesk ticket and submitter to the request in classic Feedback. The visitor who made the request was added to the request as a vote rather than the creator. The creator of these feature requests were displayed as Zendesk in classic Feedback (rather than the visitors who relayed the request to the Zendesk users).
After you migrate to Listen, the creator of any feature requests that were created through the Zendesk integration with classic Feedback is displayed as System user (instead of Zendesk) in Listen. If the visitor for any requests created through the Zendesk integration with classic Feedback exists in Pendo when you migrate to Listen, their votes are added to the feedback item.