Google Drive to OneDrive Migration Guide (Migrate Versions and Metadata)

This article outlines the complete task flow for migrating folders and documents from Google Drive to OneDrive for Business, including versions and metadata.

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully before continuing.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 

We are not able to support migrations with two-factor or multifactor authentication. 

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type.

Important

Due to a limitation of Google API, MigrationWiz will not export and migrate any Google Files belonging to a suspended user. The migration will not fail, but the skipped items will be shown as part of the error.

Which items are migrated
  • Files.
  • Folders.
  • Permissions.
  • Versions (up to 25).
  • Google Forms - migrated as a zip file containing the form as HTML and the responses as a CSV. Versions are not supported.
  • Metadata.

    • File/Folder name.

    • Modified date. (*)

    • Modified by.(*)

    • Created date.(*)

    • The description is migrated to the ‘Title' column at the destination. Migrated value is limited to the existing character limit of the 'Title’ field.

    • ‘Creator’ metadata is migrated but in some cases, this value may not be accurate. This is a current limitation without a workaround.

    • Migrations of over 60GB are now supported, but this must be set up in Advanced Options. These settings will prevent timeout errors when an import takes more than 10 minutes to complete.

      • Set LargeFileMigrations=1

      • Set LargeFileMigrationsTimeout=7200000

        • 7200000 value is an example; time is measured in milliseconds

(*)The migration of these items depends on the modified date of the most recent version that was migrated.

Which items are not migrated?
  • For some Google proprietary format files (e.g. Docs, Sheets, Slides), Google allows you to provide a custom name for a version of the file. Such version names are not migrated.GD1.png

  • Minor revisions available for Google proprietary format files are not migrated.

  • Embedded video/hyperlinks in Google Docs, sheets, or slides may not be migrated accurately when these Google proprietary files are converted to Microsoft 365 format.

  • .TMP files are not supported.

  • Links giving access/Link sharing.

  • Google Drive's Shortcuts.
Which is the migration mapping?

In the following table, you can find support for Google Proprietary file types.

File Format in Google Drive (My Drive)

Remarks

Documents

Migrated as MS Word document.

Spreadsheets

Migrated as MS Excel.

Presentations

Migrated as MS PowerPoint.

Drawings

Migrated as JPEG.

Limitation
Versions are downloaded but all of them have the same content.

Apps Scripts

Migrated as JSON.

Jam board

Migrated as PDF.

Limitation
Versions not supported.

Forms

Migrated as a zip file containing the form as HTML and the responses as a CSV.

Limitation
Versions not supported.

Site

Not migrated.

Owner

None.

OneDrive migrations

Consider the following behaviors and tips for OneDrive migrations.

  • OneDrive data may not be accessible for a few days after migration, due to OneDrive's crawling and indexing process. We suggest having your users log in immediately after migration but warn them that their data may not be available immediately. For this reason, it may be best to complete the migration on a Friday so the indexing can happen over the weekend.
  • If you are migrating to a Microsoft 365 Small Business Tenant account, the processes will be very similar to the above. However, you will not be able to use admin credentials for your Destination endpoint and will instead be using end-user credentials.
  • The destination endpoint must be OneDrive for Business (with Versions and Metadata) for this migration. The User’s personal site provisioning is supported only with this endpoint.
  • Due to versioning, storage usage in OneDrive may be increased when migrating with permissions.
  • Changing the domain after the migration process will not automatically update the previously migrated destination file. Once data is migrated from one domain to another, any subsequent changes or modifications made to the source data or the domain will not automatically reflect in the destination file.

Prepare the Source

The Google Drive (Own Service Account) connector launched in 2020 and requires the set up of a Google Service account. This significantly reduces the likelihood of the migration being throttled. This is the option we recommend for all Google Drive migrations. Follow the steps below under OAuth2 Requirements for Google Drive (Own Service Account) to set up your environment for this endpoint.

All accounts being migrated must be in Active status in the tenant. Users that are set to a status of Inactive will not be able to fully migrate and will fail in the project.

