Tiers and features move between versions, so treat this as a starting point and confirm on your own install: open the plugin’s entries screen. A full table with an export button means you are covered. A teaser screen, or no menu at all, means you are not.<\/p>\n
Exporting from the builder you already have<\/h2>\n
The native route is almost always the right one \u2014 it is free, it is already installed, and it knows your field names. We have written each of these up step by step:<\/p>\n
- \n
- Fluent Forms<\/a> \u2014 the most generous of the lot: four formats, free, and the export follows whatever the entries table is filtered to.<\/li>\n
- Gravity Forms<\/a> \u2014 Forms → Import\/Export, one form at a time, with conditional-logic and date filters.<\/li>\n
- WPForms<\/a> \u2014 read this one first if you are on Lite, because the entries may not exist to export.<\/li>\n
- Contact Form 7<\/a> \u2014 depends entirely on which storage add-on you added.<\/li>\n<\/ul>\n
Two things worth knowing before you click: most builders export one form at a time<\/strong>, and most exports respect the filters showing on screen. Set the filters first, or you will get either everything or, worse, a forgotten search term’s worth of nothing.<\/p>\n
If your builder stores nothing at all<\/h2>\n
Contact Form 7 is the one that catches people out. It formats an email, sends it, and keeps no record \u2014 so there is nothing to export until something is saving entries, and nothing can recover submissions from before you installed it.<\/p>\n
The free fix is Flamingo<\/strong>, written by Contact Form 7’s own author. Contact Form 7 ships a Flamingo module, so there is no configuration: install it and entries start appearing under Flamingo → Inbound Messages. Its CSV export is filtered by channel (one per form), by month, and by search term. Our CF7 storage guide<\/a> walks through it.<\/p>\n
The export gotchas that apply to every plugin<\/h2>\n
These are not bugs in any particular form plugin. They will bite you the same way whichever one you use, and they are the reason a “finished” export often is not.<\/p>\n
Excel mangles accented characters<\/h3>\n
Exports are UTF-8. Double-clicking the file in Excel on Windows makes it assume the local codepage, and accented characters, curly quotes and non-Latin scripts turn to mojibake. Do not double-click: open Excel first, then Data → From Text\/CSV<\/strong>, and set File Origin to UTF-8 in the preview. Google Sheets and LibreOffice get this right on import.<\/p>\n
Leading zeros disappear<\/h3>\n
Postcodes like 01234, phone numbers, and any reference starting with zero get read as numbers and lose the zero. Same import dialog, same fix: mark those columns as Text<\/strong> before the data lands. Once you have imported and saved, the zeros are gone and you have to start again from the original file.<\/p>\n
Checkboxes collapse into one cell<\/h3>\n
Three ticked options usually export as one cell containing all three, joined by a separator. Counting how many people picked each option means splitting that column afterwards \u2014 and if the separator is a comma and an option label contains one too, the split goes wrong. Good argument for keeping commas out of checkbox labels.<\/p>\n
File uploads are links, not files<\/h3>\n
An upload field exports the URL of the stored file. Delete the entries or clean the uploads directory later and the CSV points at nothing. And unless uploads are protected, those URLs are reachable by anyone holding the spreadsheet, which matters when people have uploaded CVs or ID documents. Download the files separately if the export is meant to be an archive.<\/p>\n
The timestamp column’s timezone<\/h3>\n
Timestamps are stored in UTC and displayed per your WordPress timezone setting. Whether the exported column carries the local rendering or raw UTC varies by plugin. Before you build a report on it, submit one test entry and check what the CSV actually says \u2014 an unnoticed offset quietly moves submissions across day boundaries.<\/p>\n
The test that catches all five at once:<\/strong> submit a single entry with an accented character, a leading zero, two checkboxes ticked and a file attached, then export it. That tells you more about your setup than any guide, this one included.<\/p>\n
When one board across every builder is worth it<\/h2>\n
Everything above assumes one form plugin. Plenty of sites accumulate two or three over the years, and then the native route stops being enough: each plugin only knows its own entries, so “everything from last week” means three exports and some spreadsheet stitching.<\/p>\n
Full disclosure: EntryVault<\/a> is ours. It captures from seventeen builders into one board, so the export is one file with a Source column instead of three files to reconcile. It is worth adding for that, for tags and stages on entries, and for filtering by an arbitrary date range rather than whole months. It is not<\/em> worth adding if you run one builder that already exports well \u2014 Fluent Forms users in particular already have everything this section describes.<\/p>\n
![\"Submissions](\"https:\/\/jnkplugins.com\/blog\/wp-content\/uploads\/2026\/07\/shot-ev-submissions.png\")
The Source column is the whole argument: entries from different builders in one list. If you only run one builder, you do not need this.<\/figcaption><\/figure>\n The bottom line<\/h2>\n
Check your builder’s entries screen first \u2014 most of them already store and export, free, and that is the end of the job. If you are on Contact Form 7, install Flamingo. Reach for a cross-builder tool only when you genuinely have more than one builder to reconcile. Whatever route you take, run the five-gotcha test entry before you trust an export.<\/p>\n
<\/p>\n
Frequently asked questions<\/h2>\n
Which WordPress form plugins store entries by default?<\/h3>\n
Most of the big ones: Fluent Forms, Gravity Forms, Formidable, Ninja Forms, Everest Forms and WS Form all keep submissions and offer a CSV export. WPForms puts entries and export in its paid tiers. Contact Form 7 is the exception that catches people out — it stores nothing at all and needs a companion plugin.<\/p>\n
How do I export WordPress form entries to CSV?<\/h3>\n
Use your form plugin’s own export first — it is free, already installed, and knows your field names. Open the plugin’s entries screen, set any filters you want, and look for an Export button; most builders export one form at a time and most exports respect whatever the screen is currently filtered to.<\/p>\n
Why do accented characters break when I open the CSV in Excel?<\/h3>\n
Because Excel guesses the encoding. Exports are UTF-8, and double-clicking the file on Windows makes Excel assume the local codepage, which garbles accented and non-Latin characters. Open Excel first, use Data then From Text\/CSV, and set the file origin to UTF-8. Google Sheets and LibreOffice handle it correctly on their own.<\/p>\n
Why did the leading zeros vanish from my postcodes?<\/h3>\n
The spreadsheet read the column as numbers. This is spreadsheet behaviour rather than a form plugin bug, and it hits every export the same way. In the same import dialog, mark those columns as Text before the data lands. Once you have imported and saved, the zeros are gone and you have to re-import from the original file.<\/p>\n
Does the export include uploaded files?<\/h3>\n
No. An upload field exports the URL of the file, not the file itself. If the entries or the uploads directory are cleaned out later, the CSV points at nothing. And unless uploads are protected those URLs are reachable by anyone holding the spreadsheet, which matters when people have uploaded CVs or ID documents.<\/p>\n
How do I get entries from several form plugins into one export?<\/h3>\n
You cannot with the native tools, because each plugin only knows its own entries. Either export from each one and stitch the files together, or use a cross-builder entry manager that captures from all of them into a single list. It is only worth adding a tool for this if you genuinely run more than one form plugin.<\/p>\n
Related reading<\/h2>\n
- \n
- How to export Contact Form 7 entries to CSV<\/a> \u2014 the CF7-specific route, including very large archives<\/li>\n
- Exporting WordPress posts to CSV<\/a> \u2014 the same job for your content instead of your form entries<\/li>\n
- Migrating form entries between plugins<\/a> \u2014 moving stored entries when you switch form builders<\/li>\n<\/ul>\n
- Exporting WordPress posts to CSV<\/a> \u2014 the same job for your content instead of your form entries<\/li>\n
- Gravity Forms<\/a> \u2014 Forms → Import\/Export, one form at a time, with conditional-logic and date filters.<\/li>\n