migrating toBrowse playbooks
← All playbooks
Forms and surveys migration

Jotform → Tally

Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Jotform to Tally with a reversible cutover, explicit exception ledger, and evidence-backed verification.

Typical timeline15–45 business days70–180 hours active work
Statusneeds review
Source profileJotform documentation reviewed 2026-07-20
Destination profileTally documentation reviewed 2026-07-20
Documentation date
Review window
Evidence2 sources
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Jotform

Reasons to stay
  • A huge template and integration ecosystem supports complex forms, documents, payments, and approvals
  • Hosted builders make data collection, logic, publishing, and integrations quick to operate
Reasons to leave
  • Advanced forms can accumulate proprietary widgets, conditions, apps, and generated documents
  • Question logic, response history, embeds, and connected workflows use proprietary models
New platform

Tally

What gets better
  • A clean document-like builder, generous free tier, logic, payments, and integrations make forms quick to publish
  • Hosted builders make data collection, logic, publishing, and integrations quick to operate
What gets worse
  • Smaller enterprise governance, migration, and ecosystem capabilities may limit complex organizations
  • Question logic, response history, embeds, and connected workflows use proprietary models
Best of the move

Tally: A clean document-like builder, generous free tier, logic, payments, and integrations make forms quick to publish. This removes a major source-side concern: Advanced forms can accumulate proprietary widgets, conditions, apps, and generated documents.

Worst of the move

What you lose: A huge template and integration ecosystem supports complex forms, documents, payments, and approvals. What you inherit: Smaller enterprise governance, migration, and ecosystem capabilities may limit complex organizations.

Connected catalog

2 destinations are documented from Jotform. Compare nearby routes before committing.

Also from Jotform
Also moving to Tally
Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome10 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 4, Manual rebuild: 5, Not transferred: 1.
Clean0
Partial4
Manual5
Lost1
Mapping route9 of 9 fields have a destination path

This timeline assumes

  • Up to 1,000 forms, 10 million responses, 100 GB of uploads, and 250 integrations
  • Administrators control both Jotform and Tally, including billing, identity, APIs, integrations, and export permissions.
  • Jotform remains intact and recoverable until Tally completes one representative operating cycle.
  • A production-shaped pilot includes every object type, access class, edge case, and failure path.
  • The migration team preserves stable source identifiers and records durable evidence for every blocking check.
02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
Forms, pages, questions, and field IDspartialcriticalQuestion types, internal IDs, page structure, validation, and hidden fields differ. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Map forms, pages, questions, and field ids explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Logic jumps, branching, scoring, and calculationsmanualcriticalConditional logic, formulas, answer piping, quizzes, and outcome routing require reconstruction. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Inventory and rebuild logic jumps, branching, scoring, and calculations, then test normal, edge, failure, and rollback behavior.
Responses and stable submission identitypartialcriticalExports flatten nested answers and can change respondent, form, field, and submission identifiers. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Map responses and stable submission identity explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
File uploads and respondent attachmentspartialcriticalResponse exports can omit binaries or preserve authenticated source-only download URLs. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Map file uploads and respondent attachments explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Themes, layouts, localization, and accessibilitymanualhighVisual design, custom CSS, translations, keyboard behavior, and accessibility output differ. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Inventory and rebuild themes, layouts, localization, and accessibility, then test normal, edge, failure, and rollback behavior.
Notifications, confirmations, and redirectsmanualhighEmail rules, respondent receipts, thank-you pages, redirects, and PDF output require rebuilding. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Inventory and rebuild notifications, confirmations, and redirects, then test normal, edge, failure, and rollback behavior.
Payments, signatures, and consent evidencepartialcriticalPayment tokens, signature evidence, consent wording, timestamps, and legal records need separate review. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Map payments, signatures, and consent evidence explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Embeds, domains, links, and QR codesmanualcriticalEmbed code, form URLs, custom domains, cookies, and published QR destinations change. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Inventory and rebuild embeds, domains, links, and qr codes, then test normal, edge, failure, and rollback behavior.
Webhooks, apps, and automationmanualcriticalConnected sheets, CRMs, webhooks, API keys, and workflow ownership remain source-bound. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Inventory and rebuild webhooks, apps, and automation, then test normal, edge, failure, and rollback behavior.
Analytics, partial responses, and historylosthighDrop-off analytics, partial starts, view history, attribution, and platform reports do not transfer. A successful bulk job therefore does not prove semantic parity between Jotform and Tally.Archive analytics, partial responses, and history as dated source evidence and define the new destination baseline.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Jotform: Forms, pages, questions, and field IDsTally: approved forms, pages, questions, and field ids representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for forms, pages, questions, and field ids.
Jotform: Logic jumps, branching, scoring, and calculationsTally: approved logic jumps, branching, scoring, and calculations representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for logic jumps, branching, scoring, and calculations.
Jotform: Responses and stable submission identityTally: approved responses and stable submission identity representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for responses and stable submission identity.
Jotform: File uploads and respondent attachmentsTally: approved file uploads and respondent attachments representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for file uploads and respondent attachments.
Jotform: Themes, layouts, localization, and accessibilityTally: approved themes, layouts, localization, and accessibility representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for themes, layouts, localization, and accessibility.
Jotform: Notifications, confirmations, and redirectsTally: approved notifications, confirmations, and redirects representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for notifications, confirmations, and redirects.
Jotform: Payments, signatures, and consent evidenceTally: approved payments, signatures, and consent evidence representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for payments, signatures, and consent evidence.
Jotform: Embeds, domains, links, and QR codesTally: approved embeds, domains, links, and qr codes representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for embeds, domains, links, and qr codes.
Jotform: Webhooks, apps, and automationTally: approved webhooks, apps, and automation representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for webhooks, apps, and automation.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Jotform data, configuration, access, and operating evidence before any destination write.

  1. Export every available Jotform object and binary in scope, including forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments.
  2. Capture configuration and runtime dependencies for themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes.
  3. Record counts, sizes, owners, timestamps, access classes, financial totals where applicable, and known exceptions.
  4. Hash immutable exports, record tool versions and commands, and transform working copies only.

