Jotform Enterprise Adds Existing Table Data Import for Faster Migrations.

Jotform Enterprise is removing a tedious obstacle from data migration. Organizations can now import external data directly into an existing Jotform Table, rather than creating another table or copying rows into place manually.

The feature targets a common operational problem for businesses that collect information across forms, spreadsheets, and external systems. According to Jotform’s official blog post, the update became available to Enterprise customers on July 28, 2026.

It is a narrow change, but one that could save meaningful time for teams consolidating customer records, registrations, inventories, or internal requests.

Previously, importing an external dataset through Jotform could require creating a new table. If an organization needed the records inside an established Table, with its existing structure and workflow, staff had to move the information separately or paste rows one by one.

That process created more than clerical work. New tables could fragment related records, while manual copying increased the likelihood of missed rows, inconsistent formatting, and duplicate entries. The larger the dataset, the harder it became to verify that the migration was complete.

Direct import changes that flow. A team can retain its existing destination Table while bringing in data accumulated elsewhere. This is particularly relevant when a Jotform deployment is replacing spreadsheets gradually, or when different departments have maintained separate datasets that now need to be centralized.

Potential use cases include:

• Adding historical customer or member records to an active Table
• Consolidating information from departmental spreadsheets
• Moving legacy form results into a current operational dataset
• Updating an established Table without rebuilding it from scratch
• Combining records gathered through multiple sources

The update also fits Jotform’s broader effort to become a workflow platform rather than only a form builder. It follows additions such as the company’s AI App Builder and Jira integration, which expanded how collected data can feed into business processes.

Direct import reduces the mechanical work, but it does not eliminate the need to prepare data carefully. Teams should review column names, date formats, required fields, and duplicate records before moving a large dataset. A small test import can also reveal mismatches before they affect the full Table.

A practical migration checklist should include:

1. Preserve the original dataset. Keep an untouched spreadsheet or export as a recovery copy.
2. Standardize the source. Normalize headings, names, dates, and other frequently inconsistent values.
3. Review the destination Table. Confirm that its fields align with the information being imported.
4. Test with a limited sample. Check where each value lands and whether formatting remains usable.
5. Validate the completed import. Compare row totals and inspect important records before treating the migration as finished.

Administrators should also examine any workflows connected to the destination Table. Imported records may differ from new form submissions, so teams should verify the behavior of downstream processes rather than assuming every connected action will respond in the same way.

Jotform’s announcement identifies the capability specifically as an Enterprise feature. The company does not provide separate pricing for it in the post, nor does the supplied announcement detail every supported file format or field limitation. Organizations planning a complex migration should confirm those requirements with Jotform before moving production data.

For Enterprise teams already using Tables as a central workspace, however, the immediate benefit is straightforward: existing records can remain where they are, while outside data comes to them.

What is Jotform’s existing Table data import?

It is a Jotform Enterprise feature that lets organizations import external data directly into a Jotform Table they already use. Previously, moving that data could require creating a new table or copying rows manually.

Who can use the new import capability?

Jotform describes the feature as part of Jotform Enterprise. The announcement does not state that it is available on Jotform’s other plans.

When did Jotform announce existing Table imports?

Jotform published the update on July 28, 2026. The announcement presents the capability as available to Enterprise customers, but does not list a phased rollout schedule.