FILE SERVERSPrivate preview

Move the file server's shares to OneDrive and Teams

The portal that empties the PCs empties the file server too. RealMigrator runs there as a service, scans the shares you point it to and copies each folder to the OneDrive or the Teams channel it belongs to.

Runs as a Windows service for file servers
OneDrive, the files of a Teams channel or Azure Blob Storage
Finalize one share at a time

DISCOVER

Tell the service where to look

Install the service on the file server with one command and the project name. In the portal you name the sources: all local drives, all local shares, or a list of paths, each scanned 1 folder level deep by default. The folders it finds are offered for selection, and each selection becomes a catalog with its own destination. By default the server migration runs only on machines with the service, so a user's PC never starts copying the file server by accident.

Example data.

HOME SHARES

Each home folder goes to its user's OneDrive

Point a catalog at the folder that holds the home folders and choose OneDrive as the destination. In home share mode every subfolder is one person's data, so the share becomes one OneDrive per subfolder: Anna's folder goes into Anna's OneDrive, Jonas's into his. A short project script tells RealMigrator which user a folder name belongs to, so naming schemes like "aschmidt" or "Schmidt, Anna" are no obstacle.

The mapping from folder to user is a short project script. Example data.

TEAM SHARES

Each department share goes into a Teams channel

A department share belongs where the department already works. Choose a Teams channel as the destination, by its link or the team's ID, and optionally a folder inside it; the share's folders land in that channel's files. If you allow it (off by default), a team can be created while the catalog is set up. File servers that should not go to Teams can still go to Azure Blob Storage.

Example data.

TIMING

Start the copy weeks before the switch

A file server is busy until its last day. These options let the copy start weeks ahead and the switch happen on one evening.

Stage OneDrive data
Files for OneDrive are first parked in Blob Storage and move into the users' OneDrives in a second step. Optional, off by default.
Teams data after the final run
Files for Teams are copied to Teams after the final run, so a channel does not fill up while people still work on the share. Optional, off by default.
Finalize one share at a time
Administrators can finalize single shares instead of the whole server: the finance share this Friday, sales next week. Optional.

WHAT STAYS

What stays on the server

Every catalog has a file selector that works as an include list or an exclude list. The default leaves out hidden files, temp files, pagefile.sys, hiberfile.sys, IconCache.db and desktop.ini. The project's path blacklist applies on the server as on the PCs, so the folders you excluded once stay excluded everywhere.

Plan the file server together with the PCs

The same portal, the same reports, the same final dates. Name your file servers in the preview request, and we look at how they fit into your project. Access is by invitation after a short qualification.

Request preview