1. BitTitan Help Center
  2. Perform a Migration
  3. Google
  4. Documents

Google Drive to Dropbox Migration Guide

Introduction

This is the complete onboarding task flow for migrating folders and documents from Google Drive to Dropbox.

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

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.

 

Items and folders in "Shared with Me" will not be migrated. Only items in "My Drive" will be migrated. To migrate "Shared with Me" items, they must be added to "My Drive".

 

Prepare the Source Environment

Google Drive (Own Service Account) Endpoint 

This endpoint requires your tenant service account to be set up and Google APIs be enabled. Follow the steps below to set up your environment for this endpoint. 

Prerequisites:

  • Subscription to Google Cloud Platform.

  • Google Super Administrator account.

  • Ability to set up a service account on the G Suite tenant.

  • Service account must be set up before the MigrationWiz project is created.

 Step 1: 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.

 Step 2: 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.

 Step 3: Create Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.

  2. Click Create Service Account 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 Done.

  6. You will now be returned to the "Service Accounts" page. 
  7. On ‘Service accounts' page, click vertical ellipsis under 'Actions’ column for the service account created above.

  8. Click + Add Key.

  9. Click Create New Key.

  10. Make sure that JSON is selected as "Key Type."

  11. Click Create.

  12. Click Close.
    Notes:

    • Make sure that you 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 Mailbox Migration project.

    • 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.

Step 4: Setting the Scopes for the Migration

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 Customer Tenant Account.
    5. Find the Unique ID field for that service account by clicking the Column Display Options button in the right upper corner above Actions and copy the ID number. This is the Client ID number that will be used in a later step.
      Note:
      • 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:

    • Go to the G Suite admin page at google.com
    • Click on Security
    • Click on Advanced Settings
    • 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

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

     Once these steps are complete:

    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:
      1. 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
        OR
      2. For destination endpoint (must include read-write scopes):
        https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, 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,
        https://www.googleapis.com/auth/drive
    3. Click Authorize.

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

 

Prepare the Destination Environment

  1. Create the Dropbox Business account and purchase Dropbox licenses.
  2. Create a Dropbox user account that will be used for the migration, and grant this account appropriate team admin privileges. Follow the instructions in the Add Tiered Admins guide from Dropbox.
  3. Use the list created under Step 3 of the Prepare the Source Environment section of this guide to recreate users in the new Dropbox Business account. Follow the instructions in the Invite your Team guide from Dropbox.

    Note: Users must accept the invitations before their accounts are created at Dropbox. You must wait for the team to accept the invitations before starting the migration, or the migration will fail.

 

 

MigrationWiz Steps

Create New Project

Create Google Drive (Own Service Account) Source Endpoint

To create a new migration project:

    1. Click the Go To My Projects button.
    2. Click the Create Project button.
    3. Click on the type of project that you wish to create. For this scenario, select Document. Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.
    1. Click Next Step.
    2. Enter a Project name and select a Customer.
      Note: If you have not already added the customer into MSPComplete, you will need to click New to create the Customer. For steps on creating customers, see View, Add, and Edit Your Customers.
    3. Click Next Step.
    4. Select a Source Endpoint from the Endpoint dropdown menu or create a new endpoint. 
      Notes:

      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive (Own Service Account).

      • Click Select File > Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.

      • Enter the Google admin account email address. Please note that this admin email should match the end user domain.

    5. Select the Dropbox Destination Endpoint from the Endpoint dropdown menu or create a new one.
    6. Click Save and Go to Summary.
      Note: If setting up a Tenant to Tenant Coexistence mailbox project, check the box for Enable Tenant to Tenant Coexistence. Otherwise, leave that box unchecked.

Once the project is created:

    • Note: At the Authorization tab, click the Request Access Token button. Within the Dropbox - API Request Authorization page, enter the email address and password for the Dropbox admin account and click the Allow button on the next screen.
  1. Add the accounts (also referred to as "items") that will be migrated to the project. Read the How do I add items to my migration project? article for more information.
  2. Run an assessment to calculate the number of licenses required for your migration. Read the How does the MigrationWiz Assessment tool work? article for more information.
  3. Set the Project Advanced Options. Read the What project Advanced Options are available? article for more information.
    • Set the Advanced Option to send a notification to end users after the migration pass completes.
      • Notifications > Send successful migration and notification to: > Source email address (if users are still using G suite Gmail) or Destination email address (if users have already migrated from the G Suite gmail platform).
      • Customize the notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
        Note: Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-stage migration strategy, only set this up prior to the final Full (Delta) pass.
  4. Run Verify Credentials. Read the How do I verify credentials? article for more information.
  5. Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Google Drive accounts, because any modifications will not be included in the migration.
  6. Perform the migration, using one of the following strategies:
    • Full Migration strategy. For more information, see How do I start a migration?
      • For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
    • Pre-Stage Migration Strategy:
      • Pre-Stage pass. For more information, see How do I start a migration?
      • Full (Delta) pass. For more information, see How do I start a migration?
      • For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.
        Important: Recent changes to the Dropbox APIs prevent us from adding watermarks on files in the Destination Dropbox accounts. Therefore, if you perform a partial migration, reset the items in MigrationWiz, and then perform the migration again, you will end up with duplicate files at the Destination. If you must rerun the migration, we recommend that you first delete all files already migrated to the Destination Dropbox accounts.
  7. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.

 

Post-Migration Steps

  1. To prevent users from inadvertently logging in and using their Google Drive accounts, decommission the Google Drive user accounts, or change their passwords.
  2. Notify users once the migration has completed.

    Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon completion of the migration. Assist them with setting up access to their Dropbox accounts.
  3. Provide training to end users on Dropbox.

 

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

Articles in this section

See more