The telltale signs of a successful migration from Box to Google Drive are minimal disruption and a smooth adoption process for your end users. In this guide, we’ll walk through the key steps and considerations to keep in mind during the migration process using CloudM Migrate, a powerful tool that simplifies moving your data.

1. Prepare your source

Before diving into the migration, it’s crucial to prepare your source environment — in this case, Box — to avoid surprises that can cause issues down the road.

What to keep in mind

When migrating data from Box to Google Drive, there are several factors to consider to ensure a smooth transition:

Document permissions

Migrating permissions can be tricky. It’s important to ensure that shared folders, documents, and their permission levels are carried over correctly. CloudM Migrate can migrate documents with their associated permissions, so files will remain accessible to the same users.

Folder structure

Migrating your folder structure is crucial, especially for teams that rely heavily on file organization within Box. Fortunately, CloudM Migrate allows for the preservation of the folder hierarchy, ensuring everything remains as familiar as possible for end users.

Less is more – clean up before the move

A migration is an excellent opportunity to tidy up your data. Over time, files that are no longer relevant or necessary can clutter your storage and slow down progress. With CloudM Migrate, you can ensure only required data gets transferred by:

Targeting specific users or folders: you have the flexibility to migrate specific users or groups of users to a Shared Drive or personal account. CloudM Migrate also allows targeting a specific folder within a user’s Box account.

Applying date filters: to avoid moving unnecessary data, you can set date filters to migrate only files that were created or modified within a specific date range. 

2. Consider the specifics of your destination

While Google Drive is a powerful and flexible platform, it’s important to understand its limitations to avoid any issues post-migration.

Google Shared Drive object limits

As of July 2024, Shared Drives in Google Workspace have expanded capabilities. Shared Drives can now have:

  • 100 levels of nested folders
  • Up to 500,000 items

While this increased limit provides more flexibility, it’s essential to keep track of how deep and complex your folder structures are during the migration to avoid hitting these limits.

Google folder depth limit

Google Drive limits the depth of folder structures, which could be a concern if your current Box environment has extremely deep folder trees. Although Shared Drives now allow for up to 100 levels of nesting, consider simplifying your folder hierarchy where possible to make navigation more intuitive for your team.



Get Started

CloudM empowers IT teams to migrate, archive and backup data
through frictionless, secure and automated solutions. 

  • Over 10M+ Migrations
  • 24/7 Dedicated Support
  • Google & Microsoft Certified
partner logo
partner logo
partner logo
partner logo
partner logo
partner logo
partner logo
partner logo
partner logo
partner logo

Fill out the form and one of our team will contact you.

partner logo partner logo


3. Execute the migration

Once your source environment is prepared and you’ve considered the limitations of your destination, it’s time for the actual migration.

1

Configure the source

When using CloudM Migrate, you’ll authenticate Box using JWT (JSON Web Token) authentication, which is a more secure method than some alternatives. This ensures that your data transfer is encrypted and secure during the migration process.
2

Configure the destination

Next, you’ll configure Google Drive as the destination. Ensure that permissions are set properly and that Shared Drives or user accounts are ready to receive the data.
3

Select items

At this stage, you can choose which users to migrate from Box to Google Drive. This could be individual users, groups of users, or all users across your organization.
4

Select content

Here, you’ll specify which data you want to migrate, whether it’s all user data or only specific files. This step allows you to filter content based on the user or folder.
5

Scan the environment

Running a scan of both the Box and Google Drive environments is essential to identify any potential issues, such as file size limits, unsupported file types, or naming conflicts.
6

Run the migration

Once the environment scan is complete, it’s time to run the migration. CloudM Migrate handles the heavy lifting, transferring data securely from Box to Google Drive.
7

Review the results

After the migration is complete, it’s important to review the results and ensure all data, permissions, and structures were transferred correctly. This is where you'll verify that everything is in place for a smooth transition.
8

Run delta migrations

To ensure you haven’t missed any changes or updates that occurred during the migration window, run one or several delta migrations. This will capture any files that were modified or created after the initial migration began.

Conclusion

Migrating from Box to Google Drive is a critical task for any organization looking to streamline its cloud storage. By following these steps and utilizing CloudM Migrate, you can ensure a smooth and efficient migration process that keeps your data, permissions, and structures intact while avoiding common pitfalls. 

If you are facing a particularly complex migration scenario or simply don’t have the internal resource and experience to tackle your upcoming migration project alone, CloudM are happy to help. We offer serviced migrations as well as customer-led consultancy workshops to ensure your success. 

Book a call with our migration specialists today

Latest resources

Blog

Choosing a software solution: Eight things to consider for the NIS2 directive

November 15, 2024

Find out more
Customer Story

Seamless integration of Google Workspace tenants transforms Atlassian post-acquisition

November 13, 2024

Find out more
Product

Product update: more flexibility for your offboarding workflows and email signatures in CloudM Automate

November 12, 2024

Find out more
  • Choosing a software solution: Eight things to consider for the NIS2 directive

    November 15, 2024

  • Seamless integration of Google Workspace tenants transforms Atlassian post-acquisition

    November 13, 2024

  • Product update: more flexibility for your offboarding workflows and email signatures in CloudM Automate

    November 12, 2024

Back to Resources