OAuth2 Requirements for Google Drive (Own Service Account)

Prerequisites

  • Subscription to Google Cloud Platform.
  • Google Super Administrator account.
  • Ability to set up a service account on the G Suite tenant.
  • A Google service account must be set up before the MigrationWiz project is created.

Create a Google Project

  1. Go to the Google Cloud Platform (GCP) Console and sign in as a super administrator. Choose one of the options below:
    • If you haven't used the Google Cloud Platform Console before, agree to the Terms of Service and click Create Project.
    • If you have used Google Cloud Platform Console before, at the top of the screen next to your most recent project name, click Down to open your projects list. Then, click New Project.
  2. Enter a project name and click Create.
  3. When the new project creation completes, at the top of the screen next to the current project name, click the Down icon and select the newly created project name from the list.

If you are not able to create a project here, it may be that the ability to create projects has been disabled for your tenant. To check this, navigate to the Google Admin Center click on Apps > Additional Google Services, and select the Google Cloud Platform. Once there, you should see a setting that can be toggled to allow users to create projects.

Enable APIs for Service Account

  1. From the Google Cloud Platform Console, click Menu > APIs & Services > Library.
  2. Enable the following APIs by selecting the specific API and clicking Enable.
    Repeat for each API listed below:
    • Google Drive API
    • Admin SDK

Make sure that the respective services are enabled within the Google tenant. You can control services for your users using the instructions on this page: Control who can access G Suite and Google Services.

Create a Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.
  2. Click + Create Service Account at the top middle of the screen and enter a name.
  3. Click Create.
  4. Assign the role of Owner to the new Service Account by selecting Owner from the Role drop-down menu.
  5. Click Continue to move to the next step, then click the Done 
  6. You will now be returned to the "Service Accounts" page. 
  7. On the ‘Service accounts' page, click the vertical ellipsis under the 'Actions’ column for the service account created above.
  8. Click the Create key.
    1. Make sure that JSON is selected as "Key Type."
  9. Click Create.
  10. Click Close.

Download the key as a JSON file and make a note of the name and location of the file. This JSON file will be used when setting up the migration endpoint in the migration project.

Important

The JSON file must contain information in the following fields: “type”, “private key”, and “client email”. If these mandatory fields are empty the file upload during endpoint creation will fail.

Setting the Scopes for the Migration

  1. From the Google Cloud Platform Console:

      1. Click Menu.
      2. Click IAM & Admin.
      3. Click Service Accounts.
      4. Find the service account that was set up in Step 3: Create a Customer Tenant Account.
      5. Find and copy the service account's Unique ID number. This is the Client ID number that will be used in a later step.
        • This field often needs to be added to the view. Click on the Column display options button and add a checkmark to Unique ID, then click OK.
        • This Client ID should be considered similar to Administrator account passwords and handled securely.
      6. You will now have one of two options, depending on if the Google UI has been updated in your tenant.

      Old Google Tenant UI

      1. Go to the G Suite admin page at google.com.
      2. Click Security.
      3. Click Advanced Settings.
      4. Click Manage API Client Access.

      OR If your account shows the latest UI updates from Google, as shown below:New_Google_Admin_APP_Access_Control.JPG

      1. Go to the G Suite admin page at google.com.
      2. Click Security.
      3. Click Advanced Settings.
      4. Under ‘Domain-wide delegation’, click Manage domain-wide delegation.
      5. On the Manage domain-wide delegation page, click Add new.

 Once these steps are complete, follow these last steps:

  1. In the Client ID field, paste the Unique ID copied above.
  2. In the OAuth scopes (comma-delimited) field, paste all scopes listed below:
  3. For source endpoint:
    https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive.readonly
  4. Click Authorize.

 You should now see your specific Unique ID and the associate scopes listed.

Export mailboxes to CSV file(s)

From the Google Admin portal:

  1. Click Users.
  2. Click ⁝ (3 vertical dots).
  3. Download Users.
  4. Download All Users.
  5. Click OK.
  6. Save.

