Salesforce is retiring GetFeedback, and Delighted (a separate Qualtrics product) already shut down on June 30. You don't have to rebuild your survey by hand before the deadline — paste in what you have, and AutoSurvey rebuilds it as a native survey, so every response lands as a Salesforce record instead of another cloud to sync.
Dec 31, 2026 isn't a soft deprecation notice — it's when GetFeedback stops working. Delighted (a separate Qualtrics product) already hit its own date, June 30, 2026. Whatever you're moving, it has to be done before your product's date.
Even connected to Salesforce, GetFeedback data lives in GetFeedback first, then syncs. AutoSurvey responses are Salesforce records from the moment they're submitted.
Most teams assume "migrate" means re-typing every question and choice into a new tool. There's a real importer so that isn't the only option.
How it works
Paste or connect what you have — a GetFeedback export or a connected account.
AutoSurvey rebuilds it natively — questions and choices recreated as a real AutoSurvey survey, not an embed or an iframe.
Responses are Salesforce records from the first submission — reportable next to the Case and Contact data they already relate to.
We're still verifying import accuracy against real GetFeedback exports as sample surveys come in In progress
Importing a GetFeedback survey, walked through
Demo coming soonThe importer moves your survey definition — the questions and answer choices. Skip logic and branching don't carry over in v1 and need to be rebuilt with AutoSurvey's Show If rules in the destination survey. It does not automatically pull over your historical responses. Those stay in GetFeedback (or wherever you've exported them) until you move them separately.
If you want that response history backfilled into Salesforce as records too, tell us in the founding-partner program — that's exactly the kind of migration work it exists for.
GetFeedback (the Salesforce/SurveyMonkey product) shuts down December 31, 2026. Delighted is a separate Qualtrics product that already sunset on June 30, 2026, with subscriptions no longer renewing since May 31, 2026. If you're coming from Delighted, the move is overdue rather than upcoming.
Your questions and answer choices. AutoSurvey rebuilds a native survey definition from what you had in GetFeedback — it isn't embedding or screen-scraping the old survey. Skip logic and branching don't carry over in v1; rebuild that with AutoSurvey's Show If rules in the destination survey.
The importer moves your survey definition, not your response history. Existing responses stay wherever you have them today — export them from GetFeedback separately, or ask about backfilling them into Salesforce through the founding-partner program.
There's a real GetFeedback importer, but fidelity is still being verified against a range of real GetFeedback exports. If your survey uses less common question types, check it after import before sending it live.
It helps, but the self-serve import doesn't require one. If you'd rather have someone walk through your specific survey with you, that's what the founding-partner program is for.
Yes — run the import in a sandbox first, the same way you'd test any other change before it touches production.
Tell us what you're running and we'll come back with a migration plan — the fastest, lowest-risk way over, including a sandbox trial run before anything touches production.
Erik reads these himself and usually replies within a day. Want to skip ahead? Grab a 30-minute migration call.
Rather have someone drive? White-glove migration help is part of the founding-partner program.