Moving from another tool
Using the Tally importer
The importer reads a Tally form and rebuilds it here as a draft. It takes an API key or a JSON file, and it tells you exactly what it could not map.
Last updated
Two ways to hand over a form
API key. In Tally, go to Settings → API keys and create one. Paste it into the importer and pick which forms to bring across. The key is used for that request and nothing else: it is never written to our database, never logged, and never sent back to your browser.
JSON file. If you would rather not share a key at all, export the form as JSON and upload the file. Same result, one more step.
We do not read your public Tally pages to scrape a form. Those are Tally's pages, and scraping them is not our business.
The import report
Every import produces a report in three parts:
- Mapped. Came across as-is.
- Approximated. Came across as the nearest thing we have, and the report says what changed.
- Not supported. Could not come across. The report names the block so you can find it.
Read it once before you publish. It is faster than discovering a missing branch from a confused respondent.
Then what
The imported survey is a draft. Nothing is published, nothing is collecting and nothing is shared until you press publish. Work through the full switching guide, or go straight to the editor basics if you already know what you want to change.
If the report lists something you cannot work around, send it to us. Import gaps are the fastest bug reports we get, and we fix them.
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.