GetFeedback Migration Guide

Use the migration cockpit when you need to move one survey or a full GetFeedback account into BuoyForms. GetFeedback is the most complete migration path in BuoyForms today because it has both survey-structure import and historical-response preservation workflows.

Keep each migrated form in draft until the checklist below passes.

Start a Project

Go to Forms and choose Migrate GetFeedback, or open the migration cockpit from the GetFeedback creation path.
Create a project with the customer name, source URL, and notes about exports or API access.
For API migrations, paste the customer-approved GetFeedback bearer token into the project API panel and run Test connection / preview surveys.
Select the surveys to import, confirm the owner user ID, then run Import selected surveys. BuoyForms creates draft forms with source survey metadata attached to the target organization and owner.
Add source survey inventory as CSV when the customer provides an export or when API access is not available. Use columns such as title, source_survey_id, source_url, owner, response_count, and notes.
Assign each survey to an operator and move its status from Inventory to Reviewing, Ready, Blocked, or Signed off as work progresses.

API tokens are used for the preview or import request and are not saved as a shared product credential in this flow.

What Carries Over

Source item	BuoyForms result	Notes
Survey name, title, and description	Form name and description	Available through the GetFeedback API path.
NPS, CSAT, CES, rating	Matching survey-score fields	Review labels and scoring after import.
Multiple choice and yes/no	Radio field	Picture choice also imports as radio.
Multiple-selection choice fields	Checkbox field	The importer uses GetFeedback multi-select flags when present.
Short answer, long answer, email, number, date, dropdown	Matching or closest BuoyForms field	Multiline short-answer fields become textarea fields.
Choices and scores	Option labels, values, source ids, and score metadata	Useful for parity review and historical response mapping.
Grid items	Subfield metadata	Review grid-style questions after import.
Thank-you-page button text	Submit or completion button label when available	Review final thank-you behavior manually.
Theme color and font hints	Theme recommendation inputs	Primary, background, text, and font values are used when the API exposes them.

URL-Only Fallback

Without a customer-approved API token, GetFeedback URL extraction is detection only. It can identify an embedded GetFeedback survey and capture an obvious survey id, but it does not import fields from the hosted page. Use the cockpit API flow or customer exports for real migrations.

Review Parity

Check the parity report before you publish. Confirm field count, required state, choices, NPS/CSAT/CES fields, unsupported items, and theme confidence. Review each warning. Mark it reviewed, accepted, or resolved before customer handoff.

Preserve Historical Responses

Upload or record the GetFeedback response export metadata in the cockpit. Confirm the response count and submitted-at column. BuoyForms supports two guarded historical paths:

API response import: enter source survey id and imported form id, run Dry run API responses, then run Write API responses only after a clean dry run.
CSV response import: run dry_run first, map each source column to a BuoyForms field, confirm the submitted-at column, then run write only after the dry run has no warnings.

Imported rows keep the original submitted timestamp and source response id.

For API imports, confirm the dry-run preview shows the expected source response ids, mapped value counts, and zero warnings before write mode. Written rows are historical records for the selected organization and owner, not live respondent submissions.

Salesforce Check

If the customer uses Salesforce, connect a sandbox org, map the migrated form, and run Test Mapping before publish. The publish gate blocks migrated forms until Salesforce verification, historical response preservation, warnings, confidence, and signoff are ready.

Handoff

Download the handoff packet from the cockpit after review. Send it with the parity report, warning decisions, historical export details, Salesforce test status, and publish blockers. Record customer signoff before replacing the GetFeedback link.