Proof to capture: A signed manifest accounts for every scoped record class, configuration object, binary, count, total, exception, and hash.

Transformation · Version-controlled migration workbook, SQL, or typed transformation code

Identity, schema, and disposition registry

Preserve stable identity and make every mapping or exclusion reviewable.

  1. Inventory source types, identifiers, owners, states, and access.
  2. Define one approved destination representation or explicit archive decision.
  3. Reject unmapped critical items and produce an exception ledger.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Official APIs, provider importers, checksums, and reconciliation scripts

Dependency-ordered migration package

Load prerequisite identities and configuration before dependent records and runtime actions.

  1. Normalize encoding, timestamps, identifiers, nulls, and destination limits.
  2. Run a representative pilot and retain request, response, and rejection evidence.
  3. Reconcile the final delta before enabling destination production writers.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Import

A completed migration hides missing or altered forms, pages, questions, and field ids

criticalpossible likelihood

Headline counts look plausible while semantic, access, or relationship checks fail.

Consequence
The destination becomes authoritative with incomplete or misleading business data.
Mitigation
Reconcile by type, state, owner, access class, and representative record rather than total count alone.

Stop if: Any critical item lacks a verified destination, approved transformation, explicit exclusion, or recoverable archive.

Cutover

Jotform and Tally both perform production actions

criticalpossible likelihood

Users, schedules, webhooks, integrations, or traffic continue changing both systems.

Consequence
State diverges or customers receive duplicate, contradictory, or unsafe actions.
Mitigation
Freeze source writers and transfer one production owner at a time with an approved rollback.

Stop if: An unapproved source writer or destination duplicate action appears after the freeze.

Verification

Destination access or security is broader than approved

criticalpossible likelihood

A representative restricted user can read, change, export, or trigger an unauthorized item.

Consequence
Confidential, regulated, financial, or security-sensitive data is exposed or changed.
Mitigation
Apply least privilege before bulk loading and test every access class using ordinary identities.

Stop if: Any unauthorized read, write, export, administrative action, or secret access succeeds.

06Precise timeline

Do the work in this order.

Estimate forUp to 1,000 forms, 10 million responses, 100 GB of uploads, and 250 integrations
Total elapsed15–45 business days
Active work70–180 hours
BufferAdd time for large Jotform exports, destination rate limits, unsupported features, identity exceptions, regulated data, or a strict downtime objective.
01
Days 1–4Inventory and decisions2–4 days
02
Days 3–8Backup and reconcile2–5 days
03
Days 6–20Map, transform, and pilot5–12 days
04
Days 18–35Bulk load, final delta, and switch2–8 days
05
Days 25–45Observe and close7–14 days
  1. Days 1–4 · inventory

    Inventory and decisions

    8–16 hours active2–4 days elapsedOwner, legal, security, and finance review waiting
    • Inventory Jotform data, configuration, identities, integrations, limits, and billing.
    • Approve scope, owners, mappings, exclusions, acceptance thresholds, and rollback authority.

    Depends on: Jotform and Tally administrator access

    Stop / go checkpoint

    Export?

    Go when: Every critical item and production action has an owner and disposition.

    Stop when: Authority, retention, billing, access, or system ownership is unclear.

  2. Days 3–8 · backup

    Backup and reconcile

    8–20 hours active2–5 days elapsedProvider export processing waiting
    • Create immutable data, configuration, binary, and audit exports.
    • Reconcile source counts, totals, sizes, access classes, and hashes.

    Depends on: Approved inventory and retention location

    Stop / go checkpoint

    Transform?

    Go when: The signed source manifest and exports agree.

    Stop when: Any critical dataset, binary, configuration, or recovery path is absent.

  3. Days 6–20 · pilot

    Map, transform, and pilot

    25–70 hours active5–12 days elapsedDestination processing and owner review waiting
    • Configure Tally and transform a production-shaped pilot.
    • Test normal records, every feature class, edge cases, permissions, failures, and rollback.

    Depends on: Verified source backup and approved mapping registry

    Stop / go checkpoint

    Scale?

    Go when: Every pilot mapping and blocking verification check passes.

    Stop when: Any critical invariant, access boundary, or production action lacks a safe destination.

  4. Days 18–35 · cutover

    Bulk load, final delta, and switch

    20–55 hours active2–8 days elapsedImports, propagation, indexing, or synchronization waiting
    • Freeze production writes and automated actions in Jotform.
    • Apply and reconcile the final delta, switch ownership to Tally, and run all blocking checks.

    Depends on: Passed pilot, stakeholder go decision, and rehearsed rollback

    Stop / go checkpoint

    Open production?

    Go when: Tally is the sole production owner and every critical exception is resolved.

    Stop when: A source writer remains active, a blocking check fails, or rollback is unavailable.

  5. Days 25–45 · observe

    Observe and close

    9–19 hours active7–14 days elapsedRepresentative operating-cycle evidence waiting
    • Monitor correctness, access, failures, latency, delivery, cost, and user outcomes.
    • Sign the verification report and close rollback only after stable evidence.

    Depends on: Verified cutover

    Stop / go checkpoint

    Close rollback?

    Go when: No trigger occurs during the approved observation period.

    Stop when: Data, access, delivery, routing, cost, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Tally the only production system without losing the final Jotform delta.

