> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/move-file.md). # Move file You can move files from a shared drive to another shared drive, or to the integration admin's My Drive. This action can be done in bulk, for up to 100,000 files. There are several use cases that require moving large numbers of files from a Google shared drive: * **Data retention policy** - To address compliance requirements, you can archive unviewed Google files in a dedicated drive instead of deleting them immediately. This process can be conducted [on-demand](#move-files-in-bulk), or as a [scheduled workflow](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/remediate/google-drive-remediation.md#move-file). * **Organizational change** - Reorganizing teams or departments might require moving files to align with the new organizational structure. This can also happen as a result of mergers and acquisitions. * **Compliance needs** - To meet regulatory or auditing demands, data is often segregated by ethical walls: sensitive data is isolated from general company information. Rapidly changing the file structure in Google shared drive helps to efficiently address compliance policies. * **Operational requirements** - When migrating from legacy systems or personal drives, it's usually required to move large volumes of files to ensure that business-critical data is centrally managed and accessible to the relevant stakeholders. {% hint style="info" %} * Only **files** from a shared drive can be moved, not folders. * If you want to move files from a My Drive to another My Drive, use the [Change owner](#change-owner) action. {% endhint %} ### Prerequisites For this action to succeed, make sure these conditions are fulfilled: * The integration admin's user email has direct access (not in a group) to both the **origin** and **destination** folders. * The integration admin's **email** is the same email assigned to the admin user in the integration wizard. To find out what this email is, go to **Integrations > Google Workspace > Settings > Edit**. ### Sharing impact Moving files might change ownership and permissions, so we recommend that you plan migrations to avoid accidental data exposure or loss of access: * Files will gain permissions of the destination folder. * All collaborators who were not given direct access permissions, but inherited permissions from the origin folder, will be removed. * Follow best practices to minimize disruption and maintain data integrity ### Move files in bulk To comply with a data retention policy, you can manually select your inactive Google files and move them to a dedicated archive folder before deletion. You can move files in bulk for up to 100,000 files in Google shared drives, to another shared drive or to the admin user's My Drive. 1. Navigate to **Inventory > Assets** > **Google Drive**. 2. From all assets, filter by **Drive type** includes **Shared drive**. 3. Apply other relevant filters, such as **Shared drive name** or **Google label**.

4. Select the assets you want to remediate. 5. Click the **Move file** remediation action:

6. If you want to run an assessment report first to see how many assets will be remediated, select [Assess and remediate](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/assess-and-remediate.md). Otherwise, select **Just remediate.**

7. The assessment summary indicates how many files are valid and can be moved to another location, as well as the number of the invalid files that cannot be moved. 8. Click **Download report** to view full details about files, their origin folders, and access permissions.

9. Select the relevant workflow to run. 10. Enter the **destination folder ID**. To retrieve the folder ID, open the destination drive folder and copy the URL suffix after `folders/` 11. Click **Validate**

to check the folder ID is valid, and confirm that the admin user has **direct** permission to access the destination folder. 12. If the folder ID is validated, you'll see a green checkmark

13. Click **Remediate**.\ DoControl moves all selected assets to the specified destination folder. ## Troubleshooting If the Move action does not succeed, verify that you have fulfilled all the prerequisites. ### Destination folder not found There are several possible reasons the destination folder might not be found: * The ID might be incorrect * The destination folder might not be synced yet with DoControl * The destination folder might no longer exist ### Integration admin doesn't have required permissions To verify that the admin user has the necessary permissions to both the origin and destination folders, inspect your Google Drive permissions: 1. In Google Drive, go to the **origin** folder, and verify that the integration admin has direct access permission (not in a group). 2. In Google Drive, go to the **destination** folder, and verify that the integration admin has direct access permission (not in a group). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docontrol.io/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/move-file.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.