GetFeedback retires December 31, 2026. Move your surveys to native Salesforce →
Insights · Switching · Salesforce admins

How to replace GetFeedback before December 31, 2026: a checklist for Salesforce teams

GetFeedback Direct shuts down on December 31, 2026. Here is a week-by-week plan to move your NPS, CSAT and CES surveys without losing history or follow-up.

SalesHub · October 19, 2026 · 7 min read

GetFeedback Direct is scheduled to shut down on December 31, 2026. Its owner is pointing customers to SurveyMonkey Enterprise. If your team sends surveys from Salesforce today, you have about ten weeks to pick a replacement, rebuild your surveys and switch over without a gap in feedback. Delighted, another popular NPS tool, already shut down on June 30, 2026 and deleted customer data after its end date. Don't leave exporting to the last week.

This checklist is written for Salesforce admins and CX leads who own the move. It works whichever tool you choose.

Your switch timeline to December 31, 20261Oct 31Inventory donefirst export taken2Nov 14Tool choseninstalled in sandbox3Nov 26Top 2 surveysrebuilt and tested4Dec 8First surveylive in production5Dec 15All surveys liveold tool read-only6Dec 22Final exportold tool retired!Dec 31GetFeedbackDirect sunsets
A working timeline: six milestones that finish a week before GetFeedback Direct's December 31, 2026 sunset.

1. Inventory every survey you run (this week)

Before you compare tools, write down what you actually have. For each survey, capture:

FieldExample
Survey name and typeSupport CSAT (CSAT)
Salesforce triggerCase: Status = Closed
ChannelEmail, one hour after close
Questions and scales"How satisfied are you…" 1–5, plus a comment box
Where answers are writtenCustom object linked to Case and Contact
What happens on a low scoreTask to the queue lead
Reports and dashboards that use it"CSAT by queue" dashboard
OwnerSupport operations manager

Most teams find a few surveys nobody uses. Retire those now rather than rebuild them.

2. Export your data while you still have access

Export survey definitions, response history and any contact-level data you're allowed to keep. Check your contract for the exact access end date and export options, and keep the files somewhere your security team approves. Decide now whether old responses must live in Salesforce, so trends continue, or can stay archived as files.

3. Decide what the replacement must do

Use these criteria rather than a feature checklist:

Bolt-on survey tool vs. native appBOLT-ONData lives in two placesSalesforcerecordsVendor cloudresponsesconnector + field mapping✕ New vendor security review✕ Sync errors and duplicates✕ Low scores noticed lateNATIVE (NPS SURVEY CX OS)Everything on the recordInside your Salesforce orgEventsends surveyAnsweron recordLow scoreopens caseDashboardCX360✓ Data never leaves Salesforce✓ No connector to maintain✓ Every detractor gets an owner
Where the data lives decides most of the work: a connector to maintain, or a loop that stays inside Salesforce.

4. Rebuild in a sandbox (weeks 2–5)

  1. Install the new tool in a sandbox.
  2. Rebuild your highest-volume survey first, usually case-close CSAT or relationship NPS.
  3. Recreate the trigger on the same Salesforce event, and map answers to the same fields so existing reports keep working.
  4. Set the follow-up rules: detractors (0–6) open a case with an owner, passives (7–8) get a nurture, promoters (9–10) get a review or referral ask.
  5. Test with internal users, then a small group of real customers.

5. Run both in parallel, then cut over (weeks 6–9)

Go live in production for one survey and watch response rates and follow-up for a week. Then move the rest. Keep the old tool read-only until your final export is done.

A working timeline to December 31

ByMilestone
Oct 31Survey inventory done; first export taken
Nov 14Replacement chosen; installed in a sandbox
Nov 26Top two surveys rebuilt and tested
Dec 8First survey live in production
Dec 15All surveys live; old tool read-only
Dec 22Final export archived; old tool retired

Where NPS Survey CX OS fits

NPS Survey CX OS by SalesHub is a Salesforce-native NPS, CSAT and CES app on AppExchange. Surveys are sent from Salesforce events, answers are written to your records, and low scores open an owned case automatically. It has 70+ ready-made forms and industry blueprints to rebuild from, and it's priced per org: CX Lite $3,500, CX Pro $8,500 and CX360 Insights from $16,000 a year. Every edition has a 7-day free trial. Rated 5.0 on AppExchange.

Moving off GetFeedback or Delighted?

Keep your surveys, follow-up and dashboards inside Salesforce. Start the 7-day free trial, or book a 30-minute switch call.

Start the free trial →See the switch plan →

Sources: Salesforce Ben, "GetFeedback and Delighted to be retired in 2026" (January 30, 2026); Delighted sunset FAQ. Confirm your own dates with your vendor. GetFeedback, SurveyMonkey and Delighted are trademarks of their respective owners; SalesHub is not affiliated with them.