Archive Google Forms responses without losing the attached files

Keep the form's original responses until a second authorised person can find a selected submission and its files in the archive. A downloaded spreadsheet is only one part of that test. The harder questions are whether the collection was complete at a known cutoff, what each column meant, and whether attachments remain accessible without the original owner's help.

This is a proposed archival procedure for an existing Google Workspace setup. It is not a report of a migration we performed, a promise of unlimited collection or a procedure for restoring deleted responses into Forms. It also does not determine your organisation's retention obligations; use the period and access rules your records owner has approved.

Check the limit that is actually affecting you

Google's September 2026 limits are 500,000 responses and 1 GB per form; uploaded files are excluded from that storage limit. Summary views can stop beyond 50,000 responses and Sheets synchronization beyond 100,000. A stale linked Sheet is therefore not proof collection stopped. Google's current response limits.

For existing enterprise forms already above the new limits, Google describes a transition until March 2027, followed by a generated response archive for administrators or owners and deletion of those responses. Google does not specify a day. That exception is not a general extension for every form. Check the in-product notice and administrator's plan. Google's transition guidance.

Record the form's owner, displayed response count, current alert, linked Sheet and upload folder. Assign one person to coordinate the archive and one to approve the result. Keep the response-limit decision separate from the wider Workspace subscription decision: clearing one form does not establish that the organisation can reduce storage or cancel a licence.

Establish a collection boundary before exporting

Pick a cutoff that the people using the form can tolerate. Announce where urgent submissions should go while you reconcile the archive. Use a clear closed-form message rather than leaving applicants guessing whether their work was received.

Google documents stopping responses through the published-form controls and downloading responses as CSV. Its guidance recommends closing collection before downloading and deleting; downloaded rows may be out of timestamp order. Google's response-management instructions.

Record the closure time and verify the public link from a respondent's perspective. Confirm any submission already in progress has been accounted for before deciding which export is final. If collection cannot pause, agree a separate reconciliation method with the data owner; do not delete while the archive still has an uncertain boundary.

Preserve the first export unchanged. Work on a copy for sorting and analysis. Save the current questionnaire, answer choices and any explanation needed to interpret historical values. If questions changed during collection, record the relevant versions; a column heading alone may not explain what earlier respondents were asked.

Reconcile rows as records, not lines of text

Open the CSV with a spreadsheet importer and inspect its parsing. Count response records excluding the header, rather than counting text-file lines: multiline answers can make those different. Compare the record count with the form count at the cutoff and explain every discrepancy before proceeding.

Do not use an email address or timestamp alone as a unique identifier unless your collection design makes it unique. A person may legitimately submit twice. Assign an archive reference for retrieval and preserve the original values alongside it; the reference is your index, not a claim that Google assigned that identifier.

Use a small test matrix before reviewing the whole archive:

Selected submission	Archive check	Stop if
Long multiline answer	The full answer occupies the intended field	Lines became separate records or text is truncated
Repeated respondent	Each legitimate submission remains distinct	Deduplication removed an answer without review
Blank optional answer	The blank is preserved as a blank	Cleanup invented a value or shifted columns
Non-English name and text	Characters remain readable	Encoding changes the meaning
Submission near cutoff	Its inclusion agrees with the recorded boundary	The form and export disagree without explanation

Choose records from different periods and question versions. Keep a discrepancy log with the original record, the issue and the person who resolved it. An apparently tidy table is not sufficient if its cleanup cannot be explained.

Preserve uploads independently

Google stores uploaded files in a folder in the form owner's Drive. Google's file-upload documentation. Identify that folder and inventory the files the approved archive must contain. A response row containing a link does not establish that the file has been copied to your archive.

Create a manifest connecting each archived response reference to the relevant file or files, with a permitted destination and a retrieval result. Keep original filenames alongside any archive names. Similar filenames and multiple files per response are reasons to check the mapping carefully, not to guess which attachment belongs where.

Test the stored file itself from the second reviewer's authorised account. Include an older upload, a large representative file and two uploads with similar names. Confirm both the contents and the intended access boundary. Do not broaden sharing to make an inaccessible file pass.

Google says deleting form responses does not delete their attachments. Google's response limits and deletion notes. Treat those retained files as a separate inventory with an owner and retention decision; response cleanup is not evidence that file cleanup happened too.

Treat the form, Sheet and archive as separate records

The linked spreadsheet is a separate Drive file. Google says unlinking leaves its existing data but stops new responses reaching it, and later form-permission changes do not automatically update Sheet permissions. Deleting responses inside Forms cannot be undone. Google's response-destination and deletion guidance.

Review permissions on the form, linked Sheet, upload folder and archive individually. Have the backup find a response using the index, explain the question it answered and open the attachment. Also test an account that should have no access. Record the date and outcome; no account transfer or owner-departure procedure is assumed to have succeeded merely because a file is visible today.

Only the responsible owner should decide whether to clear responses after these checks. Keeping an export supports retrieval; this guide does not establish that it can rebuild Forms' original response interface. If reconstruction is required, retain the source until that separate recovery requirement has a tested solution.

After any approved change, submit dummy data through the intended active form and verify its destination and access. Preserve the archive index and collection boundary so later reports do not count the same submissions twice. Track archive storage and maintenance in the subscription audit only where they affect a real bill; no savings arise simply from downloading a CSV.