Moving from GetFeedback
GetFeedback Direct retires on 31 December 2026. This page shows what each GetFeedback feature becomes in Sliick Forms, and an order of work that keeps responses reaching Salesforce while you move.
What each feature becomes
Section titled “What each feature becomes”| GetFeedback | Sliick Forms |
|---|---|
| Survey | A form, identified by its external ID |
| Question | A question on the form |
| NPS question | A Rating question, scale 0 to 10 |
| CSAT or rating question | A Rating question, scale 1 to 5 |
| Customer effort question | A Rating question, scale 1 to 7 |
| Logic and branching | Visibility rules, on a question or a whole page |
| Multi-page surveys | Pages |
| Pushing answers to Salesforce fields | A Salesforce mapping on each question, then processing |
| Merge fields and hidden context | Hidden fields with default values |
| Response records | Responses in the responses console |
| Draft and published survey | Versions: each response belongs to the version that was published when it was sent |
| Sharing 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
Section titled “Migration steps”- List your surveys. For each one, write down its questions, logic and Salesforce mappings, and note which ones are still getting responses.
- Recreate each survey from a starter. In the builder, start from the NPS survey, CSAT survey or Customer effort survey starter. Each already has the scored question at the right scale, plus follow-up questions. Keep the scored question’s API name as it is:
nps_score,csat_scoreorces_score, so the answers are easy to find in the CSV export. - Rebuild your logic as visibility rules. For example, show a follow-up question or page when
nps_scoreis at most 6. - Set up the Salesforce mappings. Choose each question’s target object and field. Tick Use for matching on the question that identifies the person, usually email, so a response updates their record instead of creating a duplicate. Matching needs every ticked question to agree, so:
- If the form collects a real identifier, such as a customer number, match on that alone. Adding more questions only narrows the match: a customer whose email changed would be duplicated.
- Make every matching question required, because each one must be answered.
- Publish the form. Later edits do not change what someone already filling it in sees, or how their response is mapped.
- Swap your links. Replace GetFeedback links and embeds with your Experience Cloud page or your public address. In email campaigns, link to the form.
- Test end to end. Submit a test response, check it appears in the responses console, process it, and check the Salesforce records.
- Close GetFeedback. Once real responses are arriving in Sliick Forms, close the GetFeedback survey and export its past responses to CSV to keep.
What does not come across
Section titled “What does not come across”- No questions inside the email itself. You share a link or embed, and the scored question appears on the form, not in the email.
- No import of past responses. Keep your GetFeedback CSV exports. Response history in Sliick Forms starts from the day you switch.
- No NPS score summary yet. Scored answers are saved, shown per question in View results, and included in the CSV export. A summary score and trends over time are planned for a dedicated analytics page. See Results and funnels.
The survey starters
Section titled “The survey starters”| Starter | Scored question | Scale | Follow-up questions |
|---|---|---|---|
| NPS survey | nps_score | 0 to 10 | Reason for a low score (6 or below), what they liked (9 or above) |
| CSAT survey | csat_score | 1 to 5 | Reason for a low score (2 or below), optional contact email |
| Customer effort survey | ces_score | 1 to 7 | What made it hard (3 or below) |
The starters follow the standard NPS scoring: 9 to 10 are promoters, 7 to 8 are passives, and 0 to 6 are detractors. To work out your NPS from the CSV export, take the percentage of promoters and subtract the percentage of detractors.