Preparing the Destination

Administrator Permission Options

The two options listed below apply to both the source and/or destination endpoints when they are for OneDrive or SharePoint Online.
  • Both options require a Global Administrator for the configuration steps.
  • Of the two options available, the most recommended is the App-Based Authentication, as it is more secure and incurs less throttling during the migration. This option also has the benefit of not requiring the account being used to migrate the data to have any administrator roles assigned to it.
App-Based Authentication Delegated Authentication

BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Microsoft 365 Groups (Documents), and Teams migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Microsoft 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Microsoft 365 tenants. Using this option, including steps for uninstalling, can be found outlined here: App-based authentication using Application Permissions for SharePoint and OneDrive Migrations

Full-Control vs Read-Only

Why does the source require consent to a Full-Control application permission?

All AMR migrations require full-control permission. If you have a specific need to not allow full-control permissions, you can use MigrationWiz-SharePoint-ReadOnly (only for the source). However, please note that with read-only permissions, MigrationWiz will not export document permissions, versioning, or metadata, and cannot use AMR. Additionally, OneNote files will be migrated, but will not contain content, due to a lack of permissions when preparing the files to migrate.

Steps for enabling app-based authentication permissions

  1. Ensure you are signed in as a Global Admin.
  2. Go to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted. Once you click on Accept, you will be redirected to the BitTitan login page. This is normal and the page can be closed.

  3. Create a new security group named MigrationWiz in the Office 365 Admin Portal. (The name of the security group must be an exact match)

  4. Create a new user that is not having data migrated in the project. This account does not require any administrator roles to be assigned. (If you already have an existing user, that should be fine)

  5. Add the new (or existing) user to the previously created security group as a Member (Adding as an Owner will not work here).

  6. Create MigrationWiz project.

  7. When creating the source and destination endpoints, enter the user credentials for the user in step 4 that corresponds with the endpoint the user belongs.

  8. Add the support option UseApplicationPermission=1 to the advanced options of the MigrationWiz project under Support Options.
  • Users being migrated need to be licensed to use OneDrive in the destination tenant
  • Users being migrated must not be blocked from signing into the destination tenant
  • Destination OneDrives must not be set to read-only
  • If electing to use Delegated Authentication (outlined under Administrator Permission Options above) for the administrator account performing the migration, it must be set as Site Collection Admin of the Destination OneDrives

Preparing Azure Environment for Destination Endpoint

Microsoft-Provided Azure storage

We recommend using Microsoft-provided Azure storage for this migration. Refer to Microsoft documentation for more details. If you elect to use your own Azure Storage, follow the steps under Own Azure Storage below.

Own Azure storage

If you plan to use your own Azure storage, refer to the following steps to prepare your Azure environment. We recommend that you create your Azure storage account in the same Microsoft data center as the destination Microsoft 365 tenant. You do not need to create any Azure containers for this migration.

  1. Estimate Azure storage costs. This step is optional but is useful to provide the customer with up-front storage costs ahead of time. 
  2. Buy an Azure subscription

Subscription vs. Free Trial

You have the option to use the free one-month trial, but be aware that this option is only viable if you are performing a very small migration.

Create an Azure storage account

You will need to set up a STORAGE (General Purpose v2) account rather than a storage blob.

  • Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the destination settings. 

To create the Azure storage account:

  1. Visit the Azure portal.
    1. Click New.
    2. Select Storage.
    3. Select Storage account.
    4. Enter a name for your storage account.
    5. Choose the a Resource manager model for the Deployment model.
    6. Choose STORAGE (General Purpose v2).
    7. Record the storage account name (-accesskey, example: “accountname”) and primary access key (-secretkey, example: “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”)
    8. In the Replication field, select Locally Redundant Storage (LRS).
    9. Select the subscription in which you want to create the new storage account.
    10. Specify a new resource group or select an existing resource group.
    11. Select the geographic location for your storage account.
    12. Click Create to create the storage account.

Now the storage account appears in the storage list.

MSPComplete Steps

