Skip to content

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.

GetFeedbackSliick Forms
SurveyA form, identified by its external ID
QuestionA question on the form
NPS questionA Rating question, scale 0 to 10
CSAT or rating questionA Rating question, scale 1 to 5
Customer effort questionA Rating question, scale 1 to 7
Logic and branchingVisibility rules, on a question or a whole page
Multi-page surveysPages
Pushing answers to Salesforce fieldsA Salesforce mapping on each question, then processing
Merge fields and hidden contextHidden fields with default values
Response recordsResponses in the responses console
Draft and published surveyVersions: each response belongs to the version that was published when it was sent
Sharing by link or embedAn Experience Cloud page, or your own Sliick Edge address
Dashboards and NPS trendNot yet. Scored answers are in View results and the CSV export
  1. List your surveys. For each one, write down its questions, logic and Salesforce mappings, and note which ones are still getting responses.
  2. 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_score or ces_score, so the answers are easy to find in the CSV export.
  3. Rebuild your logic as visibility rules. For example, show a follow-up question or page when nps_score is at most 6.
  4. 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.
  5. Publish the form. Later edits do not change what someone already filling it in sees, or how their response is mapped.
  6. Swap your links. Replace GetFeedback links and embeds with your Experience Cloud page or your public address. In email campaigns, link to the form.
  7. Test end to end. Submit a test response, check it appears in the responses console, process it, and check the Salesforce records.
  8. Close GetFeedback. Once real responses are arriving in Sliick Forms, close the GetFeedback survey and export its past responses to CSV to keep.
  • 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.
StarterScored questionScaleFollow-up questions
NPS surveynps_score0 to 10Reason for a low score (6 or below), what they liked (9 or above)
CSAT surveycsat_score1 to 5Reason for a low score (2 or below), optional contact email
Customer effort surveyces_score1 to 7What 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.