How to export data from Google Forms before the account closes
Responses, the linked Google Sheet and uploaded files can all leave Google, but each one follows a different path, so the work is to confirm each path in Google's current help pages before deleting anything. Responses are the form's own data, the Sheet is a separate spreadsheet that Google keeps in sync, and uploads are files stored in the form owner's Google Drive. Treating them as one export is the most common reason a migration loses something. No Google export limits, file formats or sorting behavior were verified for this page, so check each of them against Google's documentation and against your own forms before you rely on them.
Start with an inventory of each form. Record the owner account, every collaborator with edit or view rights on the form and on the linked Sheet, and whether any file-upload questions exist. Then test a download on a large form, because the CSV you get may not come back in timestamp order, and you should confirm that the row count matches the response count shown in the Responses tab. Check who can see the linked Sheet, since sharing settings on a spreadsheet are separate from the form, and remove anyone who should not keep access before the export. For file uploads, identify the Drive folder that holds them and confirm that the files are owned by the account you plan to close, not only visible to it.
Which Google Forms data you can export, and how
This table lists the four kinds of material in a Google Form that you need to get out: responses, the linked Sheet, uploaded files and the form structure. Each row names the export method to confirm, the output you should expect and the limit to check in Google's own documentation. The main takeaway is that responses, Sheet data and Drive files are exported by different routes, so plan each one separately before the account closes.
| Data | Export method to confirm | Output format | Limits and what to confirm |
|---|---|---|---|
| Form responses | Responses tab, then the download option for CSV | CSV, one row per submission | Confirm current download limits and whether sorting by timestamp is needed on large forms |
| Linked Google Sheet | Open the Sheet and export or download it as a file | Spreadsheet file, may include formulas and added tabs | Check who has edit or view access to the Sheet, and whether it is still updated by the form |
| Uploaded files in Drive | Drive download for folders, or Google Takeout for bulk export | Original files in folders, with Takeout archive format options | Confirm file size and count limits for Takeout in Google's documentation, and who owns the Drive folder |
| Form structure | Record questions, sections, logic and settings manually or by copying the form | Notes or a copied form, no native structure export | Logic and response validation rules may not transfer, so document them and confirm against Google's help pages |
What does not come out of Google Forms in one click
A CSV download covers the answers, but several parts of a Google Form sit outside the response sheet. Logic, layout, file links, timing details and attached scripts each need a separate step during export, and each one is easy to miss before the account closes.
Question logic and section branching
Go-to-section rules and response validation live in the form definition, not in the exported responses. A CSV shows which answers were given, but not which path the respondent was sent down. Record each branch rule on paper or in a spreadsheet before you export, then rebuild it in the target tool and test each path with sample answers. Confirm the current branching options in Google's Forms help before you rely on the list.
Visual layout and theme
Themes, header images, colors, fonts and section ordering are not part of the response data. Take full-page screenshots of every section and note the order of questions, descriptions and required markers. Your rebuilt survey will look different, so keep the screenshots as a reference for reviewers and for anyone checking that the same wording reached respondents.
Uploaded files without a clear row link
Each file upload is stored in the owner's Drive folder for that form, and the response sheet usually holds only a link to the file. Files from different respondents can share similar names, and a link can break if the file is moved or deleted. Ask the form owner to export the Drive folder with the response timestamp and a respondent identifier field, then match each file to its row before you move anything.
Timestamps and edit history on large forms
The response CSV is not always sorted by submission time on large forms, so a naive import can change the order of answers. Edit history is also not part of the standard export. Sort the export by the timestamp column, keep a copy of the raw file, and record the export date and the account that performed it. Ask Google's documentation which timestamps and revision details are available for your form type.
Apps Script and add-on connections
Scripts, add-ons and linked Sheet triggers can send responses to other systems and keep running after you stop using the form. Open the script editor and the Add-ons menu for the form, list every trigger and connected service, and note who created them. Disable them before the account closes, and confirm with Google's Apps Script documentation how triggers and linked resources behave when an account is removed.
Export sequence for data from Google Forms, step by step
This sequence gives you a complete, checked copy of every Google Form's responses, linked spreadsheets, uploaded files and structure, stored in a location your organization controls before any account is closed. Each step ends with a comparison against the source so sign-off rests on evidence rather than assumption.
Inventory every form and its owner
Ask each Google Workspace administrator and form owner to list every form they created or co-own, including forms in shared drives and forms owned by people who have left the organization. Record the form title, form link, owner, linked Sheet name, the Drive folder holding any uploads, and the approximate response count shown in the Responses tab. The output is a single register that your records or IT team signs off, because any form missing from it will not be exported. Check the register against an admin search of Drive for files of the Google Forms type to confirm nothing was left out.
Freeze edits and record response counts
Before exporting, agree a cut-off with form owners and turn off responses in each form, or announce a closing time after which no new submissions will be accepted. Note the response count in the Responses tab and the row count in the linked Sheet for each form, and record the time of the cut-off in the register. Confirm the counts match in both places, and have the form owner sign off that the freeze is in effect. Any response that arrives after this point must be captured in a second, dated export.
Download the response CSV and check sorting
In each form's Responses tab, download the responses as a CSV file. On large forms, do not assume the rows are in timestamp order, because the export may not sort them consistently, so sort the file yourself on the Timestamp column and keep the original as received. Compare the number of data rows, excluding the header, with the count recorded in step two. The check is complete when the row counts match and the first and last timestamps fall within the period the form was open. The records lead or form owner signs off on each file.
Export the linked Sheet and version history
Open the spreadsheet linked to each form and download it as an Excel or CSV file, and separately save its version history so you can show how the data changed over time. Confirm that the Sheet still holds the same responses as the form, since a Sheet can contain manual edits, added columns or deleted rows that do not appear in the Responses tab. Note who has edit and view access to the Sheet, because that list is part of the access record you will need before the account closes. The owner of the Sheet signs off that the copy matches the source.
Download uploaded files from Drive
For every question that accepted file uploads, locate the Drive folder Google Forms created and download its contents with the folder structure intact. Compare the number of files and the total of their sizes against the count of file upload answers in the response export, noting that a single respondent may have uploaded several files. Record any file that cannot be downloaded, such as one restricted by a sharing setting, and resolve it with the owner before sign-off. The records lead confirms that the file count and the response references match before the Drive copy is treated as complete.
Record the form structure
For each form, capture the questions, question types, required flags, sections, branching rules, validation settings and the confirmation message, either by screenshot or by a written list kept with the export. Compare the number of questions in the record with the number of answer columns in the CSV to confirm the structure matches the data. This record is what you will rebuild from when you create replacement surveys, so it must be complete before sign-off. The form owner confirms the record is accurate.
Store the exports in an organization-controlled location
Move the responses, Sheets, uploaded files, structure records and the access list into a storage location that your organization administers, such as a file server or self-hosted storage you run. Keep the folder names aligned with the register, and set access so only named staff can read the archive. Compare the stored file counts and checksums against the originals, and confirm that the access list has been reviewed and that the Google account retention plan is documented. The data protection or records owner signs off once the archive is complete and verified.
Who runs the export: form owner, Workspace admin or both
If you created the form from a personal Google account, you can reach the responses, the linked Google Sheet and the Drive folder that holds respondent uploads, as long as that account stays active. No administrator action is needed for this path.
- Responses view: Download responses as CSV from the form's Responses page. On large forms, check the row order yourself, because the download is not guaranteed to be sorted by timestamp.
- Linked Sheet: Open the spreadsheet linked to the form and review its sharing settings, including editors and any link sharing, before you export.
- Upload folder: Locate the Drive folder that holds files submitted through file upload questions, then confirm that every file is present and downloadable.
- Collaborators: List everyone with edit or view access to the form and the Sheet, so you know who has already seen or copied the data.
Before the account is closed or its owner leaves, record your export list and confirm that the CSV, the Sheet and the upload folder are all saved outside the account.
When a form belongs to someone who has left the organization, you may not be able to reach its data through the owner's account. Your options depend on whether that account is active, suspended or deleted, and on the ownership and retention settings your Workspace uses. Confirm the current steps in Google's Workspace administrator documentation before you act, because the exact behavior can differ by edition and configuration.
- Account state: Determine whether the user account is active, suspended or deleted, since each state changes what you can reach and how.
- Ownership transfer: Confirm in Google's documentation whether Drive files owned by the departed user can be transferred to another user, and whether form responses and linked Sheets move with them.
- Retention window: Confirm how long data from a deleted user account can be restored, and check whether that window is still open.
- Audit trail: Review the admin audit logs available in your edition to see who accessed or shared the form and the Sheet, and confirm which log types you can search.
- Holds and policies: If the records fall under a retention rule or hold your organization applies, involve legal or records staff before you transfer or delete anything.
Get written confirmation from the people who run your admin console about the exact steps, owners and dates before any account is changed.
When a form is created inside a shared drive, the drive, not one person, is the main owner. Access to the form, its Sheet and its uploads then follows drive membership and roles. Confirm in Google's shared drive documentation which roles can export responses, manage files and remove content, and whether a member's departure changes access to forms they created.
- Membership and roles: List every member and their role, since these settings govern who can open the form, the Sheet and the upload folder.
- Creator departure: Confirm whether the form and its linked files remain in the shared drive after the person who created them leaves.
- Separate Sheet permissions: The linked Sheet may have been created or moved outside the shared drive, so check its sharing on its own.
- Upload location: Find where the upload folder lives and whether anyone outside the shared drive can reach it.
- Named export owner: Assign one person to run the export and store the download in a controlled location that the team can audit.
Ask the drive's owners to confirm in writing who will hold the responses, uploads and Sheet after the migration, and who can still see them.
Checks to run before you export data from Google Forms and delete anything
A CSV can look complete and still be wrong. On large forms, the download is not guaranteed to come out sorted by timestamp, so the row order you see in a spreadsheet is not a reliable basis for comparison. Before you compare anything, sort the export by the Timestamp column or by a response identifier you can trust, then confirm that the first and last rows match the first and last responses shown in the Google Forms Responses tab. Only after the order is fixed should you compare individual records. Without this step, two exports of the same form can appear to differ when they only differ in sequence, and a missing row can hide in a block of shuffled entries.
Next, reconcile counts. Record the number of responses shown in the Responses tab at the moment of export, the number of data rows in the CSV (excluding the header), and the row count in the linked Google Sheet if one exists. Compute a checksum over a fixed column set, such as a hash of the timestamp and a few required answers, and repeat the calculation on the exported file. Then check the uploaded files. Google Forms stores them in the owner's Drive, so pick a sample that includes the oldest, the newest and several in between, download them, open each one, and confirm the file type and approximate size match the respondent's upload. Opening a sample is a spot check, not proof, so treat any mismatch as a reason to widen the sample before continuing.
Keep a dated record of who ran each step, what file was used, the counts and checksum values, and the names of the people who reviewed them. Store that log outside the Google account you are about to close. Then stop. No deletion of responses, linked Sheets, or Drive files should happen until a second person, working from the log and not from memory, has independently confirmed the counts and the sample results. If the two counts disagree, the export is not finished, and the form must stay in place until the difference is explained.
What to plan before the Google account or Workspace contract ends
Closing a Google account or Workspace subscription removes access to forms, linked Sheets and Drive files on a timeline you need to confirm with Google. The cards below cover the items to settle before that date, in the order most teams find them useful.
Confirm the end date and grace period
Find out the exact date access stops and whether Google keeps data for a grace period after a Workspace subscription ends or an account is deleted. Ask the Workspace administrator for the billing end date, and check the Google Workspace help pages or your Google account representative for the deletion and recovery window. Record the date in the migration plan, because the export work below has to finish before it.
Transfer ownership of forms and folders
Forms, linked Sheets and Drive folders are owned by the account that created them, so removing that account can take the responses with it. Move ownership of each form and folder to a retained account, or export them first. Build an inventory that lists each form owner, its linked Sheet and the Drive folder that holds uploads, so nothing is missed.
Review access on linked Sheets and folders
Each linked Sheet and upload folder may be shared with colleagues, external contractors or groups, and those people may see respondent data after the export. List every editor and viewer, remove access that is no longer needed, and confirm that link-sharing is turned off for anything containing personal data. Keep a record of the changes for your access review.
Revoke third-party add-on access
Google Forms add-ons and connected services such as spreadsheet add-ons, automation tools and notification apps hold their own OAuth grants to your Google account. Review the connected apps in the account security settings and remove grants you do not need. Confirm with each vendor whether they hold copies of responses, because revoking access does not delete data they already stored.
Decide retention for responses and files
Set a retention rule for each dataset before export, covering how long responses, Sheets and uploaded files are kept on your own servers and when they are deleted. Your legal, HR or records team usually owns this decision, and it should match the retention schedule already in place for similar records. Write the decision down, because the export format will keep whatever you choose to import.
Notify respondents where personal data is involved
If forms collected names, contact details, health information or identity documents, respondents may need notice that the data is moving to a new system and that their records will be kept or deleted under a stated rule. Involve your privacy or data protection lead to decide whether notice is required and what it must say. Confirm the wording with counsel before sending it.
Questions teams ask before they export data from Google Forms
How much effort does exporting data from Google Forms take?
The effort depends mostly on how many forms you have, how many responses each one holds, how many file upload questions they contain, and how complex the branching logic is. A single short form with a few hundred plain-text responses is a small job, because the CSV download covers it directly. Many forms with file uploads, nested sections and logic need more care, since each uploaded file lives in the owner's Drive and must be matched back to its response. Inventory the forms first, then group them by these drivers so you can estimate the work before you commit to a plan.
Can one person export Google Forms data without outside help?
Often yes for a small set of forms, because Google Forms offers a CSV download and the linked Sheet can be opened and copied by anyone with the right access. The harder parts are retrieving uploaded files from Drive, confirming the export is complete, and deciding what to keep. A single person usually needs the form owner's account or a Workspace administrator to reach files that belong to someone else. If forms are owned by many people or by people who have left, the work becomes a coordination task rather than a technical one, and outside help is worth considering. DeployOpen can plan, script and verify an export in your environment under a written scope.
What does the export need from our organization?
The export needs named form owners who can sign off on each form, a Google Workspace administrator who can confirm ownership transfers and Drive access, and a decided storage location for the exported data and files. You also need an approver who accepts that the export is complete before the source account is changed. Record where responses and uploads will live, who can read them, and how long they will be kept. Involving the privacy or records owner early avoids moving personal data to a location nobody has approved.
What makes a Google Forms export take longer?
The main drivers are the number of forms, the volume of responses, the number of uploaded files, and how many people must review the results. Large forms with thousands of rows need extra checks on sorting and column mapping. Uploads add time because each file must be located, downloaded and linked to the right response. Access problems add time too, for example when a form owner has left the organization or files were shared with a personal account. Ask for a plan that lists these drivers for each form rather than a single overall number.
Are the linked Google Sheet and the CSV download the same data?
They usually hold the same responses, but they are not guaranteed to match in every detail. The linked Sheet is a live spreadsheet that keeps updating as new responses arrive, and it can be edited, so a column may be renamed, reordered or overwritten by someone with edit access. The CSV download is a snapshot taken at the moment you request it, and on large forms its rows are not sorted by timestamp, so you must sort them yourself. Compare row counts and a sample of entries between the two before you treat either one as the record.
What should we do with uploads from respondents without a Google account?
Respondents without a Google account can usually be asked for files only when the form allows it, and the files are stored in the form owner's Drive. Export these uploads with their response IDs so each file stays linked to its submission, and record who can access the folder. Confirm that no file is shared publicly before you move it. For future collection, a self-hosted form tool that accepts file uploads without a Google sign-in can avoid this dependency, but you should confirm its file size limits, storage location and retention settings in your own environment before relying on it.
What should we ask for in a quote for this export?
Ask for a written scope that lists every form, its response count, its file upload questions and its owner. Ask who performs each step, including inventory, export, file retrieval, checksum or count verification, and handover. Request the deliverables in writing, such as the exported files, a reconciliation report and a record of access changes. Confirm what happens if an owner is unavailable, how changes to scope are priced, and whether ongoing support is included. DeployOpen does not publish a price list, and a quote follows from the written scope.
How do we confirm access is removed before the Google account closes?
Before closing the account, list every form, Sheet and Drive folder that holds responses or uploads, and confirm who has access to each one. Transfer ownership or copy the data to the new location, then check sharing settings, linked Sheets, connected apps and any scripts that read the responses. Remove access for former staff and external collaborators, and record the date of each change. Keep a log of this review so the security or compliance team can show that access was checked before the account was retired.
How DeployOpen scopes and delivers a Google Forms data exit
DeployOpen approaches a Google Forms data exit as a fixed-scope engagement inside your own infrastructure. We start by inventorying which forms, linked Sheets, uploaded files and sharing settings matter to your organization, then agree deliverables in writing before any export work begins.
How we scope
- Inventory every form, linked Google Sheet, Drive folder and collaborator who can see responses today
- Agree in writing which exports, file transfers and access checks are in scope for your Google Forms data
- Confirm the target platform, hosting location and retention rules before any export work starts
How we build
- Set up the self-hosted target environment in your own cloud account, data center or air-gapped network
- Build repeatable export scripts that sort responses by timestamp and preserve question labels and file links
- Test exported responses and files against the originals before any source data is removed
How we hand over
- Deliver a written record of every export run, row count check and file transfer with its outcome
- Document the access review of Sheets, Drive folders and forms so you can confirm nothing remains exposed
- Hand over runbooks so your own staff can repeat the exit or verify it during an audit
How we support
- Offer ongoing support, upgrades and continuous testing of the target platform as a retainer
- Keep backups and restore tests of migrated responses and files under the agreed scope
- Provide follow-up support for questions raised by compliance assessors or your own auditors
