Is GetFeedback shutting down? What Salesforce teams need to know

• GetFeedback Direct, the Salesforce-connected survey product, closes December 31, 2026.
• SurveyMonkey owns GetFeedback Direct. In the closure announcement, they recommend their own Enterprise platform as a replacement, and estimate the transition at around 90 days.
• The Salesforce integration isn't included on standard SurveyMonkey plans, and Enterprise pricing is quote-only.
• Recreating the surveys is the quick part. Your Salesforce Flows, field mappings, suppression rules, follow-up automations, and reports all need to be audited, rebuilt where necessary, and tested.
• If you're considering Simplesat, we'll handle the migration with you, including survey setup, historical feedback import, Salesforce integration, mappings, and testing.
• Start early enough to run both systems in parallel before GetFeedback Direct shuts down.
• The naming is confusing. The product that will shut down is GetFeedback Direct. SurveyMonkey also has a website feedback tool called GetFeedback, formerly GetFeedback Digital. That one isn't closing.

Which GetFeedback is shutting down?

Two products currently carry the GetFeedback name, and one of them now has a new self-serve tier. Only GetFeedback Direct is closing.

GetFeedback Direct sends surveys out to your customers. It covers NPS, CSAT, and CES, both one-off transactional feedback and ongoing relationship programs.

The Salesforce integration is why many teams chose GetFeedback Direct in the first place. Surveys fire from your own Salesforce automation, carry record data with them, and the responses write back to the objects and fields that your reports and follow-up workflows depend on.

This is the product that will close on December 31, 2026.

GetFeedback is the website feedback product that used to be called GetFeedback Digital. According to SurveyMonkey's FAQ: "With GetFeedback Direct sunsetting on December 31, 2026, we changed the name of GetFeedback Digital to GetFeedback. Nothing else about your product, access, or setup is changing." If GetFeedback Digital is part of your current subscription, you can renew that portion beyond December 31.

The new self-serve version is a simpler tier of that same website feedback product, announced July 22, 2026, and aimed at new customers. SurveyMonkey has told GetFeedback Digital customers it's "a different product tier and not a replacement for what you have today."

Still confused? Look at where the survey shows up. GetFeedback Direct sends surveys to people, by email or link, often triggered from a Salesforce record. GetFeedback collects feedback from visitors already on your site, through buttons and pop-ups. If you're sending surveys out, the deadline applies to you. If you're collecting on-site, you're fine.

The key facts

What's closing GetFeedback Direct, the Salesforce-connected survey productClosing dateDecember 31, 2026What continuesGetFeedback, the website feedback product formerly known as GetFeedback DigitalRecommended actionExport your data and document your Salesforce setup before choosing a replacementYour data after December 31SurveyMonkey hasn't said how long response data will be kept. Export before then.

What breaks in your Salesforce org on December 31

Your survey triggers need a replacement. Case-closed CSAT, post-onboarding NPS, lifecycle surveys, and any other process connected to GetFeedback Direct must be moved before shutdown if you want feedback collection to continue.

Your mappings need a new destination. Ratings, comments, timestamps, sentiment, and other response data will stop reaching your existing Salesforce fields and objects unless the replacement is configured to send it there.

Your follow-up workflows stop firing. A detractor response might create a case, notify an account owner, update an account health field, send an email, post to Slack, or start another Salesforce Flow. Those dependencies are easy to miss because they sit downstream from the survey itself.

Anything that exists only in GetFeedback Direct needs protecting. SurveyMonkey has confirmed the shutdown date but hasn't committed to keeping your response data past it. Export your historical responses, comments, survey definitions, and any metadata you may want later while you still have access.

Don't uninstall the GetFeedback Salesforce package until you've checked where your historical data lives. If you use managed mapping, your responses are stored in objects that belong to the package itself rather than in your own Salesforce objects. Uninstalling a managed package removes its components and package data, so export and verify what you need first.

If you use custom mapping instead, responses already live in your own Salesforce standard or custom objects. Those records are separate from the package data, but the mappings that populated them still need to be replaced.

