Migration
Content moves off the file server, Google Drive or old sites in planned waves, checked file by file, with every old link sent to its new home.
- PaigeThe file server lease ends in March.
- CarlTwo terabytes. Ten years of everything.
- PaigeCan we just move what we use?
How it works.
- 01Decide what moves
Rules from age and owner: live work moves, old work is archived.
- 02Plan the waves
One team or division at a time, agreed with each lead.
- 03Move overnight
Checked file by file, with dates and authors kept.
- 04Nothing breaks
Every old link goes to the new place.
Change the archive date and watch where every file lands.
Sample data. Nothing you enter leaves this page.
What the work looks like.
Who moves when, and what is checked.
Open the sample Case study · client unnamedA field services firm gives every project one home.About 730 GB of live project files moved off the file server into SharePoint, with a register kept current from the project system and each new project’s folders and Teams channel set up in one step.
Read the case study Field NotesYour file server is 2 TB of everything. Here's what actually needs to move.Most of a typical file server is closed work. Sort it first, move only what is alive, and the migration shrinks by weeks.
Read the noteWhat people ask.
Will people have to stop working?
No. Moves run overnight, one team at a time, and each team hears what changes the day before.
What happens to the old links?
They are mapped to the new locations, so bookmarks and links inside documents still work.
Do we lose created dates and authors?
No. Dates and authors move with the files.
Plan your move.
Thirty minutes on a call. We tell you how we would start. Not sure yet? The Scan is free.