A solid move file server to cloud checklist needs to do more than list obvious steps. The most common failure pattern: a business migrates everything cleanly, then finds on Monday morning that the accounting software cannot open its data because a path changed and nobody knew that path was buried in a Windows registry entry rather than a config file anyone could edit. The decisions you make before you touch a single file determine whether this takes a weekend or drags on for weeks.
This checklist walks you through the right order of operations: audit what you have, pick the right platform, sort out access and permissions, handle the data move, and verify everything works before you cut over. Work through each phase in sequence. Skipping ahead is how small businesses end up rebuilding access from scratch on a live system.
Take Stock of What You Have Now
Before you touch a single file, spend time understanding exactly what you are migrating.
Start with total data volume. Connect to your file server and check how much storage is actually in use. This number drives platform choice and cost estimates more than anything else.
Next, map your folder structure. Document the top-level folders, who owns each one, and roughly how deep the nesting goes. Flat, clean structures migrate faster. Tangled ones need cleanup first, and it is better to discover that now.
Identify every active user. Pull a report from your server or Active Directory, whichever applies. Remove stale accounts while you are there. Migrating dead accounts wastes time and creates security risk on the other end.
Then find every application that touches the file server. Accounting software, line-of-business apps, and automated backup jobs often read or write to specific paths. Here is what most businesses miss: some of those apps store their file paths not in a config file you can open and edit, but in Windows registry entries buried several levels deep. When the server name or share path changes after migration, those apps break silently. There is no error on screen. The software simply cannot find its data. List every app before you plan anything, and check whether its paths live in a config file or in the registry.
- Total storage in use.
- Folder structure and ownership.
- Active user accounts.
- Applications and scripts that depend on file server paths, and where those paths are stored.
Write this down. A one-page summary prevents surprises when you pick your platform in the next step.
Choose the Right Cloud File Storage Service
Your one-page inventory drives this decision. Match the platform to what you actually have, not what a sales page describes.
Start with protocol. If your staff access files over the network today, they almost certainly use SMB (Server Message Block), the standard Windows file-sharing protocol. Any platform you choose must support it natively, or you will face compatibility problems on day one.
Amazon FSx supports SMB natively for network file access (AWS). Next, consider application compatibility. Some line-of-business apps expect a true Windows file system, not just an SMB share.
If that describes your environment, AWS FSx for Windows File Server is built to lift and shift those workloads without rearchitecting them (AWS). If your needs are simpler, file sync-and-share services like Microsoft SharePoint or Google Drive may cost less and require less management. That said, sync-and-share platforms handle permissions differently than SMB shares do and they do not expose a drive letter your line-of-business apps can address directly. If any of your apps reference a mapped drive path, an SMB-based cloud share is the safer choice.
Ask each vendor these two questions before you commit:
- Does your service support SMB natively, or only through a gateway?
- Which Windows file system features do you support?
Budget matters too. Confirm per-user and per-terabyte costs, and ask what egress fees apply when you move files back out.
Prepare Your Files Before You Migrate
Before you migrate a single file, clean house on the source server. Start by identifying stale data: files that have not been touched in years waste storage and inflate your migration window. Delete or archive them locally first.
Next, check your folder depth. Many cloud platforms and sync clients struggle with very long file paths. Flatten any folder trees that are nested more than four or five levels deep, and rename folders that contain special characters or leading spaces.
Then document your existing permissions carefully. Map out every shared folder, who has access, and whether that access is set at the share level or the NTFS level (the Windows file-system controls underneath the share). This step matters more than most migration guides admit: some migration tools strip NTFS permission inheritance silently. Child folders that inherited permissions from their parent end up with explicit permissions, or none at all, after the move. There is no warning and no error log entry. Users simply lose access and report it as a bug the following morning. Spot-checking permissions on a sample of child folders immediately after migration is the fix.
Finally, do a trial run on a small, low-risk folder before moving anything critical. That dry run will surface path errors, permission gaps, and sync conflicts while the stakes are still low. Fix what breaks, then scale up.
Run the Move File Server to Cloud Migration
Pick a migration tool that fits your volume. Small sets of files move fine with a simple drag-and-drop client. Larger migrations need a dedicated tool that logs every file, retries failures, and produces a completion report you can audit.
Run a pilot batch first. Take that low-risk folder from your dry run and push it through the actual tool against the actual destination. Confirm that folder paths land correctly, permissions carry over, and nothing syncs twice.
Plan for regional network access before you cut over. If you are using Azure Files with SMB 2.1 and encryption in transit is not enabled, clients outside the file share's Azure region cannot connect to it (Microsoft). Regardless of platform, map where your users sit and confirm they can reach the target region before migration day.
Schedule the full cutover during low-traffic hours. Redirect users to the new share, verify they can open and save files, then leave the old server in read-only mode for a short hold period. Do not decommission it on day one.
Once all users confirm access and your logs show no errors, the old server is ready to retire.
Verify the Migration and Lock Down Access
Start by spot-checking files across every department. Open several documents, compare sizes, and confirm version history carried over. Do not assume a completed sync means a clean sync.
Next, restrict who can reach the storage at the network level. Cloud platforms let you limit access to your office IP ranges and approved devices before anyone outside your perimeter can even attempt a login. Use security groups tied to your virtual private cloud to enforce that boundary (AWS).
Review every permission group after the move. Access tends to expand during migrations. This is also where you will catch any inheritance stripping that happened during the move: check that child folders still inherit the right permissions from their parent folders rather than carrying a mix of explicit and inherited rules that nobody intended.
Admin accounts deserve separate attention. Give users who need local admin rights on their own machines a dedicated account that carries no elevated access to your cloud file environment or other servers (CISA). For your domain controllers, CISA also recommends implementing a privileged access management solution to help manage and monitor privileged access (CISA). Enable audit logging on your cloud file platform so every admin action there is recorded and easy to review. Check those logs after the first full week of production use. Unusual access times or repeated failed logins are early warnings worth catching now.
Update Users and Document the New Setup
With the files verified and permissions locked down, turn your attention to the people who use the system every day.
Update every mapped drive and saved shortcut that points to the old server. Walk through a checklist of common access points: desktop shortcuts, department shared drives, email attachments that link to file paths, and any application that references a local server address. Missing one is easy and causes immediate complaints. This is also the moment to revisit those registry-stored paths you found during the inventory step and update them to the new server address.
Send a short plain-language note to staff before the cutover goes live. Tell them what is changing, what they need to do differently, and who to call when something breaks. Keep it to three bullet points if you can.
Then document the final setup while the details are fresh. Record the platform, folder structure, permission groups, sync client versions, and the name of the admin account. Store that document somewhere other than the new file platform itself. If you need to plan for what happens if the cloud file service goes offline, our disaster recovery and business continuity services page covers your options.
Schedule a check-in with your team two weeks out. Ask what is broken, slow, or confusing. Small friction points surface fast in daily use and are worth fixing before they become habits. The two-week check-in is where most of the remaining loose ends get resolved.
For a related guide, see NAS vs Cloud Backup for Small Business: How to Choose. If you want help with this work, see our cloud and infrastructure services and data center and colocation services pages.
If you want help working through this, book a free 30-minute call with Joshua and talk it through. He can help you pick the right platform, review your permission structure, and avoid the silent failures that most migration guides never mention.




