SharePoint migration,
for the files.

The most common migration in Microsoft 365 is a department share becoming a library. Here is how it runs, and what it costs.

File servers becoming document libraries, Google Drive and Dropbox consolidating into Microsoft 365, libraries moving between sites and tenants: Mover moves the files and the folder tree into SharePoint with a free dry run first. Mailboxes, users, groups, and permissions are a tenant migration, which is a different tool. The content is the part one person finishes this month.

Run a Free Dry RunSee The SharePoint Connection
$0.15/GBat scale — no subscription, no minimums
20+sources that land in SharePoint
15 minfrom connect to first dry run
4,000+companies on Files.com infrastructure

File servers into libraries.

The big one: Windows shares, NAS appliances, and SMB shares moving into SharePoint as part of a Microsoft 365 cloud-first push. The Agent reads the share from inside the network and connects outbound, so the server is never exposed and nothing opens on the firewall.
On-premises to cloud, with SharePoint as the destination.

Other clouds into Microsoft 365.

A company that bought Microsoft 365 and still pays for Dropbox or Google Workspace consolidates. Shared drives and team folders become document libraries, structure intact, and the old subscription ends with the last incremental run.
Google Drive, Dropbox, Box, and OneDrive as sources; SharePoint as the destination.

Sites and tenants.

A reorganization moves libraries between sites; an acquisition moves them between tenants. Mover moves the content with the same dry run and the same log, and states plainly that mailboxes and identities travel on a different tool.
Cross-tenant consolidation after M&A is the second-largest SharePoint pattern.

How a SharePoint migration runs.

Six steps, in order. The cloud migration guide covers the decisions around them; this is the SharePoint path through it.

Connect SharePoint once.

Sign in to Microsoft through Mover and authorize the connection. Mover lists the sites and document libraries the account can see, and any of them is a destination or a source. The SharePoint connection.

Dry run the source first.

A free dry run walks the file share, the Google Drive, or the old library, counts files, sums bytes, exercises both credentials, and prices the exact usage pack. Fifteen years of a department share is full of surprises; find them while changing the plan is free.

Map folders to libraries on purpose.

Include and exclude rules decide what moves and where it lands. One department share into one library, the archive left behind, the temp folders dropped. The structure people live with for years is set here, on the dry run, not on the Monday after.

Move in parallel while the team keeps working.

Multi-threaded transfer into SharePoint with rate limiting tuned to what Microsoft’s side accepts, retries on transient failures that never bill, and a run log with the disposition of every file.

Incremental runs, then the switch.

A difference-aware incremental run copies what changed since the bulk pass. Repeat until the delta is minutes of work, point the team at SharePoint, run one last pass, and retire the source.

Sites and tenants too.

Libraries move between sites in one tenant, and between tenants after an acquisition, with the same dry run, the same filters, and the same log. The files and the folder tree are the job; the mailboxes and identities are not.

The SharePoint pairs.

Each pair page has the specifics for that source: what SharePoint accepts, what to watch for, and how the dry run reads it. Box and OneDrive connect the same way through the catalog.

Google Drive
Microsoft SharePoint

Google Drive → SharePoint

The Workspace → M365 standardization move for shared team content. Google Drive shared drives land in SharePoint sites the same way personal Drive lands in OneDrive.

Open
Dropbox
Microsoft SharePoint

Dropbox → SharePoint

The team-content half of a Dropbox → M365 migration. Dropbox shared folders and team folders land in SharePoint sites — same identity, same governance, same search.

Open

SharePoint migration questions.

File servers, other clouds, sites and tenants, permissions, cost, and how Mover compares with Microsoft’s own tool.

Moving content into SharePoint Online, or between SharePoint sites and tenants. In practice it is three jobs that share a name: file servers and NAS shares becoming document libraries as part of a Microsoft 365 move, other clouds (Google Drive, Dropbox, Box) consolidating into SharePoint, and libraries moving between sites or tenants after a reorganization or an acquisition. Mover does all three for the files and the folder structure.

Install the Files.com Agent on a host inside the network, scope it to the shares that move, connect SharePoint, and run the dry run. The bulk pass moves the share into the library while people keep working; incremental runs catch the changes; the cutover happens when the delta is small. The on-premises to cloud page covers the Agent path in full.

Connect both sides and run the dry run; shared drives and team folders become document libraries with the folder tree intact. The pair pages have the specifics: Google Drive to SharePoint and Dropbox to SharePoint. Box and OneDrive connect the same way.

Yes, for the files. Document libraries move between sites in one tenant and between tenants, with the dry run, filters, incremental runs, and the per-file log. A full tenant migration that also moves mailboxes, users, groups, and permissions is a different job for a suite-migration platform; Mover moves the content.

A one-time usage pack from $0.15 per GB at scale, priced exactly by the dry run, with no subscription and no minimum. Leaving a file server costs no egress; leaving another cloud may, and the egress calculator estimates it.

It depends on the bytes and on how fast SharePoint accepts them, which is the slower side of most pairs and sets the pace. The dry run counts the bytes up front. The bulk pass runs in the background; the incremental runs are short; the switch-over is minutes.

No. The bulk pass runs with the source in service. Incremental runs copy what changed since, and the switch happens when the delta is small enough to finish between two meetings.

Permissions in SharePoint follow SharePoint’s model: sites, libraries, and Microsoft 365 groups. Mover moves the files and the folder tree; plan the site and library structure on the dry run so the destination’s sharing model is set before the files arrive, rather than mapped file-server ACLs one by one afterward.

Mover and SPMTlays it out: SPMT is Microsoft’s free tool for moving file shares and SharePoint Server into Microsoft 365; Mover is a cross-cloud tool with a dry run that prices the job, a web dashboard instead of a Windows desktop application, and every other cloud as a source or a destination.

Usually nothing, which is the point of a one-time move. When the need turns out to be ongoing, keeping a file server and SharePoint in step, automating what happens when files land, or governing partner exchanges, that is Files.com, the platform Mover’s engine comes from.

See your SharePoint migration before a byte moves.

Connect SharePoint and the source, and run a free dry run. Mover counts the files, sums the bytes, and prices the exact pack. The migration starts when you say so.

Run a Free Dry RunView Documentation