Research Guide
Qualtrics Migration Guide for Research Surveys
A migration is successful when the new instrument reproduces the study design, not merely the question text. Treat the QSF as a starting point, then audit logic, embedded data, recodes, randomization, redirects, accessibility, and exports before replacing a live link.
A practical workflow
- 1
Freeze and export the source
Save the QSF, a readable instrument copy, current response exports, and screenshots of logic or settings that may not travel.
- 2
Import structure
Bring questions, choices, and blocks into Domandata and review the importer report rather than assuming every setting mapped.
- 3
Rebuild design logic
Replace embedded-data and JavaScript workflows with explicit Flow conditions, variables, randomizers, and endings.
- 4
Validate variables and paths
Compare names, recodes, required behavior, hidden fields, treatment balance, and every respondent ending against the source.
- 5
Run parallel tests
Submit matched test cases to both instruments, compare exports, update panel links, and keep the original response archive separate.
Key design decisions
| Decision | Guidance |
|---|---|
| Import or rebuild? | Import conventional questions and blocks. Rebuild complex logic when a direct translation would preserve hidden complexity rather than make it auditable. |
| Merge old and new responses? | Keep historical Qualtrics responses as a frozen source dataset and harmonize them in analysis code; do not silently mix schemas. |
| When can the old link retire? | Only after matched-path tests, redirect checks, export comparisons, and stakeholder sign-off are complete. |
Common mistakes
- Assuming QSF import includes historical responses
- Forgetting embedded-data fields used in analysis
- Changing recodes while preserving the old variable name
- Replacing panel links before completion paths are tested