5users
Two to three working days
A founder, a few staff and one shared folder tree. Final pass on an evening, everyone in the new structure the next morning.
File and shared drive migration
Move the files, keep who can see them.
Dropbox, Box, OneDrive, SharePoint and Google Drive, in either direction. We design the destination structure first, then plan and run the move with Google's and Microsoft's own migration tools, mapping sharing by user and group and checking the counts before we close.
From Dropbox, Box, OneDrive or SharePoint
To Google Drive or SharePointWhat moves and where it goes
Every source, both directions.
The tool depends on where the files are and where they are going. This is what each route carries.
| From | Into Google Drive and shared drives | Into OneDrive, SharePoint and Teams |
|---|---|---|
| Dropbox | Google's data import tool, for a Dropbox business account with 1 to 100 users; personal folders to My Drive, team folders to shared drives, formats kept | Microsoft's Migration Manager, files up to 250 GB |
| Box | Box Enterprise through Google Workspace Migrate | Migration Manager; Box Notes become .docx with some elements omitted |
| OneDrive | Each user's My Drive, formats kept; sharing links mapped, one per item, the most restrictive kept | Between Microsoft 365 tenants: see tenant to tenant |
| SharePoint Online | Site collections become shared drives, libraries become folders, permissions mapped | Between Microsoft 365 tenants: see tenant to tenant |
| Google Drive and shared drives | Between Workspace accounts: see tenant to tenant | Migration Manager; Docs, Sheets and Slides converted to .docx, .xlsx and .pptx, Drawings to PNG, Forms migrated |
| Sharing | Mapped by user and group from an identity map | Shared drive permissions mapped with group mapping; file-level permissions on request |
Based on Google's and Microsoft's own migration documentation, checked October 2026. Limits change; we confirm them for your accounts during discovery.
Structure before the move
We design the destination before a single file moves.
Copying a messy Dropbox into a shared drive gives you the same mess on a new platform. A short design pass first is what makes the new home feel organized on day one.
- Personal or team, folder by folder. Work that belongs to a role goes to a shared drive or SharePoint site, so it stays when a person leaves. Personal working files go to My Drive or OneDrive.
- One space per group of people who see the same thing. Access is set on the drive or site through a group, not by one-off exceptions on folders deep inside it.
- Sensitive areas kept apart. Finance, HR and leadership get their own spaces with their own membership, instead of a restricted folder inside a space everyone can open.
- Names people can find. A short naming convention for drives, sites and top-level folders, agreed with you before the move.
- Clean-up before, not after. Duplicates, abandoned folders and over-long paths dealt with on the source, so they are not migrated, counted and paid for twice.
What does not survive
The losses, named before we start.
Every vendor tool leaves something behind. These are the documented gaps on each side, and what we do about them.
- Previous versionsGoogle's tools import the current version from OneDrive, SharePoint and Dropbox; Migration Manager moves the latest version by default. History that matters is exported first.
- Dropbox PaperNot migrated in either direction. We export Paper documents so they can live on as regular files.
- OneDrive Personal Vault and extrasPersonal Vault, Favorites, folder shortcuts and colours and expiration dates are not imported into Google Drive.
- SharePoint lists and pagesLists, web pages and permissions for identities missing from the identity map do not come across. Lists are exported to sheets.
- Items owned by outsidersFiles owned by external users stay with their owner, and external sharing links are not recreated in Microsoft 365. We list them for re-sharing.
- Shortcuts and long pathsMigration Manager skips Google Drive shortcuts and has a 400-character path limit. We shorten paths and replace key shortcuts before the move.
- Google Sites, Maps and orphaned filesNot migrated to Microsoft 365. Sites are rebuilt or archived as part of the plan.
- Box Notes and Dropbox blocked filesBox Notes convert to .docx with some elements omitted, and Dropbox files marked Blocked Download are not imported into Drive.
How a file move runs.
The same order every time, whatever the source.
Inventory
Volume per user and team space, owners, external shares, long paths, Paper documents and any version history that has to be kept.
Design the destination
Shared drives or SharePoint sites, their membership groups and the naming convention, agreed with you before the move.
Identity map
Users and groups created and licensed on the destination, matched one to one with the source, so sharing lands on the right people.
Pilot one team
A single department moved first and checked by the people who use the files, before the rest follows.
Seed, then final pass
The bulk copied in the background while everyone works from the source, then an incremental pass where the tool supports it and the source set to read-only.
Reconcile and hand off
File counts compared per space, sharing spot-checked, the losses list closed out and a one-page runbook for your next admin.
Timeline and pricing
How long it takes, and how the price is set.
Typical calendar time from kickoff to reconciled hand-off. Large file libraries add seeding time in the background, not downtime.
25users
About one week
Team spaces, groups and sharing come into play. One seeding pass, one evening or weekend switch.
100users
Two to three weeks
Seeded in waves by department with a pilot group first. The source goes read-only once, in one window.
- One fixed price per migration. Set after the discovery call from the number of users, the sources and the file volume. It changes only if the scope does.
- Licences are yours. You buy Google Workspace or Microsoft 365 directly on the plan that fits. We advise on the tier; we do not resell it.
- Included. Structure design, data migration, permission mapping, the switch window, reconciliation, a walkthrough for your team and thirty days of questions afterwards.
How we scope, quote and invoice is on how we work.
Before you decide
Straight answers.
Will sharing permissions survive?
Mostly. Into Drive they are mapped by user and group. Into OneDrive and SharePoint, shared drive permissions map by group, file-level sharing is on request, and external sharing links are not recreated.
Will Google Docs become Word files?
Yes. Docs, Sheets and Slides become .docx, .xlsx and .pptx, Drawings become PNG and Forms are migrated. Google Sites and Maps are not, and shortcuts are skipped.
Do we keep version history?
Not by default on either side. If the history of certain files matters, we export it before the move.
Can a Dropbox account go to Drive?
Yes, a Dropbox business account with 1 to 100 users through Google's data import tool. Personal folders go to My Drive, team folders to shared drives.
Is there a file size limit?
Into OneDrive and SharePoint, files up to 250 GB. Paths over 400 characters are the more common problem, so we shorten them first.
Can people keep working?
Yes. Files copy in the background, a final pass picks up recent changes, and the source goes read-only only at the switch.
Product names and logos belong to their respective owners.
Tell us where your files live and where they are going.
Thirty minutes, free. Bring the user count, the current platform and roughly how much is stored, and you leave with a route, the known losses and a fixed price.