Why the old shared drive has to go — eventually
The box in the closet that holds every file your business ever made has real weaknesses: it can die without warning, it is only reachable from the office or over a fussy VPN (a private tunnel into your network), it rarely gets backed up as well as everyone assumes, and two people cannot work in the same file at once. Cloud storage — keeping files on a service like Google Drive or Microsoft SharePoint instead of a machine you own — fixes all four.
But I want to be honest: this migration is a project, not an afternoon. Businesses that treat it as an afternoon end up with two half-organized copies of everything and staff quietly saving files to their desktops. Done in the right order, it is a few calm weeks, and the order is the whole trick.
Plan the folder structure and permissions before moving one file
The worst move is copying the old drive's mess into the cloud as-is. That mess grew from years of nobody deciding anything, and the migration is your one chance to decide.
Keep the structure boring: top-level folders by function — Admin, Finance, Clients, Projects, HR — with a consistent pattern inside each. Aim for a layout a new hire could guess.
Permissions are where cloud storage earns its keep. On the old drive, odds are everyone can see everything, including payroll. Decide now who can view and who can edit each top-level folder, and set the rule at the folder level, not file by file. HR and Finance restricted, everything else open, is a fine small-business starting point.
Also decide what does not move: files untouched for five or more years go into an Archive folder in the cloud — out of the way, but not deleted.
Migrate in the right order, not all at once
The order that works:
- Move the Archive first. It is big, nobody is editing it, and it lets you test the process harmlessly.
- Move one active department and have them work fully in the cloud for a week or two. Their problems become your checklist for everyone else.
- Move the rest, folder by folder, announcing each move.
- Make each old folder read-only the day it moves. This is the step everyone skips, and it is the reason migrations fork into two versions of the truth. People can still look at the old copy, but new work happens in the cloud only.
A migration tool or an IT partner can bulk-copy large drives with permissions intact; a small drive can honestly be moved over a weekend by hand. Size dictates the method. The order stays the same.
The things that break, because something always breaks
Each of these has caused a support call in a real office, so check them on purpose:
- Shortcuts and mapped drives. Anything pointing at the old drive letter dies — desktop shortcuts, template paths saved inside accounting or design software.
- Linked spreadsheets. Excel files that pull numbers from other files by path break when the path changes. Find them before the move by asking staff which spreadsheets update themselves.
- The scanner. Office scanners set to scan-to-folder are pointed at the old drive and need repointing. This is reliably the first complaint after a switch.
- Long paths and odd characters. Deeply nested folders with long names can exceed cloud limits; the migration report lists what got skipped, so actually read it.
- Database-style files like QuickBooks company files. Some line-of-business files should not live in synced folders while open — ask the vendor first.
Training, the read-only window, and the day you switch it off
Training is one hour, not a course: where things live now, how to search (in the cloud, search beats browsing), how sharing links replace email attachments, and who to ask when stuck. Write a one-page cheat sheet and pin it somewhere visible.
Then leave the old drive on, read-only, for 60 to 90 days. That window catches what every checklist misses — the quarterly report that pulls from a linked file, the template someone opens three times a year. When a full month passes with nobody touching the old drive, take one final backup of it, keep that backup for at least a year, and switch the machine off.
Before the hardware leaves the building, wipe or destroy its drives. That box holds your entire business history, and disposal without a wipe is how histories leak.
Your move plan
- Choose the platform — usually whichever matches the email suite you already pay for.
- Sketch the top-level folders and permission rules on one page, and get a second opinion on it.
- Move the Archive, then one pilot department, then everyone else, making each old folder read-only on its move day.
- Repoint scanners, shortcuts, and linked spreadsheets from the checklist above.
- Hold the 60-to-90-day read-only period, take a final backup, and power the old drive down.
For a typical small office this is two to five weeks elapsed, and most of that is waiting, not working. If you would rather have it handled — planning, permissions, the bulk move, and yes, the scanner call — this is one of the most common projects we take on at HashWhales for offices around the DMV. Either way: structure first, read-only on move day, and never skip the linked-spreadsheet hunt.