Skip to content

Form responses from an export file

Bring past form responses into Formspring

Export your responses from the form tool you are leaving, map the columns to the fields of a Formspring form, check the counts with a dry run, then import. Running the same file again adds nothing twice.

Forms are included from Free.

See what does not carry over

What carries over

  • Answers to the fields you map to, as stored responses in the form's inbox
  • The original submission date, when the file has a date column you choose
  • A source id per row, so a repeated row is recognised
  • The layouts of Typeform, Tally, Jotform and Formspree export files are recognised and mapped for you to review

What does not carry over

  • Answers to file upload, signature, payment, price and calculated fields
  • The form design, branching logic, payments and thank-you pages: rebuild them, or start from a form created from the export
  • Notifications, webhooks and integrations: imported responses are history and trigger none of them
  • Anything the export file does not contain

What you need

  • Export the responses from the old tool yourself, as a CSV or JSON file. Formspring never signs in to it.
  • A Formspring form whose fields match the answers you want to keep.
  • A Formspring workspace. Forms are included from Free.

How it maps

How it maps
In your file or old toolIn FormspringNote
A column or keyA form fieldSuggested by name; you confirm each one
A unique id columnSource idChoose one so a rerun never duplicates a response
A date columnOriginal dateThe response keeps the time it was really submitted
Typeform, Tally, Jotform or Formspree exportPre-filled mappingThe layout was written from public documentation and has not been checked against a live export, so review the mapping

Addresses and domains

  • Imported responses do not change any address. Your form link or endpoint is a separate switch: see the form endpoint guide.
  • Imported responses do not count toward the monthly submission allowance; their size counts toward storage.

Check before you commit

Run the dry run first. It shows how many rows are new, unchanged, repeated or in need of attention, which columns are ignored and which fields an import cannot fill. Nothing is written until you confirm.

File size
Up to 5 MB
Rows per file
Up to 10,000; split larger exports

Steps

  1. Create or open the Formspring form that should hold the responses.
  2. Export the responses from the old tool as CSV or JSON.
  3. In the form choose Import responses, upload the file and map the columns.
  4. Read the dry run, fix the mapping if needed, then confirm. The import runs in the background.
  5. Download the report for any failed row, correct it and retry only the failed rows.

Reconcile the result

  1. The outcomes on the result page add up to the number of rows in your file. If they do not, do not rely on the import.
  2. Open three imported responses and compare every answer with the old tool.
  3. Check that an imported response kept its original date.
  4. Run the same file again: nothing should be created twice.

What the dry run reports

A dry run counts every row of your file before anything is stored.

Sample data

New, unchanged, changed in the file, repeated in the file and failed rows add up to the number of rows in the file. The numbers depend on your file; none are promised here.

Switching over

Import, check, then switch the live form link or endpoint. Keep the old account read-only for a billing cycle in case you need to look something up.

Other guides