Moving from another tool
Moving from Tally to Pulseware
Most of a Tally form comes across on its own. This guide covers the order to do things in, what the importer cannot map, and the five minutes of cleaning up at the end.
Last updated
Before you start: download your responses anyway
The importer now brings your existing responses across with their original dates, so they sit alongside the new ones in the responses table, the exports and the charts. Re-running the import never duplicates them.
Even so, download the CSV from Tally (Submissions → download) before you close anything. It costs you a minute and it is your own copy, independent of either product.
Import the form
Open the Tally importer. Two ways in:
- An API key. Tally → Settings → API keys, then paste the key. We use it for that one request and never store it. Tally gives its API away on every plan, which is what makes this possible.
- A JSON file. If you would rather not hand over a key, export the form as JSON and upload the file instead.
Every imported form arrives as a draft, so nothing goes live until you say so. The importer article covers the input options in more detail.
What transfers, and what does not
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, progress bar, theme colours — and your existing responses, with their original dates. Your images are copied onto Pulseware too, so nothing breaks when you close the old account.
Needs a hand: 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 survey always finishes.
Does not come across: a payment step, because we do not have payments yet; form passwords, which you set fresh; and the device, country and timing behind your old responses, which Tally does not hand out. The import report names every one of these against the block it came from — nothing is dropped quietly.
After the import
- Read the import report. Anything marked "needs review" is genuinely worth reviewing.
- Open the Logic tab and walk the flow map. See logic and scoring.
- Reconnect your integrations. Webhook payloads differ between the two products, so re-test anything downstream. See integrations.
- Turn notifications back on. Emails to you are free; respondent confirmation emails need Pro.
- Replace the embed snippet on your site with the new one from the Share tab — see sharing and embedding.
- Submit a test response, then delete it.
- Update your links, buttons and QR codes, and close the Tally form with a message pointing at the new one.
Before you commit: what you would give up
Tally does several things we do not. Payments inside the form, custom domains, team workspaces, a public API, 50+ interface languages, connectors for AI assistants, a much larger template library and a much deeper help centre. If any of those is load-bearing for you, staying put is the right call and we would rather you knew now.
The full, dated list is on the Pulseware vs Tally comparison — including every row where Tally comes out ahead.
Did this answer your question?
If it did not, tell us what was missing and we will fix the article. Help pages that leave people stuck are worse than no help page at all.