Windows File Server to NAS Migration Guide

How to migrate a Windows file server to a NAS. Covering share mapping, user accounts, permissions, offline file migration, and DFS namespace considerations for SMB environments.

Replacing an aging Windows file server with a NAS is one of the most common SMB IT projects. A dedicated NAS costs less to run, requires less management overhead, and provides comparable SMB file sharing with built-in RAID for most workgroup environments. This guide covers migrating from a Windows Server (2016/2019/2022) to a Synology or QNAP NAS: inventorying existing shares and permissions, migrating data, recreating user accounts and share permissions on the NAS, and transitioning clients with minimal downtime. Both Synology DSM and QNAP QTS support Active Directory integration, SMB share permissions matching Windows Server, and all standard Windows client features (offline files, Distributed File System references).

In short: Inventory Windows Server shares and permissions → create matching shared folders and user/group accounts on the NAS → use robocopy to migrate data preserving ACLs where applicable → update DNS/DFS to point clients to the new NAS share path → decommission Windows Server. A controlled migration takes 1-2 days for a small workgroup with a dedicated maintenance window.

Windows File Server to NAS: 5-Phase Migration Overview
Phase 1
Inventory
Document shares, permissions, and data size on the current Windows server
Phase 2
Setup NAS
Create matching shares and user accounts on the NAS
Phase 3
Migrate Data
Run Robocopy to copy files. Repeat with /MIR on cutover day
Phase 4
Client Cutover
Remap drives via DNS rename or Group Policy. Test with a pilot user first
Phase 5
Verify
Confirm permissions, test logins, enable backup, decommission Windows server
Before
Windows Server 2012–2019
SMB shares, AD user accounts
Manual backups
Requires Windows CALs
After
Synology DS923+, DS1522+ or QNAP TS-464
SMB/CIFS compatible (transparent to clients)
Automated versioned backup
No CAL cost, lower power draw

Typical migration window: 1 weekend. Robocopy handles permissions, ACLs, and timestamps. Full details for each phase in the sections below.

Phase 1: Inventory the Existing Windows File Server

Before migrating, document what exists on the current server. Run the following on the Windows Server to export share and permission information:

net share > shares.txt
Get-SmbShare | Select-Object Name,Path,Description | Export-Csv shares.csv
Get-Acl -Path C:\Shares\* | Format-List | Out-File permissions.txt

Document for each share:

  • Share name and UNC path (e.g. \\SERVER\Finance)
  • Local path on server (e.g. D:\Shares\Finance)
  • Users and groups with access, and their permission level (Read, Read/Write, Full Control)
  • Approximate data size: Get-ChildItem -Path D:\Shares\ -Recurse | Measure-Object -Property Length -Sum

This inventory drives the NAS share structure and user account setup.

Phase 2: Set Up NAS Shares and User Accounts

On the NAS, recreate the share and user structure from your inventory:

Option A: Local NAS users (small workgroups without Active Directory):

  1. Create a shared folder on the NAS for each Windows share (e.g. Finance, Projects)
  2. Create user accounts matching your Windows Server user names (same username, new password. Distribute to users)
  3. Assign each user to the appropriate shared folders with Read or Read/Write permissions in the NAS control panel

Option B: Active Directory domain join (workgroups with an AD domain):

  1. On Synology: DSM → Control Panel → Domain/LDAP → Join domain. Enter domain controller details
  2. On QNAP: QTS → Control Panel → Network and File Services → Win/Mac/NFS → Microsoft Networking → Security → Join domain
  3. After joining, AD users and groups are available in the NAS share permission editor
  4. Assign AD groups to NAS shared folders. The permission model mirrors Windows Server share permissions

AD domain join means users authenticate with their existing domain credentials. No new password distribution required. Strongly recommended if you already have an AD domain.

Phase 3: Migrate Data with Robocopy

Robocopy is the standard tool for migrating Windows file server data. Run from the Windows Server or a client with access to both source and destination:

robocopy "\\SERVER\Finance" "\\NAS-IP\Finance" \
  /E /COPYALL /DCOPY:T /R:3 /W:5 /LOG:migration_finance.log /TEE

Key flags:

  • /E. Copy all subdirectories including empty ones
  • /COPYALL. Copy file data, attributes, timestamps, and Windows ACLs. Note: NAS file systems (ext4, Btrfs) do not preserve Windows NTFS ACLs natively. Permissions must be set on the NAS share level, not individual files
  • /DCOPY:T. Preserve directory timestamps
  • /R:3 /W:5. 3 retries, 5 second wait (handles locked files)
  • /LOG. Write log to file for audit trail

For large migrations: run an initial robocopy pass to copy the bulk of data (this can run overnight), then run a second pass with /XO (exclude older) to sync changes made since the first pass. The second pass runs quickly and minimises the cutover window.

Phase 4: Client Cutover

Transitioning clients from the Windows Server to the NAS can be done two ways:

