You copy the client folders to cloud storage. The migration report looks good. Then an employee discovers they can’t edit a working file, an old link opens the wrong copy, or a spreadsheet still points to the office server. Those problems often only show up when people try to do their usual work.
Use this cloud migration checklist for moving small-business files to plan the move, test it on a few folders, and confirm the copied files work for the right people. The scope is shared files and folders, such as moving from an office file server to a company-managed cloud workspace. Email, applications, and databases need their own plans.
1. Inventory what you have and what depends on it
List the folders you intend to move, their approximate size, the team responsible, and the destination. Flag sensitive folders and anything shared with contractors or clients. Agree with the owner on which items move, stay in an approved archive, or need a decision. Keep records subject to retention or a hold until the appropriate owner approves how they’ll be handled.
| Inventory field | What to record |
|---|---|
| Source and owner | Current location and the person who can confirm what belongs there |
| Size and number of items | Approximate storage and item counts for planning |
| Access | Who reads, edits, or shares the files, including any external users |
| Dependencies | Shortcuts, linked spreadsheets, shared URLs, templates, and tools that read or write files |
| Destination and status | Target library or shared drive, migration wave, and validation owner |
Ask staff how they use the files. Someone may open a report through a bookmark or run a weekly process that reads from a named server path. Add those workflows to the test list.
2. Set up the destination and map access
Create team-owned storage in the company’s workspace. Decide which folders or libraries need different access rules. Put sensitive material such as payroll in a restricted location and define who should be able to view, edit, or share from it.
Permissions can behave differently after a move. Microsoft’s Migration Manager has settings for preserving supported file share permissions and mapping users. Google notes that shared drive settings can affect access to moved files and folders. Confirm the behavior of the specific tool and destination you’ll use. Microsoft Migration Manager settings · Google Workspace shared drive access
Write expected access in plain language, such as “Finance staff can edit, project leads can view approved budgets only, and contractors have no access to this library.” Test with ordinary accounts for those roles. An administrator’s account can hide a permission problem.
3. Keep a recoverable copy and run a pilot
Confirm you have a backup of the source and can restore a file from it. Keep a dated record of the backup location and who can access it. The new cloud copy is still being checked during the migration, so keep your existing recovery option available.
If your migration tool supports a pre-scan, run it and review flagged items. Look for file types, names, paths, and sizes the destination may reject. Check how the tool handles timestamps, ownership, versions, and links if they matter to your work. Microsoft guidance on scanning file shares · OneDrive and SharePoint file restrictions
Pilot a small set that represents your real work. Include an actively edited document, a large file, a restricted folder, and an item shared externally if applicable. Ask the people who use them to open, edit, save, and share according to their role. Test whether a user outside the permitted group is denied access.
4. Copy in batches and reconcile the results
Give each batch an owner, a scope, and a review time. Keep a record of the planned items and compare it with the destination and the tool’s reports. Review skipped files, errors, filters, and conflicts. If counts differ, explain why. A matching count can still hide unreadable files or access problems, so also open important files and test the workflows that depend on them. Microsoft Migration Manager reports guide
Keep a short log for anything that needs rebuilding, including shared links, shortcuts, and links between files. Avoid assuming links will either survive or break across every migration. Test the ones teammates and clients actually use, replace them where necessary, and verify the replacement reaches the correct audience.
5. Switch the team to the new location
Tell staff when to stop editing the source and where to open files after the switch. If your tool supports a final pass for changes since the first copy, finish it during the agreed window and check its results. If it does not, agree in advance how you’ll identify and copy edits made since the initial batch. Avoid simultaneous writes in both locations.
Define what would delay the switch. For example, you might postpone it if the team cannot open its active project files or if a contractor can see a restricted folder. Decide who can pause the move, who can restore access to the old location if needed, and how to capture any work made in the destination before rolling back.
Keep the old location available for a limited review period
Once the team starts working from the destination, keep the old source read-only where feasible and label it clearly. Agree on a review period with the file owners. Then retire it after owners sign off, exceptions are resolved or documented, and the backup and retention plan is in place.
Worked example for a small design studio
A fictional design studio moves project folders from an office server to cloud storage. Its pilot includes one client folder, a restricted finance folder, and a spreadsheet that links to an estimate in another folder.
| Pilot finding | What the studio does |
|---|---|
| Staff can open the client briefs but can’t save edits. | The owner corrects the intended editor group and asks staff to retest. |
| An outside contractor can open a client-approved folder but also sees an internal subfolder. | The owner removes the unintended access and repeats the test with the contractor account. |
| The estimate opens, but the workbook’s link still points to the office server. | The team updates the link and verifies the report still uses the correct figures. |
The studio schedules the full switch once the lead designer can edit active files, the contractor can only reach the approved area, and the report works in the new location. It keeps the old share read-only while the team checks its first week of work.
Copy-ready cloud migration checklist
- Record source folders, owners, access, and dependencies.
- Confirm the destination, its limits, and the data that must be preserved.
- Verify a source backup and test restoring a file.
- Run a pilot with representative files and ordinary user accounts.
- Copy the remaining batches and review errors, omissions, and conflicts.
- Confirm important files open and links or workflows still work.
- Schedule the edit cutoff and capture remaining changes.
- Announce the new location and review permissions again.
- Get owner sign-off before retiring the old location.
Frequently asked questions
1. Can I drag and drop the files myself?
For a small set of ordinary files, that may be enough. Test what the copy preserves and who can open the destination. Use a supported migration tool when you need reporting, permission mapping, or a way to capture later changes.
2. Will my sharing permissions carry over?
It depends on your source, destination, and tool. Check groups and individual sharing settings. Verify access using ordinary staff and external test accounts where appropriate.
3. Do old file links still work after a cloud migration?
Some may, depending on what changed and how the links were created. Test the links used in active documents, emails, and workflows. Replace any that fail or point to an old copy.
4. How long should I keep the old file server?
Set a review period based on how often you use the files, backup coverage, and any retention requirements. Keep the old copy read-only where feasible and get owner approval before retiring it.
5. What if files are missing after the move?
Check the migration reports and source filters first. Compare the expected and actual locations, and check whether a permission setting hides the item. Keep a record of exceptions and use the source or backup to restore confirmed omissions.
Conclusion
Move a representative set of files first and ask the people who use them to test access, links, and everyday edits. Once those checks pass, move the remaining files in batches and capture any last changes before directing everyone to the new location. Keep the source available until the owners confirm the move is complete.

