Download the current survey's definition — its questions, answer options, logic, and flow — as a file you can back up, version, or share. This is separate from the collected responses; to download those, see Exporting Survey Responses.
Export a survey (JSON / Word)#
Open the survey, then open the menu on the arrow beside Save in the toolbar (or use Download in the survey's row in the Surveys list):
- Export as JSON file: saves the survey definition as a
.jsonfile, handy for keeping a copy, version control, or reading the definition in other tools. - Export to Word: opens the Word export options
dialog, then saves a readable
.docxversion of the questionnaire to share or review.
The JSON file is a Qualtrics-style definition (with keys such as SurveyID,
Questions, Blocks and SurveyFlow). It is not the JSON the builder stores,
and it cannot be pasted back into a survey or uploaded as a new one. To change a
survey's JSON in place, admins can use Edit survey JSON in the AI Edit
menu. To
copy a survey as a file you can edit and upload again, admins use Download
JSON in that editor and Import from JSON when creating a survey; see
Survey JSON Editor.
Logic in the JSON reads exactly as it does in the builder. Each condition after
the first carries a "Conjuction" of "And" or "Or" (Qualtrics' own
spelling), the same AND or OR you picked between those rows in the logic editor.
Both export the survey definition (the questions), not the collected responses. In the builder, unsaved changes are saved first so the file matches what is on screen; if that save fails, nothing is exported and the error says what to fix. The Surveys list exports the last saved version.
Word export options#
Export to Word — from the menu beside Save in the builder, or from Download in the survey's row in the Surveys list — opens a dialog where you choose what the document includes. All options are checked by default; uncheck any you want left out:
- Logic rules — display, skip and termination logic, and the Survey Rules section. An end of survey shows its status (screenout, quota full or quality control), its message and any linked quota. Branches close with an "End of branch" line, descriptive text shows its own logic, and a hidden question shows "Hidden, treated as displayed".
- Randomization — choice and row randomization, section randomizers (a "Randomizer:" line naming the sections and how many are shown), priority and auto-code settings. A randomizer closes with an "End of randomizer" line, and a section that shuffles its questions shows a "Randomize questions" or "Custom question order" line under its heading.
- Survey flow — flow elements such as variable assignments, section loops (a "Loop:" line under the section heading saying what it repeats over), flow groups (a "Group:" line before the group and "End of group:" after it), a "Set Global Variables:" line before each flow step's assignments, the Create / Edit Global Variables and Display Global Variables blocks, plus global variable definitions.
- Quotas — quota definitions and their conditions, quota groups, cross-quota grids and panel redirect URLs.
- Images — pictures embedded in questions and answer options.
- Validation rules — answer validation such as required, ranges and totals, plus the answer format (number, email, phone, postal code), a custom required message, auto-answer when only one option is shown and skip when no options are shown.
- Recode values — recoded answer numbering; unchecked, answers are numbered sequentially (1, 2, 3…), which is useful for respondent-facing copies. Checked, an option also shows its export name, and a matrix row shows its recode when that differs from its printed number.
Interface (plugin) details and translated text are always included when the survey has them. So are page breaks between questions, the "One question per page" setting, answer settings (such as a matrix answer mode, a dropdown, a distribution's target total or file upload limits), and question and section descriptions. A question that uses a custom interface names it on its type line, for example "Standard Matrix (interface: sequential_select)".
Each option maps to a query parameter on GET /api/surveys/{id}/export/word
(rules, randomization, flow, quotas, images, validation,
recodes). A parameter defaults to true when omitted, so only unchecked
options are sent, as <name>=false.
Tips#
- Backups — Use Export JSON to keep a copy of a survey's definition before making big changes.
- Sharing — Export to Word produces a readable document for stakeholders who don't use the builder.
Related guides#
- Survey Builder Overview — building and editing surveys
- Survey JSON Editor: editing a survey's JSON in place (admins)
- Exporting Survey Responses — downloading collected responses
- Platform Feature List — full capability inventory
Was this page helpful?