Loading…
Loading…
Jotform to Microsoft Excel, wired so submissions append as rows in an Excel Online workbook your Microsoft 365 team already shares.
For teams on Microsoft 365, the Jotform to Excel integration is the equivalent of the Google Sheets one: each submission appends as a new row in an Excel Online workbook, so the whole team can see what's coming in without logging into Jotform. It writes to a workbook stored in OneDrive or SharePoint, which means it stays inside the Microsoft environment you already use.
It behaves much like the Sheets integration, and so do its rough edges. The sync isn't instant, editing the workbook's structure after setup can break the column mapping, and it works against a cloud-hosted Excel Online file, not a desktop .xlsx sitting on someone's laptop. If you understand those constraints up front, it's a dependable way to get form data into the spreadsheet tool your team prefers. This page covers how it appends rows, where it breaks, and when to use Excel versus Google Sheets or a webhook.
I spent five years on Jotform's product team. The Excel and Sheets integrations drew nearly identical tickets: structure edits breaking the mapping and confusion about which file the data was going to. Here's how to set it up so rows land clean.
In Jotform's Integrations tab you authorize Microsoft access and choose an Excel Online workbook stored in OneDrive or SharePoint, then the worksheet within it. This is a cloud-hosted file, not a desktop spreadsheet on someone's machine.
Jotform matches form fields to columns, with the header row defining the columns. On initial setup it maps by field, and the column order follows the form's field order. Get the headers right before submissions start flowing.
Each new submission adds a row to the worksheet. Like the Sheets integration, this is not instant; data arrives on a short delay rather than in real time, which is fine for review and reporting but not for live dashboards.
Because the file lives in OneDrive or SharePoint, the team opens it in Excel Online or the desktop app via sync and sees rows accumulate. They can add their own columns for status or notes, with the same caution about not disturbing the mapped columns.
A registration or order form appends each entry to a shared workbook the team reviews. Works well at modest volume; like any spreadsheet, it gets sluggish and error-prone once rows climb into the thousands.
Submissions land in a workbook where the team adds status and owner columns to track follow-up. Cheaper than a CRM for a small team, with the same limits: no real dedup or pipeline logic.
Feedback responses append to a workbook that someone pivots or charts in Excel. Fine for periodic analysis; the sync delay means anything 'live' is always slightly behind.
The workbook feeds Power BI or other Microsoft reporting that the organization already runs, keeping the whole pipeline in one ecosystem.
If you add, rename, or reorder columns after the integration is live, Jotform keeps writing to the original positions and data lands in the wrong cells. Don't restructure the mapped area after setup; if you must, disconnect, restructure, and reconnect.
Rows arrive on a short delay, and under burst traffic the queue can back up further. For genuinely live data, use a webhook to write to the workbook via the Microsoft Graph API instead of relying on the polling-style sync.
The integration targets a cloud-hosted workbook in OneDrive or SharePoint. A local .xlsx on someone's laptop isn't a valid destination. If the team expects data in a desktop file, they need to work the synced cloud copy.
Fields hidden by conditional logic can land blank depending on visibility at submit time. If you need every field regardless of whether it was shown, confirm the integration is set to include them.
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your Microsoft Excel setup, or send me the details first.
Skip the native integration if you need real-time data (use a webhook to the Microsoft Graph API), if you need deduplication or pipeline stages (use a CRM), or if you expect very high volume where any spreadsheet gets sluggish. Choose Google Sheets instead if your team lives in Google rather than Microsoft 365. And don't treat a workbook as a compliant store for PHI or regulated data without the appropriate Microsoft 365 agreement and configuration.

Camp registration: signup, payment, waivers, waitlists, check-in. One Jotform.

Lead capture with scoring, dedup, CRM sync, and Slack alerts on the ones worth interrupting for.

NPS that actually does something: detractors escalate, promoters refer, and leadership gets the monthly read
In Jotform's Integrations tab, authorize Microsoft, choose an Excel Online workbook stored in OneDrive or SharePoint, and select the worksheet. Jotform maps fields to columns using the header row. Each submission then appends a row. Note it targets a cloud-hosted workbook, not a desktop .xlsx file.
Most common causes: someone edited the workbook columns after setup (breaks the mapping), the Microsoft authorization expired (re-authorize in the integration settings), or you're pointing at the wrong file. It also targets Excel Online in OneDrive or SharePoint, so a local desktop file won't work. Check the integration log for the specific error.
Use Excel if your team runs on Microsoft 365 and you want the data inside OneDrive or SharePoint, especially to feed Power BI. Use Google Sheets if your team lives in Google Workspace. Both behave similarly: a short sync delay and the same caution about not editing columns after setup.
No. Rows append on a short delay rather than instantly, and under burst traffic the queue can back up further. For live data, use a webhook that writes to the workbook via the Microsoft Graph API instead of the native polling-style sync.
Free 20-minute call. I'll tell you which workflow fits your Microsoft Excel setup and what it would take to build, or you can send me the details first.