Migrate from Tally to Formward

The change

Replace the Tally embed with an HTML form that posts to your Formward endpoint, or link to a Formward hosted page instead.

Copy<iframe data-tally-src="https://tally.so/embed/YOUR_FORM_ID"
        width="100%" height="400" frameborder="0" title="Contact"></iframe>
<script async src="https://tally.so/widgets/embed.js"></script>

Copy<form action="https://forms.formward.eu/f/<formId>" method="POST">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <input type="text" name="_gotcha" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>

Field and feature mapping

What changes, what stays

Differences to test before you switch

Specific to Tally

• Tally is a full builder with pages, logic jumps and blocks that only exist inside Tally. Formward is a form backend with hosted pages. Check each Tally block against the field types Formward supports before you switch.
• Long surveys with many branches are easier to build in Tally. Contact, booking, quote and application forms move over without loss.

How Formward behaves

• JSON responses. Send Accept: application/json and a success is a 200 with { ok: true, id }. An error is { ok: false, error } with a status code. Without that header, a successful post redirects or shows Formward's thanks page. Code that only checks res.ok keeps working.
• Status codes. 402 when the plan's monthly submission limit is reached (the body has upgrade: true), 422 when a field fails a validation rule set on the form or required consent is missing, 429 when one address posts too often (with a Retry-After header), and 403 when the origin is not allowed, the Turnstile check fails or files are sent on a plan without uploads.
• File uploads. Uploads need enctype="multipart/form-data" and a plan that includes them: Professional and up (5 files of up to 10 MiB each on Professional). On Free and Personal a post that carries files is refused with 403, so test an upload before you switch a form that takes attachments.
• Redirects. A hidden _redirect is followed only if it is a relative path or a URL on one of the form's allowed origins; otherwise it is ignored and the redirect set on the form applies, then Formward's thanks page. JSON (AJAX) requests are never redirected.
• Spam. If the _gotcha honeypot is filled in, the sender gets a normal success response, but the submission is stored as spam, sends no notification and does not count toward your quota. Rate limits apply on every plan; Cloudflare Turnstile and disposable-email blocking are optional per form.
• Allowed origins. With the list empty, any site can post to the endpoint. Once you add an origin, requests whose Origin header does not match are refused with 403, including server-side requests that send no Origin header.
• Reply-To. The Reply-To of the notification email is taken from _replyto, then _reply_to, then a field named email. So a plain email field sets Reply-To with no rename, and _replyto only overrides it, for example when the email field has another name or the form has several. An invalid address is dropped, and the email then has no Reply-To.

Every status code and body is listed in responses and redirects.

History, integrations and settings

• Get your past responses out of Tally as a CSV file, for example from a Google Sheet filled by Tally's Google Sheets integration. Formward's CSV importer (Dashboard, Import & migrate) takes any CSV with a header row, up to 5,000 rows and 10 MB per file. Imported rows send no email and do not count toward your quota. Each row keeps its original date when the file has a column named Submitted At, created_at or createdAt; otherwise it is dated at import time. Attached files are not imported, only cell values.
• Forms on the Free plan keep submissions for 30 days, and the nightly retention sweep deletes imported rows older than a form's retention window. To keep a longer history, import into a form on a paid plan with a long enough window.
• The form importer on the same page reads Tally's questions (paste the JSON from Tally's API: GET /forms/{formId}/questions, with an API key from your Tally account settings) and creates an inactive draft with the fields mapped. Notification addresses, webhooks, autoresponders and spam settings are listed for you to review and are never switched on by the import.
• Webhooks, Google Sheets, Notion, Slack and other Tally integrations belong to your Tally account and do not move with the endpoint. Recreate the ones you need: Formward webhooks (including Slack, Discord, Teams and Mattermost), Google Sheets and Baserow sync start on Professional, the autoresponder on Professional, and extra notification recipients on Personal.

Step-by-step checklist

1. Create the form. In the Formward dashboard, create a form, set the notification email and copy the endpoint.
2. Import the questions. In Formward open Import & migrate, choose Tally, paste the questions JSON and create the draft.
3. Publish the form. Copy the form's HTML into your page in place of the Tally embed, or publish it as a hosted page and update your links.
4. Rebuild the extras. Recreate hidden fields, the redirect, conditional fields and integrations on the Formward form.
5. Test before you switch. Point a copy of the form at Formward and send a few entries: a normal one, one with the honeypot filled, and one with a file if the form takes uploads. Check the dashboard and the notification email.
6. Bring the history. If you want past submissions, export them as CSV from your old provider and import them under Dashboard, Import & migrate.
7. Retire the Tally form. Switch the live form, watch the first real submissions arrive, then disable the form at Tally so nothing is split between two inboxes.

Importing the form

You do not have to rebuild the form by hand. After signing up, open Import in the dashboard and paste your current form's HTML. Formward creates an inactive draft with the same field names and types, so you can check it before switching.

The importer reads the fields only. Past submissions, integrations, spam settings and email templates are not imported, and nothing is sent to Tally.

Rolling back

• Keep your Tally form active until Formward has received real submissions for a few days. Do not delete it at the moment you switch.
• To go back, put the previous action URL back in the form. Because the move changes only that one attribute, the rollback is one line too.
• If you renamed fields during the move, rename them back as well, or integrations on the Tally side may not recognise them.
• Submissions that reached Formward in the meantime stay in your Formward dashboard. From the Personal plan you can also export them as CSV.