GetFeedback Sunset 2026: The Salesforce Admin Migration Checklist

What Every Salesforce Admin Should Do Before Migrating Off GetFeedback

GetFeedback Direct shuts down on December 31, 2026, and if you are the Salesforce Admin behind that integration, you already know the surveys are not the hard part. The Flows, the outbound messages, the response mappings, the permissions layer, the historical data your CS team depends on for every QBR. That is what makes this migration real. Most teams that approach it as a simple tool swap underestimate the timeline and end up rebuilding under deadline pressure. This is the checklist for not being that team.

1. Map Every Salesforce Dependency Before You Evaluate a Single Vendor

The surveys are the fastest thing to recreate. Everything your org built around them is where the real migration timeline lives.

Start with distribution automation. If your org triggers survey sends through Salesforce Flows and outbound messages tied to events like case closure or opportunity stage changes, each of those automations breaks the moment the GetFeedback endpoint goes dark. Document every Flow, every outbound message, and every email alert tied to GetFeedback.

Then catalog your response mappings. If your org uses GetFeedback Managed Mappings, survey responses live in three managed package objects installed in your org: Survey, Response, and Answer. If those objects appear in reports, page layouts, dashboards, or downstream Flows, you need a plan for what replaces them. When a managed package is uninstalled from Salesforce, all component data is deleted from the org, so export that data before you remove anything. If your team built Custom Mappings instead, response data was pushed directly into standard and custom objects like Contact, Account, and Case. Those field mappings need to be documented before you can rebuild them on a new platform.

Finally, account for merge fields. GetFeedback used merge fields to associate Salesforce data like Case ID or Contact ID with survey responses. Those values were appended to the survey URL as query parameters so each response could be linked back to the originating record. Every survey link containing those merge fields needs to be rebuilt for whatever platform comes next, and every email template, Visualforce page, or Flow that constructs those links needs to be updated at the same time.

2. Export Your Historical Data Now

SurveyMonkey has not publicly disclosed its data retention policy for GetFeedback Direct after the December 31 shutdown. What is confirmed is that you lose access to the platform on that date. The pattern from comparable SaaS shutdowns, including Delighted where all customer data was confirmed deleted at closure, is that data does not survive long after a platform goes dark.

Export everything now: raw response data, NPS and CSAT trends, survey configuration details, and any records used in QBRs, board reporting, or compliance documentation. If your organization operates in a regulated industry where historical feedback records are required for audit purposes, this export is urgent. Do not wait until Q4.

3. Evaluate the Security Architecture of Every Replacement Option

The default migration path is SurveyMonkey Enterprise, which is not built natively on Salesforce. That means your feedback data would leave the Salesforce trust boundary and connect back through OAuth tokens and API integrations. Before you accept that architecture, consider what happened in 2025.

In August 2025, the Salesloft Drift breach exposed more than 700 organizations through compromised OAuth tokens tied to a single third-party Salesforce integration. Attackers did not breach Salesforce itself. They exploited the connector sitting beside it and exfiltrated sensitive data including Cases, Accounts, Users, and Opportunities from organizations including Cloudflare, Palo Alto Networks, and Zscaler. The FBI issued a formal cybersecurity advisory in September 2025 warning that attackers are actively targeting Salesforce environments through third-party integrations.

Salesforce has been phasing out Connected Apps since its Summer ’25 release and enforced the restriction across all existing orgs in Spring ’26, disabling the creation of new Connected Apps by default and pushing organizations toward External Client Apps, a framework with tighter security controls. IBM’s 2025 Cost of a Data Breach Report found that supply chain compromises cost an average of $4.91 million per incident and took the longest to resolve at 267 days. The security architecture of your next feedback platform is the most consequential decision in the entire migration.

4. Communicate the Risk to Leadership Before the Decision Is Made for You

This migration affects more than the admin team. Customer Success leaders lose NPS and CSAT signals during any gap in collection. Executives lose the dashboards they use for board reporting. Compliance teams need clarity on where historical data will live and whether the new platform meets regulatory requirements.

Frame the conversation around three things: data continuity, security risk, and timeline. Historical feedback data may not survive the shutdown, and any collection gap during migration means lost churn signals during active renewal cycles. The default migration path moves data outside the Salesforce trust boundary, which carries documented risk. And most migrations take 60 to 90 days when planned properly, so teams that start in Q2 or Q3 finish 2026 with a stronger program. Teams that wait until Q4 rebuild under deadline pressure while renewals are running.

The strongest internal argument is that neither vendor-recommended replacement is Salesforce-native, which means feedback data continues living outside your org. Present this as an architecture decision, not a tool swap.

5. Ask These Questions Before You Commit to Any Vendor

These are the questions that separate native architecture from integration architecture. Most vendor demos skip them. Ask each one before you sign.

• Where does survey response data live the moment a respondent submits? Inside your Salesforce org as native objects, or on an external server that syncs back?
  The answer determines your compliance exposure, your security surface, and whether your existing Salesforce governance applies automatically.
• Does the platform respect your existing profiles, permission sets, and sharing rules without requiring a separate security configuration?
  A native application inherits your org’s security model. A non-native application requires parallel permission structures and doubles governance overhead.