Licensing

Licenses are required to run a migration project in MigrationWiz. To obtain license pricing information, or to purchase licenses, click the Purchase button at the top of your MSPComplete or MigrationWiz dashboard.

Payment Options

  • When purchasing with a credit card, payment is immediately processed during checkout. If successful, licenses are granted to your account instantly.
  • Wire transfers are available for purchases of 100 or more licenses. If you are purchasing at least 100 licenses, you will be presented with an option to purchase via wire transfer during checkout. A wire transfer checkout will generate an invoice with wiring information for your accounts payable department and bank. Once the funds are received by our system, the licenses are granted to your account immediately. 

For this project type, it is recommended to use our User Migration Bundle licenses. 

  • User Migration Bundle Licenses have unlimited data available per license.
  • User Migration Bundle Licenses are applied to the customer's users and expire 12 months after their purchase date. 
  • Document, Personal Archive, and DeploymentPro projects are all included when using User Migration Bundle Licenses.
  • This license type must be applied manually.

To purchase licenses

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose the license type you need.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

These licenses enable you to perform multiple migrations of documents and in-place archives.

User Migration Bundle Licenses have unlimited data available per license. User Migration Bundle Licenses are applied to the customer's users, for whom you'll be performing migrations, and are valid for one year.

Read the Licensing FAQ article for more information.

MigrationWiz Steps

Create a Document Migration project

  1. Click the Go to My Projects.
  2. Click the Create Project.
  3. Create a Document project.
  4. Click Next Step.
  5. Enter a Project name and select a Customer.
  6. Click Next Step.

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search for them. Endpoint search is case and character-specific. For example, "Customer" will not show up if the search is "customer". We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints or create new ones. 

To create a new source endpoint:

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select the Google Drive (Own Service Account) or Google Drive endpoint, based on how the source was set up:
    1. Google Drive endpoint: Provide a valid super administrator email address for the G Suite account that matches the end user domain.
    2. Google Drive (Own Service Account) endpoint: Select the JSON file created in the steps above and enter the Super Admin username (email address) for the source.
  4. Select the JSON file created in the steps above and enter the Super Admin username and password for the source.
  5. Click Add.

To create a new Destination Endpoint in MigrationWiz

  1. Click DESTINATION SETTINGS.

  2. Click New.

  3. Under Endpoint Type, select OneDrive for Business.

  4. Select the radio button named  OneDrive for Business (Office 365 User) - Documents, Permissions, Versions and Metadata.

  5. Enter the administrator username and password in the proper fields.

  6. Enter the Azure Storage Account Name and Azure Access Key (if using your own Azure storage) or select Microsoft-provided Azure Storage. If entering the Azure Storage Account Name for the destination endpoint, only numbers and lowercase letters can be used. If you enter an upper case letter, your migration will fail.

  7. Click Add Endpoint. 

OD_1.png

Add users

Add the user accounts that will be migrated to the project. MigrationWiz allows you to bulk import users into the system.

Important

For OneDrive endpoints, the email address must match the current User Principal Name of the user in the tenant.

Add the accounts (also referred to as "items") for the migration project. There are several ways to do this. 

Quick Add

This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:

  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.
Autodiscover

The Autodiscover process within MigrationWiz can be used to discover items from the Source environment so that they can be imported into your projects. This can then be edited in the project to remove users not being migrated. All users are added with the source and destination email addresses set to match the source email.

This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

There are a few requirements for this to work:

  • The Source has to be Exchange 2007 or later, Office 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
  • The endpoint on the Source needs to use admin credentials.
  • The endpoint Administrator account on the source needs to be assigned the appropriate GSuite license for MigrationWiz to access Google Drive or Google Shared Drives for the Auto Discovery process.
  • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
  • The admin mailbox must be listed in the public Global Address List (GAL).
  • The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.

One additional item to note here is that there is no way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using one of the other available options.

Autodiscover of items will not work while using Modern Authentication

Autodiscovery exposes the following items:

  • For mailbox migration, autodiscovery will list all mailboxes at the Source.