Every one of these has to be found before December 31.

What to document before you touch anything

Plenty of teams configured GetFeedback Direct once, years ago, and no longer remember the specifics. Before you sit through a single demo, get the current setup written down. You'll need it to brief vendors, and you'll need it again when you rebuild.

For every survey, write down:

• The trigger: which object, which event, and which Flow or workflow rule calls it
• The Salesforce object that responses map to
• The fields that receive rating, comment, sentiment, timestamp, or other values
• Any sync conditions or filters
• The merge fields appended to survey URLs, so responses tie back to the originating record
• What happens after a negative or positive response: cases, tasks, emails, Slack alerts, or other actions
• Account, contact, or case fields updated after a response
• Reports and dashboards that depend on GetFeedback Direct fields or objects
• Any other systems receiving GetFeedback Direct data
• Custom Salesforce code, Apex, Visualforce, or components connected to the survey process

One thing that catches teams out is the rule that stops the same customer being surveyed twice in a month. Many teams built that themselves, with a date field and a check on the Flow entry criteria. It works well, but it's invisible until it's gone. Write yours down, and ask every vendor whether their tool enforces that rule for you or you're building it again.

Note who owns each survey, who reads the reports, and who understands the Salesforce automation behind them.

The Salesforce loop you're rebuilding

Strip away the survey itself and this is what GetFeedback Direct is really doing for you:

A case closes. A Flow sends a survey with identifiers for the case and customer. The customer responds. The response is connected to the appropriate contact, account, or case. The rating then updates the fields, reports, and workflows your team already uses.

Every piece of that has to exist in the replacement, and vendors differ most in the last few steps. Plenty of tools can send a CSAT email triggered by Salesforce. Fewer can put the result somewhere your current dashboards and workflows can use without creating another project for your Salesforce team.

Take a relationship NPS program that's been running for three years. The survey is one question. But Salesforce is deciding who gets it, when they get it, who should be excluded, which account and contact the response belongs to, what happens when someone becomes a detractor, and which reports receive the result.

None of that is visible when you're comparing survey builders.

Should you move to SurveyMonkey Enterprise?

For some teams, yes.

SurveyMonkey Enterprise is a capable platform, and its Salesforce integration is more substantial than some comparisons online suggest. It supports a Salesforce managed package, custom object mappings, survey triggers, Salesforce Flows, reports, and dashboards.

So the real question isn't whether it connects to Salesforce. It's how much work the transition creates, who owns that work, and whether it's the right-sized platform for your budget and for what you're trying to do. A few things to know before you decide.

SurveyMonkey estimates the transition at around 90 days. Customers are assigned a Technical Solutions Manager, and implementation may include Salesforce integration training, survey recreation, and account setup.

Migration support isn't the same everywhere. US-based customers are offered data migration services. Everywhere else, the offer is a manual rebuild of top-priority surveys, which puts the work back on your team. Confirm which applies to you before you commit to a timeline.

Pricing isn't published. SurveyMonkey Enterprise is quote-only, so you won't be able to compare total cost until you're some way into a sales conversation. Ask for the Salesforce integration to be priced as a separate line item.

Check what's scoped and what's left to your admin. Some work happens inside your Salesforce org whichever vendor you pick. What varies is how much of it the vendor plans, configures, and tests with you. SurveyMonkey's setup instructions point you to your Salesforce admin for the email template and Flow.

There's also the question of fit. SurveyMonkey Enterprise supports research programs, advanced survey analysis, panels, administration, and hundreds of integrations. For organizations running feedback and research across multiple departments, that breadth can make sense.

But if what you need is feedback landing back on the right record when a case closes, and someone acting on it, you may be buying a much bigger platform than the problem needs. That's a call worth making deliberately rather than defaulting into.

How to evaluate a replacement

We fielded a lot of these evaluations when Qualtrics closed Delighted. Our advice for a smooth migration:

