Legacy Survey Import
Legacy Survey Import helps organizations move surveys from the previous Q-Fi platform into Quali-Fi. Connect with a migration token, preview what will transfer, select surveys, and track per-survey progress while Quali-Fi preserves question and response ID mappings where possible.
Note
Legacy import is an organization-level feature. If you do not see Import Legacy Surveys under Activities → Surveys, contact your Quali-Fi administrator or account team.
Before you start
- Obtain a legacy migration token from your Quali-Fi onboarding or support contact.
- Plan which surveys you need in Quali-Fi first, import runs per survey, not as an all-or-nothing bulk job.
- After import, review logic, quotas, and embedded data in the Survey Builder before going live.
Connect to your legacy account
Go to Activities → Surveys.
Open Import Legacy Surveys (or navigate to the legacy import page from the surveys area).
Paste your migration token and connect.
Quali-Fi validates the token and loads the list of available legacy surveys.
Your connection session is stored locally so you can return to the import list without re-entering the token until it expires.
Preview and select surveys
For each legacy survey you can:
- View title, status, and last-updated metadata
- Run a preview to see how questions, pages, and logic will map
- Select one or more surveys for import
Use preview on complex instruments, especially those with branching, quotas, or custom variables, before committing to a full import run.
Run the import
Select the surveys to migrate.
Start the import run.
Monitor per-survey status: queued, running, completed, or failed. Reload the browser if you need to. In-progress imports stay on the list after a refresh.
When a survey completes, open it in the Survey Builder to verify structure and test a live response path.
Completed imports create new Quali-Fi surveys with persistent ID mapping so historical references and downstream tooling can align with the legacy source where supported.
Exit variables (exitvar)
Recent import improvements include support for legacy exit variables (exitvar), the variables that drove screening, termination, and quota-full outcomes on the previous platform.
When exit variables are present on a legacy survey, the importer maps them into Quali-Fi's equivalent logic and outcome handling where possible. Still verify:
- Terminate and quota-full paths in Survey Logic and End Survey Screens
- Mixed conditions that combined questions with legacy sample variables (for example panel codes such as
PANEL), these map to Embedded Data sources; open the condition editor after import and confirm each rule still reads correctly - Any reporting or export filters that referenced legacy exit codes
- Embedded data fields that carried exit status into downstream systems
Legacy sample variables used in skip / terminate / quota logic generally become embedded-data conditions. Prefer a live path check after import rather than assuming every compound rule transferred without review.
Grid textbox → Side by Side
Legacy GridTextBox (free-text grid) questions import as Quali-Fi Side by Side with Text attribute columns:
- Legacy statements / rows become Side by Side items
- Legacy column headers become attributes with column type Text
- Legacy min/max options map to Min filled per row / Max filled per row in Side by Side Settings
That last point matters: respondents must fill the required number of cells per row, not every attribute by default. After import, open the question in the Survey Builder and confirm the fill limits match the original instrument.
Import translations
When you start an import run, Import translations is on by default. It brings published question, help, and choice labels for extra languages from the legacy survey.
- Leave it checked to import multilingual content with the survey.
- Uncheck it to import the default language only.
After a run completes, the progress summary can show how many translations were imported and how many were skipped. Spot-check the survey Translations page for languages that matter to your deploy.
Some legacy field overlays are not imported yet (for example certain side-by-side item/column overlays, dropdown/multislider/rotation overlays, and matrix row overlays where Quali-Fi maps column/option labels only). Re-enter those strings in Quali-Fi if the original instrument depended on them.
For bulk CSV/Excel translation workflows on an existing Quali-Fi survey, see Importing Survey Translations.
After import checklist
- Question types and labels render correctly in preview
- Logic rules and skip paths behave as expected
- Exit / End Survey Screen rules that used sample variables still evaluate correctly
- Quotas and embedded data fields match your deployment plan
- GridTextBox imports look right as Side by Side (including min/max filled per row)
- Extra-language translations look correct when Import translations was enabled (or re-import / re-apply if you imported default language only)
- Distribution links updated to Quali-Fi URLs before inviting respondents
Troubleshooting
| Issue | What to try |
|---|---|
| Token rejected | Confirm the token has not expired; request a fresh token from support |
| Survey stuck in running | Refresh the import list, in-progress runs still appear after a reload; contact support if status does not change |
| Logic differs from legacy | Compare preview output; some legacy constructs may need manual adjustment in the Survey Builder |
| Missing question type | Check release notes, import coverage expands over time; unsupported types may need rebuild |
| Translations missing | Confirm Import translations was checked; review skipped counts in the run summary; fill gaps on Translations or via translation import |
Related
- Creating Surveys, build or adjust imported surveys
- Side by Side, GridTextBox import target
- Survey Logic & Branching, fix or extend branching after import
- Embedded Data, map legacy sample variables
- Importing Survey Translations, CSV/Excel translation import for Quali-Fi surveys