Moving or recovering a whole instance? Use backup and restore.
Keep databases, permission state, storage, secrets and configuration together. A PostgreSQL dump and
an S3 copy alone are not a complete recovery plan.
What carries over
A Formbricks file carries the survey’s content: questions, blocks, endings, welcome card, languages and translations, hidden fields, variables, logic and recall. For app surveys it also carries triggers, display settings and targeting filters, with the actions and contact attributes they use. The import finds those in the target workspace or creates them. It does not carry:- Responses, displays, contacts and tags. To bring responses along, use Migrating Survey Responses instead of this page.
- The survey ID. The imported survey gets a new one, so its link changes.
- Styling, survey settings, follow-ups and quotas.
- Images and videos. The file links to them on the source instance, so they load only while it is up and reachable.
Before you start
1
Match the versions
Run the same Formbricks version on the target as on the source, or a newer one. A file from a newer
version is refused until you update the target.
2
Check your access
On the source, you need to see the surveys; read-only access is enough. On the target, you need write
access to the workspace you import into.
3
Allow large uploads on the target
If a reverse proxy sits in front of the target, let request bodies of up to 16 MB through to
/api/internal/surveys/. See Self-hosting: proxy body
size.Step 1: Export from the source
For each survey, go to Surveys on the source instance, click ⋮ on the survey’s card, then Export → Formbricks file (.json). The file downloads as<survey name>.formbricks.json.
Step 2: Import into the target
1
Open the import dialog
On the target instance, open the workspace, go to Surveys, open the New Survey menu and choose
Import survey.
2
Drop the file
Drop the
.formbricks.json file into the dialog, or click to choose it.3
Read the report
The review shows the survey and the Import report: the actions and attributes the import will create,
and anything it removes. Click Download to keep a copy.
4
Save and continue
The survey is created as a draft named
<survey name> (imported) and opens in the editor. Nothing is
published.Step 3: Finish by hand
- Work through the import report from the top.
- Rename the survey if you don’t want the “(imported)” suffix, then publish it.
- Re-point everything that used the old survey ID. A link survey’s URL is
https://your-instance.com/s/<surveyId>, so every shared link, QR code, email campaign and embed snippet needs the new one. Old links keep working only while the source instance runs. - Rebuild what the file leaves out: styling, survey settings, follow-ups and quotas.
- Replace images and videos if the source instance is going away.
- Check app surveys. No-code actions the import created still match the source’s pages; update them if
the target app lives on other URLs. Rebuild any targeting filters the report says were removed before
you publish: a live app survey without targeting is shown to everyone. Then point
Formbricks.setup()at the target: bothworkspaceIdandappUrlstill name the source.
Moving changes later
Update only works in the workspace a survey lives in. The survey you imported has a new ID on the target, so a file exported again from the source doesn’t match it: importing that file creates another copy. To change a migrated survey, edit it on the target. Or export it from the target, edit the file, and import it back there with Update. See Update a survey from a file.Need help? Reach out in GitHub Discussions.