Moving files is the easy part
Storage moves usually start for a simple reason: an ageing server in the corner of the office, three cloud platforms where there should be one, or a new client who works in SharePoint. The files copy across without much trouble. What goes wrong is everything around them: who can see what, links that stop working, and people opening the new system on Monday with no idea where their work went.
What we move
Office servers to the cloud. Synology, QNAP or Windows file servers moved to Google Drive, SharePoint or OneDrive.
Cloud to cloud. Any combination of Google Drive, Dropbox, OneDrive, SharePoint and Box, including moves that come with a switch between Google Workspace and Microsoft 365.
Hybrid set-ups. For video and design teams, large working files often belong on fast local storage with the rest in the cloud. Our network attached storage page covers that side.
Permissions are the hard part
Sharing does not translate cleanly between platforms. Google Drive shares files with people, SharePoint inherits access down a site, and Dropbox mixes both. Shared links embedded in documents break when the files move. Before anything is copied we map who has access to what today, decide with you what it should be, and rebuild it that way on the new platform. It is common to find a few folders shared far wider than anyone intended, and the move is the right time to fix that.
How it works
Week 1: Audit. We measure how much data there is, who owns it, how it is shared, and what is no longer needed. Old duplicates and abandoned folders are archived instead of moved.
Week 2: Design. A folder structure for the new platform that fits how teams work, with the permissions mapped to it. You sign it off before we start.
Weeks 3 to 4: Copy. A migration tool suited to the platforms involved copies the data in the background while everyone keeps working on the old system. Changes are synced again before cutover.
Cutover. Team by team, or all at once over a weekend if that suits you better. Each team gets a short note on where everything now lives, and the old system is set to read-only for a period so nothing gets saved in the wrong place.
Afterwards. We check the copy against the source, fix stragglers, and keep the old system available read-only until you are happy to switch it off.
Why Stabilise
We support the platforms on both sides of the move, so the migration is planned by the people who will look after the result. Synced folders on every Mac are set up through device management, so Google Drive or OneDrive appears in Finder on day one without anyone installing anything.
Frequently Asked Questions
Will people be able to work during the migration? Yes. Copying runs in the background on the old system, and the switch happens at a time you choose.
What happens to shared links in our documents? Links between files usually break when files change platform. We find the documents that rely on them and either fix the links or tell you which ones need updating.
How long does it take? For most small and medium companies, three to five weeks from audit to cutover. Very large data sets take longer, mostly because of the time it takes to copy.
Can you check nothing went missing? Yes. We compare file counts and sizes between the old and new systems and give you a report of what moved and where it went.
