Moving from GetFeedback

GetFeedback Direct retires on 31 December 2026. This page maps each GetFeedback concept to its Sliick Forms equivalent and gives an order of work that keeps your Salesforce data flowing while you move.

What each concept becomes

GetFeedback	Sliick Forms
Survey	A form, keyed by its external ID
Question	A field on the form
NPS question	A Rating field, scale 0 to 10
CSAT or rating question	A Rating field, scale 1 to 5
Customer effort question	A Rating field, scale 1 to 7
Logic and branching	Visibility rules, per question or per page
Multi-page surveys	Pages
Salesforce push on mapped fields	A Salesforce mapping per field, plus processing
Merge fields and hidden context	Hidden fields with default values
Response records	Staged responses in the responses console
Draft versus published survey	Versions: responses pin to the published version
Web distribution by link or embed	An Experience Cloud page, or your own Sliick Edge address
Dashboards and NPS trend	Not yet. Scored answers are in View results and the CSV export

Migration steps

1. Inventory your surveys. Export each survey’s questions, logic and Salesforce mappings, and note which surveys are still receiving responses.
2. Recreate each survey from a starter. In the builder, start from the NPS survey, CSAT survey or Customer effort survey starter. They already include the scored field at the right scale and the conditional follow-ups. Keep the scored field’s API name, nps_score, csat_score or ces_score: the NPS calculation keys off nps_score.
3. Rebuild logic as visibility rules. Branch logic becomes rules such as nps_score at most 6 on a follow-up question or on a whole page.
4. Re-point the Salesforce mappings. Set each question’s target object and field, and tick Use for matching on the field that identified the record, usually email, so a response updates instead of duplicating. Two consequences are worth planning around, because matching requires every ticked field to agree:
   • If the form collects a real identifier, such as a customer number, match on that alone. Adding more fields can only narrow the match, so a customer whose email address changed would be duplicated.
   • Every field in the key has to be answered, so make match fields required.
5. Publish the form. Publishing snapshots the survey, so later edits never change what an in-flight respondent sees or how their response maps.
6. Swap distribution. Replace GetFeedback links and embeds with your Experience Cloud page or your public address. For email campaigns, link to the form.
7. Verify the loop. Submit a test response, confirm it appears in the responses console, process it, and check the target records.
8. Freeze GetFeedback. Once live traffic is landing in Sliick Forms, close the GetFeedback survey and export its historical responses to CSV for your archive.

What does not come across

• No question inside the email itself. Distribution is by link or embed, and the scored question renders on the form rather than in the email body.
• No historical response import. Keep your GetFeedback CSV exports: response history starts fresh at the cutover.
• No NPS roll-up yet. Scored answers are captured, visible per question in View results, and in the CSV export. The roll-up and period-over-period trends are waiting on a dedicated analytics page. See Results and funnels.

The survey starters

Starter	Scored field	Scale	Follow-ups
NPS survey	nps_score	0 to 10	Detractor reason at 6 or below, promoter highlight at 9 or above
CSAT survey	csat_score	1 to 5	Low-score reason at 2 or below, opt-in contact email
Customer effort survey	ces_score	1 to 7	Friction description at 3 or below

The scoring convention the starters follow counts nps_score answers as promoters at 9 to 10, passives at 7 to 8 and detractors at 0 to 6, and computes NPS as the promoter percentage minus the detractor percentage across the most recent 2000 responses.