Moving from Tally to PulseFormCreator

When you import with an API key, the importer brings your existing responses across with their original dates, so they appear with the new ones in the responses table, the exports and the charts. 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.

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.

Every import produces a report in three parts:

• Mapped. Came across unchanged.
• Approximated. Came across as the nearest block we have. The report says what changed.
• Not supported. Could not come across. The report 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 colours, 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: matrix questions that allowed several answers per row, 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 does not provide. The import report names each of these against the block it came from.

1. Read the import report. Check every item marked "needs review".
2. Check the rules that came across. They sit as cards under the questions they run after. Open Flow in the top bar to follow the paths. See logic and scoring.
3. Reconnect your integrations. Webhook payloads differ between the two products, so re-test anything downstream. See integrations.
4. Turn notifications back on. Emails to you are free. Respondent confirmation emails need Pro.
5. Replace the embed snippet on your site with the new one from the Share tab. See sharing and embedding.
6. Submit a test response, then delete it.
7. Update your links, buttons and QR codes, and close the Tally form with a message pointing at the new one.

For a short form, starting again from a template can be quicker than importing. The contact form template, the registration form template and the lead generation form template cover three common Tally forms.

Tally has several things PulseFormCreator does not: payments inside the form, custom domains, team workspaces, a public API, 50+ interface languages, connectors for AI assistants, a larger template library and a larger help centre. If you depend on any of those, stay with Tally.

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