Steps to Run Autodiscover

  1. Navigate to the project you want to import users into.

  2. Ensure that you have created an endpoint for the source project.

  3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

  4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

Advanced Options

Under the Support tab

Warning 

Remove and do not use DocumentBrowsingMode=Moderate in the Project advanced options.
This option will not able to migrate items from folders under My Drive NOT owned by the user resulting in missing items

Full Copy

  • DocumentBrowsingMode=FullCopy
    • See Google Drive Migration FAQ for more details

    • Scans “My Drive” for the source address in your migration project. 

    • Migrates all folders and files in "My Drive" regardless of ownership.
    • The destination OneDrive user will become the owner of all folders and files migrated from the source MyDrive. There is no current option to avoid this.
    • Documents and Document permissions must be migrated together in the first pass for permissions to be applied properly.
  • InvalidCharacterReplacementString=a (where 'a' is the string used to replace unsupported characters in file names)
    • SharePoint Online doesn’t allow some characters to be used as file names. The advanced option attempts to replace instances of unsupported characters in file names with the specified string provided by the advanced option. (e.g. a)
    • Please refer to Microsoft's documentation for unsupported characters.
  • InitializationTimeout=8 This increases the initialization timeout window to eight hours. This value is in hours, up to a maximum of 100 hours. Values above 100 are in milliseconds. This is useful for large migrations, for example:​
    • InitializationTimeout=2 will increase the timeout to 2 hours.
    • InitializationTimeout=21600000 will increase the timeout to 6 hours.
  • DestPersonalSitesIsProvisioned=1
    • MigrationWiz will use App-based authentication for OneDrive personal site retrieval.
  • IgnoreConflictingFiles=1
    • The project must have IgnoreConflictingFiles=1 added to the support options of the project to avoid duplicates. The one caveat with this is that if there is more than one file with the same name in the source Google Drive folders (which Google allows but not Microsoft) will be ignored as well.
  • RenameConflictingFolders=1
    • Microsoft does not support duplicated names of folders and files, unlike Google Workspaces. Therefore, this AO enables the migration of folders with duplicated names from Google Drive as a Source into Microsoft destinations. With this AO, folders with duplicated names will be migrated with a suffix.

  • ShrinkFoldersMaxLength=200 (where 200 is the maximum path length that can be tolerated before shrinking)
    • When migrating to SharePoint Online or OneDrive, the path length limitation is a common issue. Refer to the SharePoint & OneDrive FAQ to understand how this advanced option works.
    • Please note that, if the folder path is too long, even the truncated path using the advanced option may not be short enough to reach the SharePoint path length limit - in such case an error will be logged and the associated item will not be migrated. In this case, our recommendation would be to reduce the number of nested folders at the source to shorten the path.
  • UseGoogleAPIV2=1 This configuration avoids migrated items corruption and missing items issues. This is a default option.
  • UserMapping="abc_user1@source-domain.com->pqr_user5@destination-domain.com"
    • Use the UserMapping advanced option when you want to customize the permission mapping for a user or group.
    • UserMapping="groupS1@source-domain2.com->groupD5@destination-domain3.com"
    • UserMapping="@source-domain2.com->@destination-domain3.com"
    • Here are some more examples of how UserMapping can be used in this project:
      • The userMapping advanced option should be used when you want to customize the permission mapping.
      • Please note that the destination user/group (user5@destination-domain.com) must have been commissioned and be available at the destination document library before migration.

Permission Mapping Behavior

By default, MigrationWiz will map permission for users/groups by changing the source domain to the destination domain.

    • Domain from the admin emails, set by you for source and destination endpoints respectively, will be used for default permission mapping by MigrationWiz.
    • Permissions for users/groups with other domains (even if they belong to the source tenant) are considered external by default. External permissions are not migrated by default.
    • If your source has multiple domains then we strongly recommend the use of the UserMapping advanced option to set the desired mapping for permissions.
  • MapPermissionEmailByPairsInProject=1
    • When this advanced option is used, MigrationWiz will use the email address (source, destination) set in line items to map permission.
    • The example below: In this case, source permissions from user1@source-domain.com will be migrated to user5@destination-domain.com at the destination.