Recommended window: A low-volume weekday morning with platform, data, security, networking, finance, and business owners available.

  1. Freeze user, integration, schedule, and API writes in Jotform.
  2. Capture and reconcile the final source delta against the last verified checkpoint.
  3. Apply the approved delta and configuration changes to Tally.
  4. Switch traffic, domains, integrations, credentials, automation, and user entry points in dependency order.
  5. Run every blocking verification check and keep the source intact.

Proof to capture: Tally alone owns production, totals reconcile, exceptions are signed, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Jotform without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, keys, or retention settings are changed.

  1. Stop new user, integration, schedule, and API writes in Tally.
  2. Restore prior Jotform traffic, domains, credentials, automation, and integration ownership.
  3. Export and classify the Tally post-cutover delta.
  4. Apply safe destination-era changes back to Jotform without duplicating actions.
  5. Run the same blocking checks against the restored source.

Proof to capture: Jotform again owns production with current data and no duplicate destination action.

Rollback immediately when
  • Unexplained critical count, value, relationship, or checksum variance
  • Missing, corrupted, or exposed critical data
  • Duplicate production action or unresolved split-brain state
  • Failed access, security, delivery, routing, performance, or integration check
  • A critical feature has no safe destination replacement or rollback path
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingForms, pages, questions, and field IDs reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for forms, pages, questions, and field ids.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Forms, pages, questions, and field IDs ledger with counts, exceptions, sample IDs, and owner sign-off.
V-02BlockingLogic jumps, branching, scoring, and calculations reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for logic jumps, branching, scoring, and calculations.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Logic jumps, branching, scoring, and calculations ledger with counts, exceptions, sample IDs, and owner sign-off.
V-03BlockingResponses and stable submission identity reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for responses and stable submission identity.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Responses and stable submission identity ledger with counts, exceptions, sample IDs, and owner sign-off.
V-04BlockingFile uploads and respondent attachments reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for file uploads and respondent attachments.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.File uploads and respondent attachments ledger with counts, exceptions, sample IDs, and owner sign-off.
V-05Themes, layouts, localization, and accessibility reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for themes, layouts, localization, and accessibility.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Themes, layouts, localization, and accessibility ledger with counts, exceptions, sample IDs, and owner sign-off.
V-06Notifications, confirmations, and redirects reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for notifications, confirmations, and redirects.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Notifications, confirmations, and redirects ledger with counts, exceptions, sample IDs, and owner sign-off.
V-07BlockingPayments, signatures, and consent evidence reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for payments, signatures, and consent evidence.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Payments, signatures, and consent evidence ledger with counts, exceptions, sample IDs, and owner sign-off.
V-08BlockingEmbeds, domains, links, and QR codes reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for embeds, domains, links, and qr codes.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Embeds, domains, links, and QR codes ledger with counts, exceptions, sample IDs, and owner sign-off.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check and exception.

  1. Create final Jotform exports and archive verification, access, financial, and rollback evidence.
  2. Revoke temporary credentials, API keys, webhooks, elevated roles, and migration network access.
  3. Remove obsolete jobs, embeds, domains, integrations, collectors, routes, and DNS records.
  4. Keep the source intact and read-only through the approved legal and operational retention window.
  5. Cancel paid plans only after billing, legal, security, evidence, and recovery review.
  6. Schedule the next Tally backup, restore test, access review, and migration-playbook review.
Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

  1. Jotform: official portability and migration documentationAccessed 2026-07-20
  2. Tally: official portability and migration documentationAccessed 2026-07-20