Migrating from Dropbox to SharePoint and OneDrive without data loss

Many SMEs work with a mix that has grown that way over the years: email and Office via Microsoft 365, but files still in Dropbox or on an old shared drive in the utility cupboard. That works, until it starts to pinch. You pay for two systems, collaboration is cumbersome and nobody knows exactly who can access what where.

The logical next step: moving your files into SharePoint and OneDrive, the storage services that are already part of your Microsoft 365 subscription. In this practical guide you'll read why that's smart, what the difference is between SharePoint and OneDrive, which pitfalls you'll encounter when moving everything over and how to migrate safely without data loss.

Why switch from Dropbox to Microsoft 365?

If you're already using Microsoft 365, Dropbox or a separate file server is essentially a duplicate. Here are a few concrete reasons to make the switch.

Everything works together

SharePoint and OneDrive are built into Microsoft 365. You open a Word or Excel file straight from Teams, work in the same document with colleagues at the same time and see changes live. No more hassle with versions emailed back and forth or a folder that only exists on someone's laptop. Files, email, calendar and Teams all live in the same system.

Better security and management

In Microsoft 365 you manage centrally who can access which folder. When an employee leaves, you revoke all their access in a single action. You can enforce multi-factor authentication (MFA), label sensitive files and see who has shared what. With a standalone Dropbox or a shared drive you rarely have that overview, and that's exactly where data breaches start.

Lower costs

A separate Dropbox licence alongside your Microsoft 365 subscription is money you're spending twice. The storage in SharePoint and OneDrive is usually already included. By bringing everything onto one platform, you pay for fewer suppliers and management is simpler.

Work securely from anywhere

Files live in the cloud, not on a server you have to maintain, back up and secure yourself. Employees work from the office, from home or on the road, on a laptop or phone, without any VPN hassle. Versions are saved automatically, so a wrongly saved file is easy to roll back.

SharePoint or OneDrive: what's the difference?

This is the question we get most often. The answer is actually simple if you remember this rule of thumb: OneDrive is yours, SharePoint belongs to the team.

OneDrive: your personal work folder

OneDrive is your own, personal storage within Microsoft 365. This is where you put files you work on by yourself, drafts and documents that aren't finished yet. It's comparable to the "Documents" folder on your laptop, but in the cloud and available on all your devices. You can share a file from OneDrive with a colleague, but you remain the owner.

SharePoint: the shared workspace

SharePoint is designed for collaboration. This is where everything that belongs to the company or a department goes: project files, quotes, administration, contracts. Files in SharePoint belong to the team, not to a single person. When someone leaves, the files simply stay put and everyone else keeps access. So this is the right place for whatever currently sits in your shared Dropbox folders or on the shared drive.

For most SMEs this means: the shared folders go to SharePoint, personal files to OneDrive. A good SharePoint setup, with separate workspaces per department or project, largely determines how pleasant it is to work with afterwards. You can read more about that on our page about Microsoft SharePoint.

Common pitfalls during migration

A migration that goes wrong costs days of recovery work and creates distrust towards the new system. These are the pitfalls we come across most often in practice.

Copying the folder structure blindly

The folder structure that has grown in Dropbox over the years is often messy and too deep. Moving everything over one to one simply carries that mess along. A migration is the perfect moment to clean up and set up a logical layout, before you begin.

Shared links that break

Have you shared links to files with clients or suppliers via Dropbox? Those links no longer work after the migration. Map out in advance which external links are in use, so you can recreate the most important ones from SharePoint.

Permissions and access that don't add up

In Dropbox everyone often has more access than they need, because that once seemed convenient. Don't carry that situation over. Decide afresh for each folder who really needs access, so the new environment is secure right from the start.

File names and paths that are too long

Microsoft 365 has a limit on the total length of a file path (folder plus file name). Files buried deep with a long name can't come along. You track these down in advance and shorten them, otherwise they quietly get left behind.

Forbidden characters in file names

Characters such as \ / : * ? " < > | are not allowed in SharePoint and OneDrive. Files with such characters in their name fail during the transfer. Good preparation flags these cases in time.

Version history that disappears

With a sloppy migration the version history is lost and you can no longer retrieve old versions. With the right approach and migration tools you preserve the history where possible, so you don't lose anything.

Step-by-step plan: migrate safely without data loss

A good migration is above all a matter of preparation. Here's how we approach it.

1. Inventory. We map out what's there: how much data, which folders, who has access where and which shared links are in use. That way you know exactly what needs to happen.
2. Clean up and organise. Together we tidy up. Old and duplicate files are removed and we design a logical layout in SharePoint and OneDrive, tailored to how your team works.
3. Check for pitfalls. We track down paths that are too long, forbidden characters and other sticking points and resolve them before the migration begins.
4. Set permissions. For each workspace and folder we set out who gets access, so the new situation is secure and clear right away.
5. Test migration. First we move over a defined portion and check that everything is correct: files, structure, permissions and version history. That way surprises come to light before it really matters.
6. The actual migration. We schedule the full transfer for a quiet moment, often outside working hours or at the weekend, so your employees notice as little as possible.
7. Verification and aftercare. Afterwards we check whether all the data has come over completely. We deliberately leave Dropbox or the old drive in place for a while as a safety net, until we're sure everything is in order.
8. Guiding your team. We help your employees get to grips with the new way of working, so everyone knows where files live from now on and how to collaborate.

This phased approach is the reason a migration runs without data loss: you only push ahead once the test has succeeded and you check everything afterwards.

How IT-gemak guides your migration

A file migration is exactly the kind of job that you, as an SME without your own IT department, don't want on your plate. One mistake and you lose files or bring work to a standstill. IT-gemak takes that off your hands, from plan to aftercare.

We guide the entire switch from Dropbox to Microsoft 365: the inventory, the clean-up, setting up SharePoint and OneDrive, the actual migration and the explanation to your team. Is your data coming not from Dropbox but from a shared drive, a file server or another cloud service? Then you're in good hands with our cloud migration too. The approach is the same: careful, phased and without data loss.

As a Microsoft Partner we know Microsoft 365 inside out and we know exactly where the pitfalls are. So after the switch you work with a tidy, secure environment in which collaboration just happens naturally.

Want to know what a switch would mean for your business? Schedule a no-obligation consultation. Together we'll look at your current situation and draw up a concrete plan for a smooth migration.