Forms and surveys migration

Jotform → Typeform

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 Typeform 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 profileTypeform documentation reviewed 2026-07-20

Documentation date2026-07-20

Review window2026-07-202026-10-20

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

Typeform

What gets better

Polished conversational forms, logic, embeds, and integrations create a strong respondent experience
Hosted builders make data collection, logic, publishing, and integrations quick to operate

What gets worse

One-question presentation, logic references, themes, and response analytics are difficult to reproduce elsewhere
Question logic, response history, embeds, and connected workflows use proprietary models

Best of the move

Typeform: Polished conversational forms, logic, embeds, and integrations create a strong respondent experience. 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: One-question presentation, logic references, themes, and response analytics are difficult to reproduce elsewhere.

Jump to a section

01At a glance

Know the shape of the move.

Transfer outcome10 features audited

Clean0

Partial4

Manual5

Lost1

Mapping route9 of 9 fields have a destination path

SourceJotform9 mapped fields

Automatic0

Transform4

Manual5

Unsupported0

DestinationTypeform9 supported paths

This timeline assumes

Up to 1,000 forms, 10 million responses, 100 GB of uploads, and 250 integrations
Administrators control both Jotform and Typeform, including billing, identity, APIs, integrations, and export permissions.
Jotform remains intact and recoverable until Typeform 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.

Item	Outcome	Impact	What happens	Mitigation
Forms, pages, questions, and field IDs	partial	critical	Question types, internal IDs, page structure, validation, and hidden fields differ. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	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 calculations	manual	critical	Conditional logic, formulas, answer piping, quizzes, and outcome routing require reconstruction. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	Inventory and rebuild logic jumps, branching, scoring, and calculations, then test normal, edge, failure, and rollback behavior.
Responses and stable submission identity	partial	critical	Exports 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 Typeform.	Map responses and stable submission identity explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
File uploads and respondent attachments	partial	critical	Response exports can omit binaries or preserve authenticated source-only download URLs. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	Map file uploads and respondent attachments explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Themes, layouts, localization, and accessibility	manual	high	Visual design, custom CSS, translations, keyboard behavior, and accessibility output differ. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	Inventory and rebuild themes, layouts, localization, and accessibility, then test normal, edge, failure, and rollback behavior.
Notifications, confirmations, and redirects	manual	high	Email 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 Typeform.	Inventory and rebuild notifications, confirmations, and redirects, then test normal, edge, failure, and rollback behavior.
Payments, signatures, and consent evidence	partial	critical	Payment 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 Typeform.	Map payments, signatures, and consent evidence explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Embeds, domains, links, and QR codes	manual	critical	Embed code, form URLs, custom domains, cookies, and published QR destinations change. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	Inventory and rebuild embeds, domains, links, and qr codes, then test normal, edge, failure, and rollback behavior.
Webhooks, apps, and automation	manual	critical	Connected sheets, CRMs, webhooks, API keys, and workflow ownership remain source-bound. A successful bulk job therefore does not prove semantic parity between Jotform and Typeform.	Inventory and rebuild webhooks, apps, and automation, then test normal, edge, failure, and rollback behavior.
Analytics, partial responses, and history	lost	high	Drop-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 Typeform.	Archive analytics, partial responses, and history as dated source evidence and define the new destination baseline.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Jotform: Forms, pages, questions, and field IDs	Typeform: approved forms, pages, questions, and field ids representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for forms, pages, questions, and field ids.
Jotform: Logic jumps, branching, scoring, and calculations	Typeform: approved logic jumps, branching, scoring, and calculations representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for logic jumps, branching, scoring, and calculations.
Jotform: Responses and stable submission identity	Typeform: approved responses and stable submission identity representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for responses and stable submission identity.
Jotform: File uploads and respondent attachments	Typeform: approved file uploads and respondent attachments representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for file uploads and respondent attachments.
Jotform: Themes, layouts, localization, and accessibility	Typeform: approved themes, layouts, localization, and accessibility representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for themes, layouts, localization, and accessibility.
Jotform: Notifications, confirmations, and redirects	Typeform: approved notifications, confirmations, and redirects representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for notifications, confirmations, and redirects.
Jotform: Payments, signatures, and consent evidence	Typeform: approved payments, signatures, and consent evidence representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for payments, signatures, and consent evidence.
Jotform: Embeds, domains, links, and QR codes	Typeform: approved embeds, domains, links, and qr codes representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for embeds, domains, links, and qr codes.
Jotform: Webhooks, apps, and automation	Typeform: approved webhooks, apps, and automation representation	manual	Preserve 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.

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.
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.
Record counts, sizes, owners, timestamps, access classes, financial totals where applicable, and known exceptions.
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.

Inventory source types, identifiers, owners, states, and access.
Define one approved destination representation or explicit archive decision.
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.

Normalize encoding, timestamps, identifiers, nulls, and destination limits.
Run a representative pilot and retain request, response, and rejection evidence.
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 Typeform 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.

Days 1–4Inventory and decisions2–4 days

Days 3–8Backup and reconcile2–5 days

Days 6–20Map, transform, and pilot5–12 days

Days 18–35Bulk load, final delta, and switch2–8 days

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 Typeform 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 Typeform 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 Typeform, and run all blocking checks.
Depends on: Passed pilot, stakeholder go decision, and rehearsed rollback
Stop / go checkpoint
Open production?
Go when: Typeform 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 Typeform 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.

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

Proof to capture: Typeform 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.

Stop new user, integration, schedule, and API writes in Typeform.
Restore prior Jotform traffic, domains, credentials, automation, and integration ownership.
Export and classify the Typeform post-cutover delta.
Apply safe destination-era changes back to Jotform without duplicating actions.
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.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	Forms, pages, questions, and field IDs reconciliation	Compare 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-02`Blocking	Logic jumps, branching, scoring, and calculations reconciliation	Compare 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-03`Blocking	Responses and stable submission identity reconciliation	Compare 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-04`Blocking	File uploads and respondent attachments reconciliation	Compare 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-05`	Themes, layouts, localization, and accessibility reconciliation	Compare 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-06`	Notifications, confirmations, and redirects reconciliation	Compare 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-07`Blocking	Payments, signatures, and consent evidence reconciliation	Compare 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-08`Blocking	Embeds, domains, links, and QR codes reconciliation	Compare 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.

Create final Jotform exports and archive verification, access, financial, and rollback evidence.
Revoke temporary credentials, API keys, webhooks, elevated roles, and migration network access.
Remove obsolete jobs, embeds, domains, integrations, collectors, routes, and DNS records.
Keep the source intact and read-only through the approved legal and operational retention window.
Cancel paid plans only after billing, legal, security, evidence, and recovery review.
Schedule the next Typeform 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.

Jotform: official portability and migration documentationAccessed 2026-07-20
Typeform: official portability and migration documentationAccessed 2026-07-20

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

Identity, schema, and disposition registry

Dependency-ordered migration package

The things most likely to hurt.

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

Jotform and Typeform both perform production actions

Destination access or security is broader than approved

Do the work in this order.

Inventory and decisions

Export?

Backup and reconcile

Transform?

Map, transform, and pilot

Scale?

Bulk load, final delta, and switch

Open production?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

Verify against the primary material.