Ask who owns the implementation. Don't settle for "we support Salesforce." Ask who recreates your surveys, field mappings, triggers, suppression logic, historical data, follow-up workflows, and reporting connections. If the answer is your Salesforce admin, include those hours in the cost of the migration.

Show vendors your real setup. Don't spend the demo rebuilding a sample CSAT survey. Show them one of your existing GetFeedback Direct workflows and ask how they would reproduce it. A useful answer should be specific enough that your Salesforce admin can challenge it.

Test response integrity, not just whether the survey sends. If you're running case-based CSAT, submit the same survey twice and reopen an old survey link. Make sure every response stays tied to the correct case and that an old link can't quietly create a duplicate or misattribute feedback. Those problems don't cause an obvious outage. They corrupt the metric you're reporting.

Check that a historical import keeps its original dates. Three years of CSAT is no use if it all lands looking like it was collected this month. Ask whether imported responses keep their original submission dates and timestamps.

Ask how a detractor's response reaches someone who can fix it. GetFeedback Direct does that through Salesforce workflows and case creation. You want the specific path, not a general answer about alerts.

Add up the total cost. Connector fees, seats, professional services, and your team's implementation time all count.

Ask who owns the vendor and what their roadmap is. You're rebuilding all of this because a product you relied on got retired. That can happen again.

Two more that teams leave too late.

Test on real devices before you cut over. Skip logic, mobile rendering, and email embed behavior all shift between platforms, and a browser preview can hide that from you.

Export your GetFeedback Direct data before you choose a vendor. Teams treat the export as part of the migration project, so it waits on a decision that takes months. But the data you pull out is the same whichever vendor you pick. Do it now rather than in December.

There's one upside. You're rebuilding anyway, so this is the moment to finally add the follow-up automation or reporting view you never got around to building.

Where Simplesat fits

We make Simplesat, so you should evaluate us with the same questions.

Simplesat is customer feedback software for support and CX teams, used by more than 1,000 brands. We support CSAT, CES, NPS, 5-star, and custom surveys. We're independent, founded in 2016, SOC 2 Type II certified, and GDPR and CCPA compliant.

On Salesforce, Simplesat can:

• Trigger surveys from Salesforce events and Flows
• Deliver surveys inside live Salesforce conversations
• Sync responses to a custom Salesforce object related to contacts, accounts, and cases
• Write ratings, sentiment, comments, and other feedback back to Salesforce fields
• Pull case and customer context into each response
• Kick off follow-up in Salesforce based on survey responses or sentiment
• Build survey audiences from Salesforce contacts and reports
• Let you report on feedback in Salesforce or Simplesat
• Import historical ratings, comments, and response dates so your reporting history comes with you

Salesforce starts on our Pro plan at $249 per month, or $229 per month billed annually. The price is published. You don't need a separate quote for the Salesforce connector.

But the bigger difference for a GetFeedback customer is the migration.

What we'll handle for you

We don't want you spending the next few months reverse-engineering GetFeedback Direct and rebuilding it alone.

We'll work through your existing setup with you and own the migration plan.

That includes:

• Recreating your surveys in Simplesat
• Importing your historical ratings and comments
• Setting up the Simplesat Salesforce integration
• Configuring response mappings and sync
• Recreating supported survey triggers and follow-up behavior
• Connecting responses back to the right contacts, accounts, and cases
• Testing the new setup against real Salesforce records
• Running Simplesat alongside GetFeedback Direct before cutover
• Helping verify that the data your Salesforce reports and dashboards depend on is still arriving correctly
• Planning the final switch so you're not discovering problems after GetFeedback Direct is already gone

If something requires a change that can only be made inside your Salesforce org, or involves custom code, we'll identify it clearly and work through it with your Salesforce admin.

Your migration timeline

Work backward from December 31. Your real deadline is earlier because you want the new system tested before GetFeedback Direct disappears.

Now: Document every survey, trigger, mapping, suppression rule, follow-up workflow, and reporting dependency. Export all historical response data. Identify who owns the surveys and who understands the Salesforce automation behind them.