Speedster_3.png

    • Once set, this advanced option is applied to all line items in the same project.
    • If you have split all the Google Drive accounts across different MigrationWiz projects, use the Support Option MapPermissionEmailByPairsInCustomer=1 instead to use the mapping of all users across all projects.

  • OverwriteDestinationFilePermissionsAndMetadata=1 (only valid if permissions checkbox is selected and a second or delta pass is being executed).
    • When source files have updated permissions (user/group permissions, access levels), destination files also will be updated to reflect the latest changes from the source accurately.
    • When source file metadata has been updated, destination files will also be updated to reflect the latest changes from the source accurately (description (to Title), last modified by, last modified timestamp, owner, creator, created by).
    • When a source file is renamed, a new file will be created in the destination with a new name with updated metadata (description (to Title), last modified by, last modified timestamp, owner, creator, created by).
    • The best practice for leveraging this advanced option would be to utilize it during the final pass. Utilizing it for every subsequent pass will slow the migration process.

    • Exceptions to the above behavior when the destination file has been modified:
      • When the destination file name has been modified by the user - then the file will not be migrated.
      • When the destination file title has been modified by the user - then the description changes to the title from the source will not be migrated

Under the Filtering tab

  • Google file extension for filtering: As Google proprietary files do not contain a file extension (.doc, .jpg, etc.), MigrationWiz will recognize the following terms for the proprietary Google file types. The list of terms shown below should be used when the Advanced Option > Filter > By File Extension is used for any Google file type.

Google file types

Term to use as Google file extension

Google Docs

document

Google Drawing

drawing

Google Forms

form

Google My Maps

map

Google Slides

presentation

Google Apps Scripts

script

Google Sites

site

Google Sheets

spreadsheet

Google Jamboard

jam

f49440d8-4a85-48c1-86a8-2222e1190051.png

Under the Source/Destination tab

  • Set the number of versions to be migrated per project requirement:
    • The minimum number of versions to migrate is 1, the maximum number is 25.
    • The default selection for the number of versions is 1. Please update this value as per your requirements.
    • Known Limitation - Google Drawing and Google Slide will have the same recent version content across all the migrated versions.
    • Speedster_4.png
  • Multi-pass behavior: For information on how multi-pass behavior works in OneDrive and SharePoint migrations, see Versions & Metadata Migration for SharePoint & OneDrive.
  • Notifications
    • Send successful migration and notification to the Source email address (if users are still using G Suite Gmail) or Destination email address (if users are already using Microsoft 365).
    • Customize notification email: Checkmark the Customize "successful migration" email. Add your own customization text and company name to this email.
    • Notifications are not mandatory for a successful migration. Notifications should only be set up before the final pass as a courtesy to the users impacted by the final migration. If performing a single Full pass migration, set this notification up now. If you are following a Pre-Stage migration strategy, only set this up before the final Full (Delta) pass.

Run Verify Credentials

  1. ​Sign in to your MigrationWiz account.
  2. Open the Project containing the items you wish to validate.
  3. Select the items you wish to validate.
  4. Click the Start button in your dashboard.
  5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Send out the final notification that the migration is beginning. Include when the migration will start, the expected duration, any usage instructions during migration, and any expected steps or notifications for the post-migration timeline. Remind them to avoid modifying any documents at the Source, as this may cause corrupt data or an incomplete migration.

Run migration

Perform a Full Migration

  1. Open the project containing the items you wish to migrate.
  2. Select the line items to migrate.
  3. Click on the Start button in your dashboard.
  4. Select Full Migration from the drop-down list.
  5. Ensure that the Documents and Permissions checkboxes are selected.
  6. Click Start Migration.
  7. Once complete, the results of the migration will be shown in the Status section.

Speedster_65.png

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

Was this article helpful?
1 out of 1 found this helpful