Most organizations that run on Microsoft aren’t as fully Microsoft as they think they are. Teams for collaboration, Exchange for email, OneDrive for personal files, SharePoint as the intranet — and then Box, sitting quietly in the corner, holding a significant chunk of the company’s working documents. Or Dropbox, still running in the marketing department because nobody ever turned it off. Or ShareFile, embedded in the professional services workflow since before Microsoft 365 existed.
It’s an arrangement that’s felt manageable. Until Microsoft 365 Copilot changed the game — and SharePoint Copilot readiness became a strategic priority rather than a future consideration.
Copilot grounds its responses in SharePoint, OneDrive, and the Microsoft Graph. Content outside that boundary is invisible to it. Which means if your organization is running a split data estate — collaborating in Microsoft 365 but storing a significant portion of its content elsewhere — your Copilot is working with an incomplete picture of your business.
According to a 2025 Total Economic Impact study conducted by Forrester Consulting on behalf of Microsoft, organizations can achieve 116% ROI over three years from Microsoft 365 Copilot, with users saving an average of nine hours a month on routine tasks. But that return depends entirely on Copilot being able to reach your content. Every file sitting in Box or Dropbox is organizational knowledge your AI investment can’t access.
This isn’t a file management problem, more a SharePoint Copilot readiness problem. And for organizations still straddling two storage platforms, it’s becoming increasingly urgent to resolve.
How organizations end up with split data estates
It rarely happens by design. Cisco research consistently shows that around 80% of employees use technology at work that hasn’t been formally sanctioned by IT. And file storage is consistently one of the most common categories. Box gets adopted for secure client document exchange. Dropbox spreads through a team that found it easier than the corporate alternative. ShareFile gets embedded in an accounting or legal workflow and never gets rationalized.
Then Microsoft 365 arrives. Teams gets rolled out, OneDrive becomes the standard for personal files, SharePoint gets built out as the intranet — but the legacy storage platform stays, because migrating it feels disruptive and there are always more pressing priorities.
The result is a split data estate that nobody consciously chose and that most organizations haven’t fully reckoned with.
The platforms we see most often
The organizations coming to us typically fall into one of five situations:
Box — widely adopted for enterprise content management and client-facing document exchange before Microsoft 365 matured into a credible alternative. Often deeply embedded in external sharing workflows.
Dropbox — frequently a shadow IT situation that grew from individual or team adoption and never got cleaned up during the Microsoft 365 rollout. Dropbox’s revenue growth has stalled in recent years, and its product roadmap is diverging further from the Microsoft ecosystem.
ShareFile — common in professional services, accounting, legal, and financial services firms. Worth noting that ShareFile has changed ownership three times in three years — from Citrix to Cloud Software Group to Progress Software — which is creating legitimate concern among its 86,000-plus customers about long-term product direction.
Egnyte — particularly prevalent in construction, life sciences, and financial services organizations with large unstructured file estates and strong compliance requirements.
Legacy file shares and NAS — on-premises Windows file servers and network-attached storage that survived the move to cloud collaboration because migrating them was always deferred. On-premises deployments still account for more than half the NAS market, meaning this is more common than most would expect.
All five situations share the same problem: content that Copilot can’t reach.
Why SharePoint Copilot readiness starts before the migration
Microsoft has made the tooling straightforward — but SharePoint Copilot readiness requires more than moving files. Migration Manager, built into the Microsoft 365 admin center, handles Box, Dropbox, and Egnyte natively. For most organizations, the mechanics of moving content are not the hard part.
The hard part is what happens before the migration begins. Structure, metadata, and governance need to be established in SharePoint before content arrives — because the quality of Copilot’s responses is directly tied to how well your SharePoint environment is organized. Flat folder hierarchies, inconsistent file naming, absent metadata, and over-permissioned sites don’t just create a poor user experience. They actively undermine your AI.
Done properly, migration is also an opportunity to do some corporate housekeeping. It’s a chance to build the kind of content environment that makes Copilot genuinely useful — one where semantic search works, agentic retrieval surfaces the right content, and governance keeps the wrong content from surfacing in the wrong context.
This week at the Microsoft 365 Community Conference in Orlando, Jeff Teper, Microsoft’s Executive Vice President for Microsoft 365 Collaborative Apps and Platforms, confirmed that SharePoint is now the number one citation source for Copilot and agents across the entire Microsoft AI stack. The organizations moving now are the ones building that foundation. The ones waiting are the ones whose Copilot will continue to underperform.
How Cloudwell guides you through your cloud storage migration
We know migration can feel like a daunting undertaking. Having completed multiple migration projects, we’ve refined an approach that keeps disruption to a minimum and sets your SharePoint environment up for long-term success — including Copilot readiness from day one.
1. Define your migration goals
Why are you moving? What does success look like — better Copilot performance, reduced platform sprawl, stronger governance? We help you answer those questions before anything moves.
2. Audit your current environment
We review your existing Box, Dropbox, ShareFile, or Egnyte structure. We identify large files, outdated content, security risks, and map permissions to avoid issues post-migration.
3. Design your information architecture
We don’t replicate your old folder structure in SharePoint. We redesign it — using Hub Sites, Site Collections, and Teams integration to create something intuitive, scalable, and Copilot-ready.
4. Plan and execute the migration
We agree the right approach for your organization — lift-and-shift or full restructured migration — set up batch scheduling to minimize disruption, and test connectivity before anything goes live.
5. Pilot and validate
We run a test migration to catch issues early, validate data integrity, permissions, and security, and make sure your IT team and key users are prepared before cutover.
6. Drive user adoption
We provide training so your team is confident from day one using SharePoint and Copilot, with ongoing support after launch.
Frequently asked questions about cloud migration
How long does a migration from Box or Dropbox to SharePoint Online typically take?
It depends on the volume of data, the complexity of your permissions structure, and how much restructuring your information architecture needs. For most mid-market organizations, a well-planned migration runs between four and eight weeks from audit to go-live. Organizations with large file estates, complex permissions, or significant governance work required should plan for longer. The audit phase — which typically takes one to two weeks — gives you a clear picture of the timeline before any content moves.
Will we lose file metadata and permissions during migration?
Not if the migration is handled correctly. Microsoft’s Migration Manager preserves file metadata, timestamps, and permissions when migrating from Box, Dropbox, and Egnyte. The key is mapping source permissions to your Microsoft 365 user accounts accurately before migration begins — which is one of the first things we do in the audit phase. Where metadata structures differ between platforms, we work with you to establish the right taxonomy in SharePoint before content arrives.
Can we run Box or Dropbox in parallel with SharePoint during the migration?
Yes, and for most organizations a phased approach is the right one. Running both platforms in parallel during a defined transition window reduces risk and gives users time to adapt. The important thing is setting a clear cutover date and communicating it — extended parallel running tends to reinforce old habits and slow adoption of the new environment.
Do we need to clean up our existing file structure before migrating?
You don’t have to, but it’s strongly advisable and it’s something we can help you with. Moving a disorganized file estate into SharePoint replicates the disorganization — and a poorly structured SharePoint environment will undermine your Copilot performance just as much as having content in the wrong platform. We typically recommend a content audit before migration to identify what should move, what should be archived, and what can be deleted. It’s also an opportunity to establish the metadata and naming conventions that will make Copilot retrieval more accurate.
How does Microsoft’s Migration Manager work, and do we need additional tools?
Migration Manager is Microsoft’s built-in tool for migrating content from Box, Dropbox, Egnyte, and file shares into Microsoft 365. It handles scanning, assessment, scheduling, and transfer — and for most migrations it’s sufficient. For organizations with very large file estates, complex permission structures, or specific metadata requirements, specialist migration tooling can complement Migration Manager and reduce risk. We assess the right toolset during the audit phase and recommend accordingly.
What’s the difference between migrating to OneDrive and migrating to SharePoint?
OneDrive is designed for personal work files — content that belongs to an individual user. SharePoint is designed for shared organizational content — team files, departmental libraries, project repositories, and anything that needs to be discoverable across the organization. When migrating from Box or Dropbox, personal content typically maps to OneDrive and shared or team content maps to SharePoint. Getting that distinction right matters for Copilot — SharePoint is the primary citation source for organizational knowledge queries, while OneDrive handles personal file retrieval.
Cloudwell specializes in Microsoft 365 and AI readiness. Talk to us about your SharePoint migration and SharePoint Copilot readiness project. Our migration audit will help you understand what you have, what needs to move, and how long it will take.