September: Demo two or three options. Spend the demo on your actual Salesforce configuration rather than the survey builder. Ask each vendor who owns the rebuild and whether they can reproduce your current setup.

October: Build in parallel. Recreate your highest-priority surveys first, usually post-case CSAT and relationship NPS. Configure mappings, import historical data, and test with real Salesforce records.

November: Verify every trigger, mapping, and downstream workflow. Make sure detractors reach the right people. Confirm reports and dashboards still get the fields they need. Show survey owners and report readers the new setup.

December: Deactivate GetFeedback Direct only when the replacement is proven, then watch the first few days closely.

Start now and you have room to test. Start in December and you're cutting over blind during the holidays.

Migrating from GetFeedback Direct?

Before you choose a replacement, show us what you've already built.

We'll review your surveys, Salesforce triggers, mappings, follow-up logic, and historical data, and show you what the move to Simplesat would involve.

If you choose us, we'll handle the migration at no additional cost.

Your GetFeedback contract shouldn't decide when you move. If you're still under contract, we'll cover Simplesat for the remainder of your term so you're not paying for both. If you're on a monthly plan, your first month is on us.

Email sales@simplesat.io, or see how Simplesat works with Salesforce.

FAQs

Is GetFeedback shutting down?

Yes, GetFeedback Direct is shutting down at the end of 2026. But GetFeedback (previously GetFeedback Digital) isn't affected. If you send surveys out to customers by email or link, you're using GetFeedback Direct. If you collect feedback only from visitors on your website, you're using GetFeedback.

When does GetFeedback Direct close?

December 31, 2026.

Why is GetFeedback Direct being retired?

SurveyMonkey acquired GetFeedback in 2019 and is consolidating their CX offering around SurveyMonkey Enterprise. They say they've brought key GetFeedback Direct capabilities into that platform.

Will my surveys and data automatically move to SurveyMonkey Enterprise?

Not automatically. Data migration services are offered to US-based customers, and a manual rebuild of top-priority surveys everywhere else. SurveyMonkey estimates the overall transition at around 90 days.

Does SurveyMonkey Enterprise integrate with Salesforce?

Yes. SurveyMonkey Enterprise has a Salesforce integration that supports a managed package, custom mappings, survey automation, Flows, and Salesforce reporting. Access depends on your plan and seat type rather than being included by default, so confirm what your contract covers.

Do I need to rebuild my Salesforce setup when I leave GetFeedback Direct?

Assume nothing transfers. Anything that touched GetFeedback Direct, from the Flow that fired the survey to the report that consumed the result, needs to be rebuilt and tested in the new tool.

Can Simplesat import my historical GetFeedback Direct responses?

Yes. Simplesat can import historical ratings, comments, dates, customer details, ticket IDs, and other supported data from CSV. More complex historical data can also be handled through the API.

Will Simplesat rebuild my Salesforce integration for me?

Yes. We'll own the migration with you. We'll recreate the Simplesat surveys, configure the Salesforce integration and mappings, import historical feedback, set up supported triggers and follow-up behavior, and test the new workflow with you. Anything that can only be changed inside your own org, we'll work through with your Salesforce admin.

Can we run GetFeedback Direct and Simplesat at the same time?

Yes, and that's how we'd recommend doing it. Run both systems in parallel, confirm that triggers fire and data lands where expected, then switch GetFeedback Direct off when you're comfortable with the new setup.

Will we have to pay for GetFeedback and Simplesat at the same time?

Not under this migration offer. We'll cover Simplesat for the remainder of your existing GetFeedback term. If you're paying GetFeedback monthly, your first month of Simplesat is on us.

How much work will our Salesforce admin have to do?

Some. Installing the package, creating custom objects, and building Flows all happen inside your org, so those need your admin. We handle everything on the Simplesat side — the setup, migration, mappings, historical data, and testing.

What happens to my GetFeedback Direct response history after December 31?

SurveyMonkey hasn't committed to keeping your response data past December 31. Export anything you may want to retain before then, especially data that isn't stored elsewhere.