DNS redirect (zero-client-change): Update the DNS A record for the old server name to point to the NAS IP. Clients using \\servername\share paths continue to work because the name resolves to the NAS. This requires the NAS to have the same SMB share names and the NAS hostname to match (or use a CNAME). Cleanest approach for large numbers of clients.

Group Policy mapped drives update: If clients have mapped drives assigned via Group Policy, update the GP drive mapping to point to the NAS UNC path. Push the GP update. Clients receive the new mapping at next logon or policy refresh.

Manual re-mapping (small environments): For 5-10 users, update each client's drive mappings manually. Right-click the mapped drive → Disconnect. Then Map Network Drive → enter the NAS path (\\NAS-IP\Finance). This takes 2-5 minutes per workstation.

After cutover, verify: users can read and write, permissions are correct for each group, and no users report access issues. Leave the Windows Server online for 1-2 weeks as a fallback before decommissioning.

Phase 5: Post-Migration Checklist

After the cutover:

  • ✅ Verify all share permissions. Test with a standard user account (not admin)
  • ✅ Confirm backup is running on the NAS (Hyper Backup or Hybrid Backup Sync)
  • ✅ Update DNS records to reflect the new NAS as the file server
  • ✅ Document the new share paths and share them with users
  • ✅ Run a final robocopy sync to capture any files written to the old server after cutover
  • ✅ Test restore from the NAS backup before decommissioning the Windows Server
  • ✅ Decommission Windows Server or repurpose for other roles

🇦🇺 Australian Buyers: NAS Recommendations for SMB Migration

Recommended NAS for Windows file server replacement in Australian SMB environments (March 2026):

  • Synology DS423+ (~$980): Most common SMB file server replacement. Active Backup for Business (backup Windows PCs agentless), strong AD integration, Hyper Backup for cloud offsite. Intel Celeron J4125 handles 10-20 simultaneous SMB connections comfortably
  • Synology DS923+ (~$980): AMD Ryzen R1600. Stronger multi-threaded performance for environments with 20+ simultaneous users or heavy file operations. Same software suite
  • QNAP TS-464 (~$989): Good alternative for environments that want hardware flexibility (PCIe 10GbE upgrade path). QTS Active Directory integration is mature. Hybrid Backup Sync handles cloud backup

For environments needing 10GbE for high-throughput file sharing (video production, large CAD files), consider Synology DS1823xs+ or QNAP TS-873A for built-in 10GbE, or add a PCIe 10GbE card to the TS-464.

See the small business NAS setup guide for a complete walkthrough of configuring a new NAS for SMB use, and the best NAS guide for broader model comparisons.

Use our free NAS vs Cloud Migration Cost Calculator to compare the total cost of migrating from cloud to your own NAS.

Does a NAS support Active Directory?

Yes. Both Synology DSM and QNAP QTS support joining an Active Directory domain. After domain join, AD users and security groups are available for assignment in share permissions. Users authenticate with their domain credentials. This is the recommended approach for any environment with more than 5 users. It avoids creating and managing duplicate local accounts on the NAS. Synology's AD integration is generally considered more stable and better documented than QNAP's for complex domain configurations.

Will Windows offline files work with a NAS?

Yes. NAS SMB shares support Windows Client-Side Caching (offline files). Enable offline file support on the NAS share (both Synology and QNAP support this) and configure the Windows client to sync specific folders offline. Behaviour is identical to offline files from a Windows Server. For environments where users frequently work offline (laptops taken off-site), ensure the NAS share has offline caching enabled in the share settings.

How long does data migration from Windows Server to NAS take?

Migration speed is limited by the network link between the Windows Server and NAS. On a 1GbE network: approximately 100-110MB/s = 100GB/hour. A 1TB migration takes ~10 hours. On a 2.5GbE or 10GbE direct connection, proportionally faster. Schedule the initial robocopy pass during off-hours. The final cutover pass (just catching changed files since the first pass) typically takes minutes to hours depending on write activity on the old server.

Can a NAS replace Windows Server for all file server functions?

For SMB file sharing and backup, yes. A NAS handles this as well as or better than a Windows file server at significantly lower cost and power consumption. What a NAS cannot replace: print server (unless using a print server app, limited), Windows application hosting (SQL Server, IIS), Group Policy (requires remaining domain controller), full DFS namespace with multiple targets (NAS can be a DFS target but not a DFS root). For environments where the Windows Server also runs applications beyond file sharing, evaluate what roles need to remain on a Windows machine before decommissioning.

Should I use RAID on the NAS file server?

Yes. RAID is essential for a production file server. Minimum: RAID 1 (2 drives) for drive failure protection. For larger environments: RAID 5 (4+ drives) for better storage efficiency. RAID does not replace backup. Configure Hyper Backup or Hybrid Backup Sync to push copies offsite. The NAS RAID protects against a single drive hardware failure; backup protects against everything else (ransomware, accidental deletion, multiple simultaneous failures, disaster). Both are required.

Setting up a new NAS for a small business environment? The small business NAS setup guide covers Windows shares, user permissions, and backup configuration from scratch.

Small Business NAS Setup Guide →