Migrate from Tally: forms and responses

When you import with an API key, you can bring your existing responses across: check Bring … responses across too before you import. They keep their original dates, so they appear with the new ones in the responses table, the exports and the charts, and running the import again does not duplicate them. A JSON file contains the form only, so that path brings no responses.

Download the CSV from Tally anyway (Submissions, then download) before you close anything. It takes a minute and gives you a copy that does not depend on either product.

Open the Tally importer. There are two ways to hand over a form:

• An API key. In Tally, go to Settings, then API keys, and create one. Paste it into the importer and pick which forms to bring across. The key is used for the import only. It is never written to our database, never logged and never sent back to your browser. Tally includes API access on every plan, which is why this works on a free Tally account.
• A JSON file. If you would rather not share a key, export the form as JSON and upload the file. The form comes across the same way, without its responses.

The importer walks you through four steps: Choose how to import, Pick your forms, Check what comes across and Done. You can paste or upload a JSON file and see the preview without an account; you sign in to use an API key and to save the forms.

We do not read your public Tally pages to copy a form. Every imported form arrives as a draft. Nothing is published, collecting or shared until you press Publish in the top bar.

Before anything is created, the importer previews each form and counts what it found in four groups:

• Brought across. Came across as it was.
• Approximated. Came across as the nearest thing we have. The note says what changed.
• Do yourself. Something to set up again by hand, such as the form's password.
• Not transferred. Could not come across. The note names the block so you can find it.

Read it before you publish. If it lists something you cannot work around, send it to us. We treat import gaps as bugs.

Comes across: your questions and their order, titles and descriptions, required flags, choice options, pages, endings, hidden fields, calculated fields (numbers and text), conditional logic including "make this required" rules and jumps in both directions, close dates, response limits, redirects, the progress bar, theme colors, and your existing responses with their original dates. Your images are copied onto PulseFormCreator too, so they keep working when you close the old account.

Needs a manual check: a matrix where only some rows allowed several answers (every row is widened to match), date rules beyond a simple earliest and latest, images over 5 MB (or past the first thirty in one form), and any rule that loops back on itself. We show each question at most three times so the form always finishes.

Does not come across: a payment step, because PulseFormCreator does not take payments; form passwords, which you set again; and the device, country and timing behind your old responses, which Tally's API does not include. The import report names each of these against the block it came from.

The switching checklist at the end of this guide takes you through the rest in order, from the import report to your old links. Webhook payloads differ between the two products, so re-test anything that reads them. While you are in the Workflows tab, look at what else can run after each response, such as AI triage and replies from the response.

For a short form, starting again from a template can be quicker than importing. The contact us form template, a course sign-up form and a demo request form cover three common Tally forms, and a product feedback form a fourth. An email signup form and an online RSVP form cover two more.

Tally has several things PulseFormCreator does not: payments inside the form, forms in 50+ languages for respondents, connectors for AI assistants, imports from Typeform and from files, more integrations, Pro uploads with no size limit per file, a larger template library and a larger help center. If you depend on any of those, stay with Tally.

The full list is on the PulseFormCreator and Tally comparison, including every row where Tally is ahead.