ARCHIVED: About administrative migrations of Google data
On this page:
Overview
If you need to migrate your Google at IU data because of changes to Google Storage, you may prefer an administrative migration, where UITS migrates your data for you rather than migrating your files yourself. If so, you can select the administrative migration option on the Google My Drive Migration form or the Google Shared Drives Migrations form.
- UITS uses the DryvIQ Admin account to migrate data administratively between Google and Microsoft storage. If you're a collaborator on a file or folder shared with you, you may receive notification when your collaborator's migration starts.
-
To view your total Google at IU usage, go to https://drive.google.com/settings/storage. Be sure you are logged into your Google at IU account, and not a personal Google account. To be sure, you could use a private browser.
Compare migration options
Comparison of the differences between self-migration and an administrative migration:
Self-service | UITS-managed moves |
---|---|
Collaborations will not migrate; you will need to recreate these in the Microsoft environment |
Collaborations will be copied to the Microsoft environment with your data |
Version history and metadata will not migrate from Google |
Version history and metadata will be copied to the Microsoft environment with your data |
You can initiate the migration at a time of your choosing (as long as you can complete it before November 21, 2022; see the timeline) |
UITS will schedule the migration of your data; you'll receive email notification both seven days and one day before your scheduled migration date |
Google My Drives: You can migrate everything at once, or choose an individual folder to migrate, and specify the destination folder in Microsoft OneDrive. It is possible to perform multiple Mover.IO migrations for additional folders. |
All data stored in your Google My Drive will be moved to
Microsoft OneDrive; if some data shouldn't be part of that migration, be sure to handle them yourself in advance (deleting data you don't need, and/or manually moving data to an appropriate location)
|
Google Shared Drives: Files must be manually migrated; Mover.IO cannot migrate this data. |
All data stored in your Google Shared Drives will be moved to Microsoft Teams; if some data shouldn't be part of that migration, be sure to handle them yourself in advance (deleting data you don't need, and/or manually moving data to an appropriate location)
|
Before and during your administrative migration
Prepare for your migration
If you have active collaborators editing files in your Google Drive, make sure to notify them when they need to pause. This will ensure no data is lost.
On the day of your move:
- Do not edit or create new content in your Google Drive.
- Files should begin appearing in your Microsoft OneDrive in a parent folder named FromGoogle.
- To ensure that the move is successful, avoid editing files or folders in that space while your job is underway.
The migration process can take several hours or up to a few weeks, depending on size. During the migration, continue to refrain from working in your Google Drive.
If you need to access your files
To ensure a successful migration, you should avoid editing files or folders in your Google Drive while your job is underway. However, if your migration is taking a long time and you need to access data:
- Copy any needed files to a location other than your Google Drive.
- If you have Google Drive for desktop installed in Windows or MacOS, from that device, open your Google Drive settings and select . This will prevent changes to documents from being uploaded to your Google Drive.
This is document bhwa in the Knowledge Base.
Last modified on 2023-01-10 17:24:13.