• What happens to your data if the relationship with the vendor ends?
  You are migrating off GetFeedback precisely because a vendor sunset is forcing your hand. Get a clear answer to this question before you sign.
• Does the platform require OAuth tokens, Connected Apps, or external API endpoints?
  Given Salesforce’s Spring ’26 restrictions on Connected App creation, this question carries more weight than it did a year ago.
• Can the platform trigger surveys from any standard or custom Salesforce object without external middleware or outbound messages to a third-party endpoint?
  If the answer requires middleware, outbound messages, or third-party endpoints, the platform is not truly operating within your Salesforce architecture.

6. Consider a Salesforce-Native Platform That Eliminates These Risks

A 100% Salesforce-native survey platform stores every response as a native Salesforce object inside your org. No external server, no OAuth token, no API connector, and no middleware. Your existing reporting, automation, permission sets, and sharing rules work without parallel configuration. When Salesforce tightens its security model, a native application is already compliant by default.

This is the architecture SurveyVista is built on. Hire Heroes USA, a nonprofit serving U.S. military veterans, migrated from GetFeedback to SurveyVista and gained stronger automation, tighter Salesforce integration, and workflows the previous platform could not support. Their migration is documented in full and worth watching. 

We have guided dozens of organizations through this exact transition. Our team will walk through your current setup, map your dependencies, and give you an honest picture of what migration looks like for your specific org. No pressure, just clarity. Schedule a call and let us show you what native looks like.

About SurveyVista

SurveyVista is the only 100% Salesforce-native Intelligence and Action Platform that captures insights across every customer touchpoint, transforming fragmented feedback into unified intelligence to reduce churn, grow revenue, and improve productivity — inside Salesforce. Leveraging AI to embed insights directly into Salesforce workflows, SurveyVista drives automated actions that deliver measurable results.

Frequently Asked Questions

Q: Is GetFeedback shutting down in 2026?

A: Yes. SurveyMonkey has confirmed that GetFeedback Direct will shut down permanently on December 31, 2026. GetFeedback Digital, the website and app feedback product, will continue operating, but the core Salesforce survey platform is ending. SurveyMonkey has not publicly disclosed what happens to customer data after shutdown, so organizations should export all historical response data now rather than risk losing it. Schedule a call to start your migration plan.

Q: Is SurveyMonkey Enterprise a Salesforce-native application?

A: No. SurveyMonkey Enterprise integrates with Salesforce through external API connectors, but survey response data is stored on SurveyMonkey’s external servers and synced back to Salesforce. This means feedback data leaves the Salesforce trust boundary, requires ongoing integration maintenance, and does not inherit your existing Salesforce profiles, permission sets, or sharing rules. A 100% Salesforce-native platform like SurveyVista stores all response data directly inside your org as native Salesforce objects.

Q: What is the best Salesforce-native survey tool to replace GetFeedback?

A: The strongest replacement for Salesforce teams that need feedback data to stay inside their org is a 100% native platform that stores responses as Salesforce objects, respects existing permission sets and sharing rules, and requires no external middleware. SurveyVista is the highest-rated native survey platform on the AppExchange with a 4.96 star rating across 222 reviews. Organizations like Hire Heroes USA have already completed the GetFeedback to SurveyVista migration with documented results.

Q: What happens to my GetFeedback data after the December 2026 shutdown?

A: SurveyMonkey has not publicly detailed its data retention policy for GetFeedback Direct after the December 31 shutdown. You will lose access to the platform on that date. For comparison, Delighted confirmed that all customer data would be deleted at its June 30 shutdown. The responsible approach is to export all raw response data, NPS and CSAT trends, benchmark records, and survey configurations now rather than waiting to find out. Schedule a call if you need help planning your data migration.

Q: How long does it take to migrate from GetFeedback to a new platform?

A: Most organizations complete the migration in 60 to 90 days when they begin with a proper dependency audit. SurveyVista has accomplished this in 30-60 days for existing customers. The survey rebuilds happen quickly. The real timeline comes from remapping Salesforce Flows and outbound messages, validating field mappings, reconnecting downstream reports and dashboards, and running both platforms in parallel for two to four weeks before cutting over. Starting in Q2 or Q3 of 2026 gives your team enough runway to migrate without deadline pressure. Schedule a call to scope your specific timeline.

Q: Why does Salesforce-native architecture matter more now for survey tools?

A: In August 2025, the Salesloft Drift breach compromised more than 700 organizations through stolen OAuth tokens tied to a third-party Salesforce integration. Salesforce has been phasing out Connected Apps since Summer ’25 and enforced the restriction across all orgs in Spring ’26, disabling new Connected App creation by default. A 100% native application has no external API surface, no OAuth tokens to compromise, and no middleware between your feedback data and your org. The platform direction is clear: native is the security standard.

Q: What questions should I ask survey vendors before replacing GetFeedback?

A: Ask where response data lives at the moment of submission, whether the platform respects your existing Salesforce permission sets and sharing rules without separate configuration, what happens to your data if the vendor relationship ends, and whether the platform requires OAuth tokens or external API endpoints to function. These questions separate native architecture from integration architecture and directly impact your org’s security, compliance, and ongoing maintenance overhead. Schedule a call and our team can walk through the evaluation framework with you.