Enterprise Cloud Storage Migration & Collaboration Modernization
Enterprise Cloud Storage Migration & Collaboration Modernization
A completed Dropbox-to-SharePoint migration, including data movement and new-user configuration, and a separate storage assessment for roughly 3 TB across 13 users that compared SharePoint, add-on storage, Azure Files and a hybrid design.
01Executive summary
Moving a business off a consumer-style file platform is less about copying files and more about not breaking how people work: links, permissions, sync clients, and the habits of every user who opens a file at 8 a.m. on Monday.
This case study covers two pieces of work that are easy to confuse, so they are kept apart here. The first is a completed migration from Dropbox to SharePoint, including data migration and configuration for new users. The second is a storage assessment for a different environment with roughly 3 TB of data and 13 users, where the question was which platform, or mix of platforms, should hold that data.
02Disciplines & technologies
Disciplines
Technologies
03The problem
Migration
The business had its working files in Dropbox while its identity, mail and licensing already lived in Microsoft 365. Two platforms meant two permission models, two sync clients and two bills, and new staff had to be set up twice.
Assessment
A separate business had about 3 TB of data and 13 users. SharePoint tenant storage scales with licence count, so a 13-user tenant does not come with anywhere near 3 TB of pooled storage. The question was whether to buy extra SharePoint storage, keep part of the data elsewhere, or redesign how that data was stored.
04Environment & complexity
What made it non-trivial
- Folder structures built over years, with deep paths and inconsistent naming
- Shared folders whose permissions did not map one-to-one to SharePoint sites
- Users mid-work during cutover: files open, sync clients running
- Local NAS copies that also fed the backup process
- Licensing tied to user count, not data volume
Constraints
- No data loss and no loss of version history that the business relied on
- Minimal disruption to day-to-day work
- Backups and retention had to keep working through and after any change
- Recurring cost had to be justifiable for a small business
05My contributions
- Planned and executed the Dropbox to SharePoint data migration
- Configured Microsoft 365 and SharePoint access for new users as part of the move
- Mapped the existing folder structure onto SharePoint libraries and permissions
- Prepared users for the change: sync client, where files live now, how sharing works
- For the assessment: gathered data volume and user counts, compared storage options and costs, and laid out a recommended direction
- Identified the NAS as both a sync endpoint and a backup source, so it could not simply be retired
06Migration approach & hybrid design
Migration lifecycle
- InventoryCatalogue top-level folders, owners, shared links and sizes. Flag paths that exceed SharePoint limits and file types that sync poorly.
- DesignDecide which folders become sites, which become libraries, and who owns each. Keep permission inheritance shallow.
- Pilot copyCopy a representative slice first and check names, timestamps and permissions on the destination.
- Bulk copyMove the bulk of the data while users keep working in the old platform.
- Delta & cutoverRun a final delta, switch users over, set the old platform read-only.
- OnboardConfigure new and existing users in SharePoint and OneDrive, sync the right libraries, confirm access.
- ValidateSpot-check files, permissions and sharing with users before decommissioning the old platform.
Assessment: options compared
| Option | Strengths | Trade-offs |
|---|---|---|
| SharePoint only | One platform, native M365 permissions and sharing, version history | 13 licences do not cover 3 TB of pooled storage; extra capacity is billed per GB per month; very large libraries sync poorly |
| SharePoint + add-on storage | Simplest for users | Recurring add-on cost grows with data, including data nobody opens |
| Stay on Dropbox | No migration effort | Second platform and permission model next to M365; separate subscription |
| Azure Files | SMB share, familiar drive-letter behaviour, tiers for colder data | Different access model from SharePoint; needs identity and network planning |
| Hybrid | Active files in SharePoint, colder data in cheaper storage, NAS kept for local copy and backup | More moving parts; needs clear rules about what lives where |
07Challenges & decisions
Why hybrid
Most of a 3 TB data set is rarely opened. Paying collaboration-tier prices for archive data is the expensive part, so active work goes where collaboration is best and colder data goes where storage is cheap.
Keep the NAS
The NAS was a sync endpoint and a backup source. Removing it would have broken the backup chain, so it stays in the design until backups are re-pointed and verified.
Sync scope
Syncing everything to every laptop is how large SharePoint libraries fall over. Users sync the libraries they work in, and the rest is opened on demand.
Do not migrate everything
Moving dead data costs time and money and makes the new platform harder to search. Archive first, migrate what is in use.
08Outcomes
- Verified
Dropbox to SharePoint: data migration completed.
- Verified
Dropbox to SharePoint: new users configured in Microsoft 365 / SharePoint.
- Design / evaluation
3 TB / 13-user environment: storage options assessed and a hybrid direction recommended. This is an assessment, not a deployment.
- Pending verification
Decommissioning of the old platform and final user sign-off are pending confirmation.
- Not documented
No cost savings or productivity figures are claimed.
09Lessons & capabilities
- Migration success is measured on Monday morning, not when the copy job finishes
- Licensing math belongs in the first meeting, not after the data is moved
- Every local copy may be part of a backup chain; check before retiring it
- Keep assessments and deployments separate in documentation so nobody mistakes one for the other