> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/polls/import.md).

# Migrate a Survey to Another Account

Zigpoll lets you move a survey between accounts by exporting it to a `.json` file and importing that file into a different account. This is useful when you want to reuse a proven survey across multiple brands or clients, hand a template off to a colleague, or copy a survey from a staging account into your production account.

Migration happens in two steps:

1. **Export** the survey from the source account to a JSON file.
2. **Import** that file into the destination account.

{% hint style="info" %}
**This migrates the survey itself — not its responses.** The export file contains the survey definition (slides, questions, answers, logic, settings, translations, and any email templates it uses). Collected responses, analytics, and sentiment data are **not** included. If you also need to move historical response data, see [Importing data](/polls/importing-data.md).
{% endhint %}

### Before you start

* You need access to **both** accounts — the one you are exporting from and the one you are importing into. Imports always go into the account you are currently viewing, so you must be able to switch to the destination account.
* Integrations (Shopify, Stripe, Square, Klaviyo, etc.) are connected **per account**. If your survey relies on an integration, make sure that integration is connected on the destination account too. See [Troubleshooting](#troubleshooting) below.

## Step 1 — Export the survey from the source account

1. Open the survey you want to migrate.
2. Open the survey's options menu and choose **Export**.
3. Your browser downloads a JSON file named after the survey, for example `Post-Purchase Survey_2026-6-22.json`.

The exported file is a portable survey definition. It includes:

* The survey **title** and all of its **slides** (questions and answer options)
* **Branching and skip logic**, display rules, and behavior settings
* **Design, targeting, and delivery settings**
* **Languages and translations**
* Any **account email templates** the survey references (follow-up emails and send-email actions are bundled into the file automatically)

It does **not** include responses, vote counts, sentiment, timestamps, or anything tied to the original survey's identity.

## Step 2 — Switch to the destination account

Use the account switcher to move into the account you want to import the survey into. The import always targets the account you are currently in, which is also why you can only ever import into an account you have access to.

## Step 3 — Import the survey

1. Go to your **Surveys** list in the destination account.
2. Click **Import Survey**.
3. Drag your exported `.json` file into the upload area, or click to select it.
4. Click **Upload**.

Zigpoll recreates the survey in the destination account, including its slides, logic, settings, and translations. Any email templates bundled in the export are added to the destination account as well.

{% hint style="info" %}
**Imported surveys start hidden.** A freshly imported survey is created in an inactive (hidden) state so it never goes live before you've reviewed it. You'll turn it on in the next step.
{% endhint %}

## Step 4 — Review and activate

Because the survey lands hidden, take a moment to finish setup before it goes live:

1. **Review the settings** — confirm targeting, delivery, and design look right in the new account.
2. **Reconnect anything account-specific** — re-check integration actions, notification recipients, and webhooks so they point at the destination account's connections.
3. **Activate it** — turn on visibility / set the survey active when you're ready. See [Delivery Settings](/polls/visibility-settings.md).

## What migrates and what doesn't

| Migrates                                           | Does **not** migrate                                            |
| -------------------------------------------------- | --------------------------------------------------------------- |
| Survey title and slides                            | Responses and vote counts                                       |
| Questions and answer options                       | Analytics and sentiment data                                    |
| Branching / skip logic and display rules           | The original survey's ID and history                            |
| Design, targeting, delivery, and behavior settings | Live/active status (imports start hidden)                       |
| Languages and translations                         | Integration connections (must exist on the destination account) |
| Referenced email templates                         |                                                                 |

## Troubleshooting

**"Invalid survey format uploaded."** The file must be a JSON file produced by Zigpoll's **Export** option. Re-export from the source survey and upload that file. Editing the JSON by hand can break the format.

**My responses didn't come over.** That's expected — migration moves the survey definition only. To bring historical response data into the new survey, use the CSV-based [Importing data](/polls/importing-data.md) flow.

**My integration actions or webhooks aren't working.** Integrations are connected per account. Connect the relevant integration on the destination account, then confirm the survey's actions and webhooks reference it.

{% hint style="info" %}
Need help moving a survey or its data between accounts? [Contact us](https://www.zigpoll.com/contact) and we'll be glad to help.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zigpoll.com/polls/import.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.