Archiving Old WordPress Form Submissions in Google Sheets

WordPress runs roughly 43% of all websites (W3Techs, 2026), and most of those sites collect form data into the database. Every entry, every field, every uploaded file reference lives in wp_postmeta or a plugin's custom tables. Over months, that table balloons.

A bloated database slows admin queries, inflates backups, and makes migrations painful. The fix is to treat WordPress as the capture layer, not the permanent store.

Google Sheets becomes your durable record. Submissions flow there in real time, and you archive old rows on a schedule so the live sheet stays quick. This post walks through the full strategy, including limits, rolling tabs, and a clean archive workflow.

Yes. The single most effective tactic is splitting recent submissions from historical ones. With WordPress on 43% of websites (W3Techs, 2026), high-traffic forms generate data that quickly outgrows one tab. A two-tier model keeps things manageable.

The live sheet holds the current window, often the trailing 30 to 90 days. It stays small, recalculates fast, and powers your dashboards and CRM syncs.

The archive holds everything older. It can be a separate tab, a separate workbook, or a yearly file. You rarely open it, so its size barely matters for daily work.

This separation also limits blast radius. A broken formula or accidental sort in the live sheet never touches the archived record of past leads.

The cleanest method is a date-based cutoff: any row older than your retention window moves to the archive. Because spreadsheets are error-prone, with audits finding errors in up to 88% of inspected spreadsheets (Panko, 2008), automate the move rather than dragging rows by hand.

A simple Apps Script approach: read rows where the timestamp column is older than 90 days, append them to the archive tab, then delete them from the live tab. Schedule it with a time-driven trigger so it runs nightly or weekly.

Keep the column order identical between live and archive sheets. If they drift, your appendRow calls land data in the wrong columns. Always test the script against a copy first, and log each run so you can confirm what moved. A weekly run on a clean schedule beats a manual purge you forget to do.

Both work, and the right pick depends on volume. Because one spreadsheet maxes out at 10,000,000 cells (Google Workspace Updates, 2022), very high-volume sites eventually need separate yearly workbooks rather than tabs in a single file.

Use archive tabs in the same workbook when total volume stays comfortably under the cell limit. It's simpler: one file, easy cross-tab queries, one share link to manage.

Use separate workbooks (one per year, for example) when you'd otherwise blow past the cell ceiling or when the file gets too heavy to open. The tradeoff is that cross-workbook reporting needs IMPORTRANGE and authorized links.

For most sites, start with tabs and graduate to yearly workbooks only when the numbers force it. Don't over-engineer early.

SheetLink Forms is the ingestion layer that makes Sheets your durable record in the first place. It sends submissions from 12 core form plugins (17 with the Integrations Bundle) straight to Google Sheets, with no Zapier or per-task fees, even as you scale toward the 10,000,000-cell limit (Google Workspace Updates, 2022).

Because each sync rule targets a specific spreadsheet and tab, you can route new entries to the current month's tab and keep your archive untouched. A built-in retry queue with exponential backoff means a brief Sheets outage delays delivery rather than losing data.

That reliability matters for archiving: your Sheet is only a safe permanent store if every submission actually arrives. Pair it with a scheduled archive script and you offload database bloat while keeping a complete, queryable history. Read the complete setup guide or the Sheets setup docs to get started.