Stay organized with collectionsSave and categorize content based on your preferences.
This document gives you an overview of how Migrate to Virtual Machines handles the
deletion of your data stored in Google Cloud while migrating your virtual
machine (VM) instances using Migrate to Virtual Machines.
The deletion of your data begins when you perform one of the following actions:
Disable the Migrate to Virtual Machines API or delete your Google Cloud project:You canshut down projectsusing the Google Cloud console or theprojects.deletemethod in the API. A project must have a lifecycle state ofACTIVEto be
shut down in this way.
This method immediately marks a project to be deleted. A notification email is sent to the user who initiated the delete operation and the Technical
category contacts that are listed inEssential Contactson a best effort basis; if the notification fails to send, the project is still marked to be deleted. If there's no contact in the Technical category, the fallback contact isn't notified.
A project that is marked for deletion isn't usable. If the project
has a billing account associated with it, that association is broken and isn't
reinstated if the project delete operation is canceled. After 30 days, the
project is fully deleted. Until it is fully deleted, the project might still be
visible, although it isn't usable.
At the end of the 30-day period, the project and all of its resources
are deleted and cannot be recovered. Until it is deleted, the project counts
towards your project quota.
Delete your Google account:When a Google Account is closed, Google Cloud
may impose an internal recovery period up to 30 days, depending on past account
activity. After that grace period expires, a signal containing the deleted
billing accountuser_idis broadcasted to Google products and
Google Cloud resources tied solely to thatuser_idare marked for
deletion.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# User data deletion\n\nThis document gives you an overview of how Migrate to Virtual Machines handles the\ndeletion of your data stored in Google Cloud while migrating your virtual\nmachine (VM) instances using Migrate to Virtual Machines.\n\nThe deletion of your data begins when you perform one of the following actions:\n\n- **Disable the Migrate to Virtual Machines API or delete your Google Cloud project:**\n You can [shut down projects](/resource-manager/docs/creating-managing-projects#shutting_down_projects)\n using the Google Cloud console or the [`projects.delete`](/resource-manager/reference/rest/v3/projects/delete)\n method in the API. A project must have a lifecycle state of `ACTIVE` to be\n shut down in this way.\n\n\n This method immediately marks a project to be deleted. A notification email is sent to the user who initiated the delete operation and the Technical\n category contacts that are listed in\n [Essential Contacts](/resource-manager/docs/managing-notification-contacts) on a best effort basis; if the notification fails to send, the project is still marked to be deleted. If there's no contact in the Technical category, the fallback contact isn't notified.\n\n \u003cbr /\u003e\n\n\n A project that is marked for deletion isn't usable. If the project\n has a billing account associated with it, that association is broken and isn't\n reinstated if the project delete operation is canceled. After 30 days, the\n project is fully deleted. Until it is fully deleted, the project might still be\n visible, although it isn't usable.\n\n \u003cbr /\u003e\n\n To stop the project delete process during the 30-day period, see the\n [steps to restore a project](/resource-manager/docs/creating-managing-projects#restoring_a_project).\n | **Warning:** You can recover most resources if you restore a project within the 30-day period. Some services have delays in restoring and you might need to wait some time for services to be restored. Some resources, such as Cloud Storage or Pub/Sub resources, are deleted much sooner. These resources might not be fully recoverable even if you restore the project within the 30-day period. In some cases, projects may continue to incur charges for a period of time after shutdown. To avoid unexpected charges, [disable billing](/billing/docs/how-to/modify-project#disable_billing_for_a_project) before shutting down the project. The billing account must be manually linked again after the project is restored.\n\n At the end of the 30-day period, the project and all of its resources\n are deleted and cannot be recovered. Until it is deleted, the project counts\n towards your project quota.\n- **Delete your Google account:** When a Google Account is closed, Google Cloud\n may impose an internal recovery period up to 30 days, depending on past account\n activity. After that grace period expires, a signal containing the deleted\n billing account `user_id` is broadcasted to Google products and\n Google Cloud resources tied solely to that `user_id` are marked for\n deletion.\n\nFor an overview of the secure process that occurs when you delete your data, see\n[Data deletion on Google Cloud](/docs/security/deletion)."]]
