Import your Tally forms
Paste a form’s JSON or enter a Tally API key, and preview what comes across before anything is created. Questions, logic, hidden fields and settings are imported, and the import report lists anything that was not.
Imported surveys arrive as drafts. Nothing goes live until you publish it.
- Choose how to import
- Pick your forms
- Check what comes across
- Done
Choose how to import
Step 1 of 4: Choose how to import
What comes across
68 things Tally can do, and what each becomes here. Checked against Tally’s published API schema on 2026-09-18: 43 come across as they are, 14 come across with a difference to check, 4 are steps you do yourself, and 7 have no equivalent.
Questions
| In Tally | In PulseFormCreator | Status |
|---|---|---|
| Short answer | Short answer Placeholder and maximum length come too. | Comes across |
| Long answer | Long answer | Comes across |
| Number | Number Minimum, maximum, prefix and suffix; % and currency formats become a prefix or suffix. | Comes across |
| Email Tally’s “verify with a code” maps to PulseFormCreator’s, which runs on Business. | Comes across | |
| Phone number | Phone The default country comes across; answers are stored in international format. | Comes across |
| Link | Website | Comes across |
| Date | Date Earliest and latest date come across. Blocked weekdays and specific allowed dates don’t. | Close enough |
| Time | Time | Comes across |
| Multiple choice | Multiple choice (or Checkboxes when several answers are allowed) “Other”, minimum and maximum picks, and shuffling all come across. | Comes across |
| Checkboxes | Checkboxes A lone checkbox becomes a consent tick box. | Comes across |
| Dropdown | Dropdown Up to 200 options; a multi-select dropdown becomes a searchable multi-choice. | Comes across |
| Multi-select | Multi-choice (dropdown) | Comes across |
| Options with images | Picture choice The option images are copied across with the question. | Comes across |
| Ranking | Ranking Shuffling comes across; option images don’t. | Comes across |
| Linear scale | NPS, rating or slider 0–10 becomes NPS, 1–n becomes a rating, anything else becomes a slider. | Comes across |
| Rating | Rating PulseFormCreator allows 2 to 10 points; anything larger is clamped. | Comes across |
| Matrix | Matrix One answer per row. Several answers per row and shuffled rows don’t come across. | Close enough |
| File upload | File upload Accepted types come across; the size limit is capped by your plan (10 MB Free, 5 GB paid). | Close enough |
| Signature | Signature | Comes across |
| Payment | — PulseFormCreator can’t take payments yet. A note is left in the form where it was. | Not transferred |
| Respondent country | — Insights records an approximate country per session instead (off in anonymous mode). | Not transferred |
Layout and media
| In Tally | In PulseFormCreator | Status |
|---|---|---|
| Form title, logo and cover | Survey title and theme The logo and cover are copied onto PulseFormCreator, so they keep working after you close your Tally account. | Comes across |
| Headings | Headings | Comes across |
| Text | Text block Bold, italic, links and bullets are kept. | Comes across |
| Labels | Text block Tally labels sit beside a field; PulseFormCreator puts them on their own line. | Close enough |
| Divider | Divider | Comes across |
| Page break | Page break | Comes across |
| Thank-you pages | Endings The first one becomes the default ending. | Comes across |
| Image | Image The file itself is copied across, with its alt text and caption. A link wrapped around an image isn’t. | Comes across |
| Images hosted by Tally | Copied into your PulseFormCreator storage Up to 30 images per form, 5 MB each, PNG/JPEG/WebP/GIF. Anything larger, or anything that fails, keeps its old link and is listed in the report. | Close enough |
| Video | Video (YouTube, Vimeo, Loom) or embed | Comes across |
| Embed | Embed https addresses only; the height comes across. | Comes across |
| Audio | Embed PulseFormCreator has no audio player, so it becomes a generic embed. Check it loads. | Close enough |
| Columns | Stacked blocks Side-by-side layouts are flattened into reading order. | Close enough |
| Captcha | Spam protection Shows once Turnstile keys are configured for the site. | Comes across |
Logic
| In Tally | In PulseFormCreator | Status |
|---|---|---|
| Conditions (is, is not, contains, starts with, is any of, is every of, empty, number and date comparisons) | The same conditions | Comes across |
| Condition groups | Condition groups One level of nesting. Deeper groups are flattened when they share an and/or, otherwise the rule is reported. | Close enough |
| “Does not start with” / “does not end with” | — Invert the rule instead: show the block when it does, and hide it otherwise. | Not transferred |
| Show blocks | Show this block when… | Comes across |
| Hide blocks | Show this block when… (inverted) Inverted automatically, except for “starts with”, “ends with” and “is every of”, which have no opposite. | Close enough |
| Jump to page | Jump rule, or “end the survey” for a thank-you page Forwards and backwards. A backward jump can repeat, so each block is shown at most three times and the survey always finishes. | Close enough |
| Calculated fields (number) | Variables Add, subtract, multiply, divide and set all come across. | Comes across |
| Calculated fields (text) | Text values Set a value or add to the end of it. Show it in a question with {{var:…}}, or compare it in a rule. | Comes across |
| Formulas in a calculation | Formula operand Copied across as written and flagged for review. | Close enough |
| Require an answer conditionally | “Require an answer” rule The question turns required the moment the conditions hold — checked in the survey and again on submit. | Comes across |
| Hide the submit button | — Send disqualified respondents to their own ending instead. | Not transferred |
| Conditions on today’s date or metadata | — PulseFormCreator logic reads answers, hidden fields and variables only. | Not transferred |
| Hidden fields | Hidden fields Names are kept, so `?name=value` links keep working. Unusual characters are replaced. | Comes across |
| @mentions in text | Answer piping ({{q:…}}) Fallback text is kept. | Comes across |
Settings
| In Tally | In PulseFormCreator | Status |
|---|---|---|
| Close date and time (with time zone) | Schedule | Comes across |
| Submission limit | Response limit | Comes across |
| Closed message | Closed message | Comes across |
| One response per person | Prevent duplicates A field check is matched when we can identify the field; otherwise it falls back to browser and network. | Close enough |
| Progress bar | Progress bar | Comes across |
| Partial submissions | Partial responses The setting comes across; recording partials needs Pro. | Comes across |
| Save and continue later | Save progress | Comes across |
| Auto-jump between pages | Auto-advance | Comes across |
| Redirect on completion | Redirect after submit Mentions in the URL become piped values. | Comes across |
| Data retention | Data retention The setting comes across; deleting on a schedule needs Business. | Comes across |
| Theme colours | Theme colours Matched as closely as PulseFormCreator’s palette allows. Fine-tune in Design. | Close enough |
| Custom CSS | Custom CSS Copied as written, but Tally’s class names differ, so rules need rewriting. Runs on Pro. | Close enough |
| Language | — PulseFormCreator’s built-in labels are English. Your own wording comes across as written. | Not transferred |
| Form password | — Never copied: PulseFormCreator only ever stores a hash. Set a new password in Settings → Access. | Do it yourself |
| Email notifications (to you) | — Listed in the report so nothing starts emailing addresses you haven’t re-confirmed. | Do it yourself |
| Confirmation emails (to respondents) | — Set it up under Connect → Respondent email (Pro). | Do it yourself |
| Integrations (Slack, Notion, Sheets, Airtable, webhooks, Zapier) | — Reconnect the ones you use under Connect. Webhook payloads differ. | Do it yourself |
| Responses already collected | Responses Brought across with their original dates, so your exports and charts still read the way you remember. Re-running never duplicates them. | Comes across |
| Respondent device, country and timing on old responses | — Tally doesn’t hand those out, so imported responses count as submissions but add nothing to the Insights funnel. | Not transferred |
Before you close your Tally form
- Download your responses. In Tally, open Submissions and download the CSV. An API-key import brings responses across, and the CSV is your own copy.
- Check the import report. Anything approximated or not transferred is listed with what to do instead.
- Reconnect your integrations. Slack, Notion, Sheets, Airtable, webhooks and Zapier are set up again under Connect.
- Set a password again if your form had one. We never copy a password we were handed in plain text.
- Replace the embed on your site with PulseFormCreator’s snippet from the Share tab, and update your links and QR codes.
There is a step-by-step version in the guide to moving from Tally, and a feature-by-feature comparison on the Tally alternative page. If your Tally form was short, a template such as the contact form template can be quicker than importing.
Importer questions
- Do my Tally responses come across?
- Yes, when you import with an API key. Responses come across with their original dates, and running the import again does not duplicate them. A JSON file contains the form only, so that path brings no responses. Either way, download your CSV from Tally (Submissions, then Download) before you close the form, so you have your own copy.
- What happens to my Tally API key?
- It is held in memory for the import and then discarded. PulseFormCreator never stores it, never writes it to a log and never sends it back to your browser. You can delete the key in Tally straight afterwards.
- Does the logic still work?
- Conditions, show and hide rules, jumps, calculated fields and hidden fields all come across. A "hide these blocks" rule is inverted into a show rule automatically. Anything that can’t be expressed one to one is listed in the import report and is not applied in part.
- Is my form live as soon as I import it?
- No. Imported surveys arrive as drafts, so a closed or half-built Tally form never goes live by accident. Check the import report, then publish when you are ready.