Home › Transfer Google Form to Another Account

Transfer a Google Form to Another Account (2 Real Methods, Honestly Compared)

Updated November 12, 2026 · ~10 min read

People searching "transfer google form to another account" usually want the same form, its link and all its responses to keep working after a colleague leaves, a school account is closed, or a project changes hands. Google does support this — but only in a narrow set of conditions. This guide gives the native ownership-transfer path first (it is free and lossless when it works), then the two-step export/import bridge for the cases where Google refuses. It also states plainly what the bridge cannot carry.

Decide first: Same Workspace domain and the destination can accept ownership? Use Drive ownership transfer — free, instant, keeps responses and the original link. Different domain, personal Gmail, or the transfer is blocked? Use the export → import bridge, which rebuilds the questions in a new form under the destination account.

What 'transfer to another account' actually means

There are two different things people mean, and they need different methods:

Autocomplete around this topic is dominated by `can i transfer google form to another account`, `transfer google form ownership to another user`, `outside organization`, `to another domain` — i.e. most searchers are trying object transfer and hitting a wall. Being honest about which one you need saves an afternoon.

Method 1 — native Drive ownership transfer (free, lossless)

  1. Open Google Drive, find the Form file (Forms live in Drive).
  2. Right-click → Share → Transfer ownership (or Share → add the person as Editor, then use the ownership dropdown).
  3. Enter the destination address, confirm, and send the ownership invitation. The new owner must accept.

Requirements and limits: both accounts usually need to be in the same Workspace organisation; admins can restrict transfers to external domains; a personal Gmail account often cannot receive ownership of an organisation-owned file. When it works, this is strictly better than any conversion — nothing is rebuilt.

If you only need a copy rather than a transfer, see Copy Google Form to Another Account. If you are moving many forms at once, see Move Google Forms Between Accounts.

Method 2 — two-step export / import bridge

The two-step migration bridge. ExamParser has two halves: Google Form to Word reads a form share link and writes the questions, options and answer key into an editable .docx; then the document-to-Google-Form importer accepts that .docx and builds a new Google Form under the account you sign in with. Sign in as the destination account before importing and the new form belongs to it. That is a genuine cross-account content migration — but it migrates the question structure, not the original form object.

Step 1 (export). Copy the source form's share link, open the Google Form to Word exporter, choose Word (.docx), and download the document. It contains one block per question: number, stem, options and the correct answer, with no AI rewriting.

Step 2 (import). Sign in as the destination account first — the importer creates the form under whichever account is signed in. Open the document-to-Google-Form importer, upload the .docx, choose Google Form as the destination, and the questions become a new form that the destination account owns, edits and shares.

Because the .docx is editable, you can also clean up wording, drop stale questions or split sections between the two steps — something ownership transfer cannot do.

What does and does not move

What the two-step bridge movesWhat it does NOT move
Question text, order and typeHistorical responses / submissions
Options A–EThe original form URL (a new link is generated)
Correct answer / answer keyEditors, collaborators and sharing permissions
Marks and images where supportedThe linked response spreadsheet and its formulas
—Publish state, theme, confirmation message, response validation settings

Transfer a Google Form to another account in 6 steps

Runnable check: verify the question structure before and after

After importing, confirm nothing was lost. This Apps Script reads a form and writes a checksum-style inventory you can compare with the source form (run it against both and diff the two sheets).

function inventoryForm() {
  const form = FormApp.getActiveForm();
  const items = form.getItems();
  const out = [["Index","Type","Title","Choices"]];
  items.forEach(function (it, idx) {
    const t = it.getType();
    let choices = "";
    if (t === FormApp.ItemType.MULTIPLE_CHOICE) {
      choices = it.asMultipleChoiceItem().getChoices()
        .map(function (c) { return c.getValue(); }).join(" | ");
    } else if (t === FormApp.ItemType.CHECKBOX) {
      choices = it.asCheckboxItem().getChoices()
        .map(function (c) { return c.getValue(); }).join(" | ");
    }
    out.push([idx + 1, String(t), it.getTitle(), choices]);
  });
  const ss = SpreadsheetApp.create("form-inventory-" + form.getId());
  ss.getSheets()[0].getRange(1, 1, out.length, out[0].length).setValues(out);
  Logger.log(ss.getUrl());
}

Note: getItems() works on a form-bound script. Only MCQ/checkbox item types expose getChoices(); the guard above avoids calling it on text items. Compare the Title and Choices columns between source and destination — that is where a lost option or reworded stem shows up first.

Troubleshooting

1

Try native transfer first

Drive → Share → Transfer ownership; destination accepts.

2

If blocked, export the structure

Form share link → Word (.docx) with questions, options and answer key.

3

Optionally edit the .docx

Remove stale questions, fix wording, split sections.

4

Sign in as the destination account

The importer creates the form under the signed-in account.

5

Import the .docx

Choose Google Form as destination; a new form is created.

6

Verify and re-share

Check quiz mode, answer key, images; distribute the NEW form link.

Frequently asked questions

Can I transfer a Google Form to another account?

Yes, in two different senses. Inside the same Workspace domain, Drive's Transfer ownership moves the exact same file — responses, link and settings included — and is free. Across domains or to a personal Gmail account that usually fails; the workable fallback is to export the questions to a .docx and import them into a new form under the destination account.

How do I transfer Google Form ownership to another user?

In Google Drive, right-click the form file, choose Share > Transfer ownership, enter the new owner's address and confirm; they must accept the invitation. Workspace admins can block transfers outside the organisation, which is the most common reason the option is missing.

Can I transfer ownership of a Google Form outside my organization?

Usually not through Drive — administrators commonly restrict external ownership transfers. A reliable alternative is the two-step bridge: export the form's questions to a Word .docx, sign in with the destination account, and import that .docx to build a new form the destination account owns.

Does exporting and re-importing keep my responses?

No. The .docx carries the question structure — stems, options, answer key and marks — not submissions. Export responses to Sheets or CSV separately before closing the source account, and expect a new form URL.

Why does the imported form have a different link?

Because step 2 creates a brand new form rather than moving the Drive file. Update any shared links, QR codes, LMS assignments and embeds to point at the new URL.

Google Form exporters (step 1)

Step 1 of a migration is getting the question structure out of the source form. ExamParser has a dedicated exporter for each format; the Word (.docx) one is the practical bridge because the importer accepts .docx directly.

Related guides

Start the migration with a clean export

Try native ownership transfer first — it is free and lossless when your domain allows it. When it is blocked, export the question structure to an editable .docx, then import it into a new form under the destination account. Deterministic, no AI rewriting.

Export my Google Form to Word →