MIGRATION GUIDE
Migrate Windows File Server to SharePoint
Retiring a file server? MigrationFox moves file shares straight into SharePoint Online libraries, with their created and modified dates. Run it on MigrationFox web with the File share agent, paid with credit, or on a PC with MigrationFox for Windows. No robocopy scripts, no cloud staging in between.
2 GB free on the web, or a free 14-day trial of the Windows app · No credit card · Windows 10, 11 and Windows Server 2016 or later
How It Works
File server migration runs on a Windows server or PC inside your network, because the cloud can't reach into a private SMB share. You have two ways to do it:
- On MigrationFox web: use the File share agent. On the web Devices page, click Add a file share agent, download
migrationfox-agent.exeon a server that can open the share, and runmigrationfox-agent.exe install --token <key>as administrator. It runs as a Windows service and reads shares with the server’s computer account. You start migrations on the web, and they use credit like any web migration. - In MigrationFox for Windows: install the app on the server or a PC and run the migration there, with MigrationFox Pro or its free 14-day trial. It never uses credit. The steps below cover this option.
Either way, MigrationFox:
- Reads the share as the Windows account it runs as: yours in the Windows app, or the computer account when it runs as a Windows service
- Enumerates folders, files, and file metadata
- Streams files directly to SharePoint via Microsoft Graph, no local copy
- Reports progress back to the MigrationFox dashboard in real time
What Gets Migrated
- Files and folders: the full folder tree, including empty folders. System files such as Thumbs.db and desktop.ini are skipped
- File timestamps: created and modified dates preserved
- Long paths: paths over 260 characters handled via
\\?\prefix - Large files: chunked upload for multi-GB CAD, video, and archive files
Step-by-Step with the Windows App
Step 1: Sign up and download the Windows app
Create your MigrationFox account at app.migrationfox.com and download the Windows app.
Step 2: Install and sign in
Install it on the file server itself or any Windows PC with SMB access to the share. With Only for me, MigrationFox reads the share with your Windows account, so sign in to Windows as a user that can open every folder you want to migrate. For a server or an overnight run, install it for Anyone using this computer (or with the MSI) so it runs as a Windows service and keeps running with nobody signed in, and give the PC's computer account (DOMAIN\PCNAME$) read access to the share. A server without a browser can sign in with a token from the dashboard's Devices page. Which install should I use?
Step 3: Connect SharePoint
In MigrationFox, go to Connections → New → SharePoint and sign in with a Microsoft account that can write to the destination site. Depending on your tenant’s settings, a Microsoft 365 admin may need to approve the MigrationFox app once.
Step 4: Browse the share
Start a new migration in the Windows app, choose a file share or folder on this PC as the source, and enter a UNC path like \\fileserver01\finance. Then browse its folders and pick what to move.
Step 5: Pick a destination
Choose a SharePoint site, library and folder as the destination. Missing folders are created for you.
Step 6: Scan
Run a discovery scan. MigrationFox walks the full folder tree and reports file count, total size, longest path, and any files that would hit SharePoint's 400-character URL limit or illegal character restrictions. Scans are free and unlimited.
Step 7: Run the migration
Start the job. The PC streams files to SharePoint in parallel. Live progress, time left and per-file errors appear in the Windows app (and on the web dashboard, unless job data is kept on this PC only). For a long run, lock the screen and go home: the app keeps the PC awake, and an Anyone using this computer install keeps it going with nobody signed in.
Step 8: Final pass before cutover
On cutover day, re-run the completed job. With the default skip setting, files already in SharePoint are skipped and only new files are copied. To pick up files that changed on the share, re-run with overwrite, which replaces files that already exist. ("Only newer" incremental re-runs aren't available from a file share yet.) To script the final pass across many folders, use the MigrationFox PowerShell module.
Pricing
It depends on where the migration runs:
- On MigrationFox web (File share agent): pay-as-you-go credit, like any web migration. Signup includes 2 GB free, so a small share can be moved without a license.
- In MigrationFox for Windows: MigrationFox Pro, unlimited data, tenants and clients for a yearly license per technician. Try it free for 14 days from your first PC migration (up to 2 GB), no credit card required. It never uses credit.
The agent and Windows app downloads and discovery scans are free.
Frequently Asked Questions
Do I need to install software on the file server?
Yes, on the file server or any Windows server or PC that can reach the share. Pick one: the File share agent, added from the Devices page on MigrationFox web, runs as a Windows service and uses credit like any web migration. Or MigrationFox for Windows runs the migration on the PC with MigrationFox Pro or its free 14-day trial, and never uses credit.
Are NTFS permissions migrated?
Not yet. MigrationFox copies files and folders with their created and modified dates, but file share (NTFS) permissions don't carry over. Set access on the destination SharePoint sites and libraries before the move.
What about long paths and special characters?
The Windows app handles paths longer than 260 characters using the \\?\ Windows prefix. Characters that SharePoint rejects (*, :, ?, and so on) are replaced automatically.
Can it run overnight?
Yes. The File share agent runs as a Windows service, so web migrations keep going with nobody signed in. The Windows app keeps running with the screen locked and keeps the PC awake while migrations run. Installed for Anyone using this computer (or with the MSI), it runs as a Windows service and keeps going with nobody signed in and after restarts; the share is then read by the PC’s computer account (DOMAIN\PCNAME$).