All docs

Import and migration

Bring earlier responses and forms over from a CSV or JSON file, or from a Typeform, Tally, Jotform or Formspree export. See what will and will not come across before anything is imported.

Updated . 4 min read.

You can move earlier work into Formspring in two steps: create the form from the other tool's export, then import its responses. Both steps start with a dry run that shows exactly what would happen. Nothing is written until you confirm.

Formspring reads the file you export. It does not connect to the other tool, and it never asks for your login or an API token for it. That means a migration is only as complete as the file you give it, and the dry run always tells you what is missing.

What each provider file means

Tool Form definition Responses Verification
Typeform Form definition JSON Responses JSON Shape checked
Tally Form definition JSON Submissions CSV Shape checked
Jotform Questions JSON Submissions CSV Shape checked
Formspree Form export JSON Submissions JSON or CSV Shape checked

Shape checked means the file layout was written from the tool's public documentation and tested on sample files. It has not been verified against a live export from that tool, so review the mapping on the dry run before you confirm. If a file is not recognised, Formspring does not guess: you map each column to a field by hand.

Create a form from an export

Open Forms > Import a form, upload the JSON file and read the report. Every question that could not be carried over is listed with a reason:

  • branching and conditional logic
  • payments and priced items
  • file upload questions
  • themes, thank-you pages and integrations

Treat the result as a starting point. It is never described as a full-fidelity copy.

Import responses

Open your form, choose Import responses and upload a CSV or JSON file (up to 5 MB and 10,000 rows, UTF-8).

  1. Map columns. Formspring suggests a field for each column. Choose a source id column so a re-import never duplicates, and an original date column so responses keep their real submission time.
  2. Dry run. You see how many rows are new, unchanged, changed in the file, repeated in the file or in need of attention, which columns are ignored, and which form fields cannot be filled by an import.
  3. Confirm. The import runs in the background in batches.

Imported responses are history, not new intake. They keep their original date and source id, do not count toward your monthly submission allowance (their size counts toward storage), and never send notifications, webhooks, automations or autoresponders. Answers to file upload, signature, payment, price and calculated fields are not imported.

Running the same file again

A rerun is safe. Every row has a stable fingerprint, so Formspring can tell what happened to it:

Outcome What it means What happens
New Not imported before Imported
Unchanged Imported before, same answers Nothing
Changed in the file Imported before, answers differ now Reported, left as imported
Edited in Formspring Changed in the file, but someone edited it here Reported, never overwritten
Repeated in the file The same source id appears twice Counted once
Failed The row could not be mapped Listed in the report

These outcomes add up to the number of rows in the file, and the result page says so. If they ever do not, it tells you not to rely on the import.

To update responses that changed in the file, turn on Update responses that changed in the file. Only responses nobody edited in Formspring are updated; their original date and source id stay.

Failed rows

Download the report to see each failed row and why. After you fix the form or the mapping, choose Retry failed rows. Only the failed rows run again, with the same source ids, so nothing already imported is duplicated. The kept rows are deleted after 14 days or when you remove the import.

Contacts

By default an import does not touch your contacts. You can choose to link imported responses to existing contacts, or to link and create the missing ones. Matching uses the exact email address only. Different addresses at the same company are never combined, existing contact details are never overwritten, and an imported address is never treated as verified.

Limits

  • Imports from a provider's live API are not offered. Export a file and import that.
  • Branching, payments, uploaded files and signatures are not carried over from any file.
  • The uploaded file is deleted as soon as the import finishes.

For developers

The same steps are available over the REST API (/forms/{form}/imports, abilities submissions:read and submissions:write, including resume, reconcile, retry of failed rows and rollback) and the MCP tools import_form_responses and get_form_import_run.