Google Drive as a company file server: migration

Top 3 reasons to use a migration service

 
 

Umzuzu is a small, bootstrapped firm in the Kansas City area. Certainly year 11 is much easier than year 1, but we never forget our roots. We understand the desire and value of the DIY projects. They can often save money, especially initially. But as we all know, DIY projects can be surprisingly complex!

Can’t I just do this myself, manually?

It’s a question we get often. The technical answer is “yes”, of course you can. However, in most cases you shouldn’t. Here’s why!

  1. Tracking Changes

    The second you make a manual change, you have two diverging copies of your data. This is OK if no one is working with the content. Archival content, for example, can be moved this way (in small volumes). If you have people doing their jobs -hopefully you do- the second you copy live data to Google Drive or another cloud service, your copy is out of date.

Allow your team to keep working while the migration service tracks and reconciles all changes throughout the duration of your project.

  1. Reporting

    There are several ways to manually migrate data from on-premises Windows servers and NAS devices to Google Drive and other cloud-based file servers. A primary problem with every manual option is a total lack of reporting. Did everything move? Who knows. What failed? Who knows. My source and destination content sizes are different. Why? Again, who knows. Did the migration finish or just stop running? Not sure. It’s impossible to run a manual migration with any certainty of results. There are no troubleshooting options besides starting over from the beginning.

Ensure a successful migration, backup or sync with downloadable transfer reports with checksums for validation, auditing, and compliance.

  1. Planning

    How many directories and files do you have? Each Team Drive can contain a maximum of 400,000 files and folders. How many files have been created and/or modified in the past 12 months. How much of your data is archival vs working? What do your security permissions look like? It’s difficult to plan on moving what you can’t see. While you can certainly analyze hundreds or thousands of gigabytes manually, it would not be easy or fun. Manual analysis would also be error prone as similarly named files and directories are common.

The ability to discover, filter, and analyze a data set before any content is moved enables a migration, backup, or sync project to be predictable. Give your users a smooth transition to a new system with scheduled cutovers.