What Every GetFeedback User Needs to Know Before December 31
On January 1, 2027, GetFeedback stops. Your surveys stop collecting. Your response data becomes inaccessible. This session is for teams who want to move without breaking what they have built.
Most teams replacing GetFeedback don't realise they're moving their customer data outside Salesforce until it's done. That gap has real consequences for GDPR, HIPAA, and every workflow that runs on that data today.
People who've actually run these migrations
A CX leader who has spent 20+ years inside the Salesforce ecosystem. She knows what teams have built on it, what they rely on, and what is genuinely at risk if a migration is handled without enough lead time.
Founder and CEO of SurveyVista, a 100% Salesforce-native customer intelligence & action platform. Has worked with enterprise CX teams on migrations from GetFeedback and understands where the process breaks down.
Three things every GetFeedback team needs to nail down now
Which surveys, automations, and Salesforce flows break the moment GetFeedback goes offline — and exactly what you need to audit before that date.
When feedback data moves to a non-native platform, it leaves the Salesforce security perimeter. For teams under GDPR or HIPAA, that is not a minor detail.
A framework for assessing any platform, so you compare on the criteria that matter to your architecture — not the ones a vendor puts in front of you.
One focused hour, start to finish
Everything is built around decisions you have to make before December 31.
