Key Takeaways
- Manual migration is fine for small, single-user transfers under roughly 10 GB with no permissions or shared links to preserve.
- Cross-tenant and business migrations need to preserve permissions, sharing links, and version history — something manual methods can’t do.
- Microsoft’s native cross-tenant migration works well for enterprise tenant-to-tenant moves but requires a separately licensed add-on and doesn’t support incremental passes.
- Dedicated migration tools close the gap for businesses that need flexibility, delta migration, and detailed reporting without PowerShell scripting.
Quick Answer
Need to move files from one OneDrive account to another? Whether you’re switching Microsoft accounts, migrating to a new Microsoft 365 tenant, or transferring employee data after a merger, the method you choose determines whether permissions, sharing links, and version history survive the move. Manual migration — downloading and re-uploading files — works for small, low-stakes transfers. Cross-tenant migrations and business environments typically need either Microsoft’s native tools or a dedicated migration platform to avoid broken links and lost permissions. This guide walks through when each approach makes sense.
When Do You Need OneDrive to OneDrive Migration?
OneDrive to OneDrive migrations come up in more situations than people expect. The most common triggers are:
- Changing Microsoft accounts — switching from a personal Microsoft account to a work account or consolidating two personal accounts into one.
- Employee offboarding — moving a departing employee’s OneDrive content to a manager or a shared location before the account is deactivated.
- Company mergers and acquisitions — combining two organizations’ Microsoft 365 environments under a single tenant.
- Microsoft 365 tenant migration — one of the most common business scenarios, and one with very different requirements from a personal account transfer. Cross-tenant moves involve identity mapping, permission preservation, and sharing-link redirects that a simple file copy can’t replicate. If you’re also weighing platform-level moves, our Google Workspace to Microsoft 365 migration guide covers the broader tenant transition process.
- Department restructuring — reorganizing who owns what data as teams change.
- Personal to Business migration — moving files from a personal OneDrive to a OneDrive for Business account as a freelancer becomes a registered business or joins a company.
- Business to Business migration — transferring OneDrive content between two organizational tenants, often during divestitures.
- Storage consolidation — merging multiple accounts to simplify management or reduce license costs.
Each of these scenarios has different technical requirements, which is why the “right” migration method depends heavily on your specific situation.
When Manual Migration Is Actually Enough
Not every OneDrive migration needs a tool. Manual migration — downloading files and re-uploading them, or dragging folders between synced accounts — is a reasonable choice when:
- The account is a personal OneDrive, not a business or shared environment.
- The total data is under roughly 10 GB.
- Only one user is involved, with no dependencies on other accounts.
- You don’t need to preserve permissions or sharing links, because nothing was shared in the first place.
- There are no collaboration features in play — no shared folders, no external guests, no linked Office files.
If all of that describes your situation, manual migration will save you the time and cost of setting up a tool. The moment any of those conditions’ changes — more data, more users, active sharing, or a business tenant — the risks described later in this guide start to outweigh the convenience.
Which Migration Method Is Right for You?
Here’s a practical starting point for matching your scenario to a method:
| Scenario | Best Method |
| Small personal migration (a few folders) | Manual |
| Personal account with large storage (100GB+) | Depends — manual is slow, a tool saves time |
| Small business (1–20 users) | Native tools or a migration tool |
| Cross-tenant migration | Migration tool or Microsoft’s cross-tenant feature |
| Personal to Business migration | Migration tool (native support is limited) |
| Hundreds of users | Migration platform with batch scheduling |
What Gets Preserved by Each Method?
This is one of the most common questions people have before starting a migration:
| Item | Manual | Microsoft Native | Migration Tool |
| Files | Yes | Yes | Yes |
| Folder structure | Usually | Yes | Yes |
| Permissions | No | Yes (cross-tenant) | Yes |
| Version history | No | Limited | Usually |
| Metadata (dates, authorship) | No | Partial | Usually |
| Shared links | No | Redirect support | Depends on tool |
OneDrive to OneDrive Migration Methods
Manual Migration
Manual migration means downloading files from the source OneDrive and uploading them to the destination or using OneDrive’s desktop sync client to move data locally before re-uploading.
Advantages: No cost, no setup, works for anyone with basic OneDrive access.
Limitations: File permissions and sharing links are not preserved. Version history is lost. Folder structures can break with deeply nested paths. There’s no progress tracking, and large migrations are painfully slow over a typical internet connection.
Who should use it: Individuals moving a small number of personal files where permissions and history don’t matter — see the section above for the specific conditions where this is a safe choice.
Microsoft-Native Tools
Microsoft offers several native paths depending on the scenario:
- Cross-tenant OneDrive migration, run through SharePoint Online PowerShell, lets admins move a user’s entire OneDrive from one Microsoft 365 tenant to anotherOnce scheduled, migrations occur without the user’s data ever leaving the Microsoft 365 cloud, requiring only a few minutes where a user’s OneDrive is read-only, and up to 4,000 OneDrive accounts can be scheduled for migration in advance at a given time.
- The SharePoint Migration Tool (SPMT) handles migrations into OneDrive and SharePoint from file shares, SharePoint Server, and other sources, though it’s built more for on-premises-to-cloud moves than OneDrive-to-OneDrive transfers. If you’re setting up SharePoint alongside OneDrive, our guide on adding SharePoint to File Explorer covers the sync relationship between the two.
- Migration Manager in the Microsoft 365 admin centre centralizes migration tasks, agents, and load balancing for larger jobs.
Limitations: Native cross-tenant migration requires a separately purchased Cross Tenant User Data Migration add-on, has strict prerequisites (no legal holds, no Customer Key encryption, accounts under 2TB or 1 million items), and offers no delta or incremental passes —cross-tenant moves are a one-and-done activity, and incremental or delta migration passes cannot be performed. That makes it a poor fit for organizations that need a phased cutover.
Migration Tip: Before scheduling a cross-tenant move, confirm target accounts are already provisioned. If a OneDrive site doesn’t exist yet on the destination tenant, the migration will fail outright — our guide on activating OneDrive user accounts before first login walks through pre-provisioning with PowerShell.
Professional Migration Solutions
When migrations involve many users, tight timelines, or complex permission structures, dedicated migration platforms fill the gaps that manual and native methods leave open.
| Tool | Best For | Limitation |
| Microsoft (native) | Native Microsoft 365 cross-tenant migrations | Requires a separate add-on license; no incremental passes |
| BitTitan MigrationWiz | Enterprise tenant-to-tenant migrations | Per-user licensing costs can add up on large projects |
| ShareGate | Organizations fully inside the Microsoft ecosystem | Primarily built around Microsoft workloads, less flexible for mixed platform moves |
| Cloudiway | Multi-cloud migrations spanning several platforms | Geared toward larger, enterprise-scale projects |
| SkyMigrate | SMB to enterprise OneDrive migrations needing permission and metadata fidelity | Best suited to organizations that want managed support alongside the technical migration |
None of these is objectively “best” — the right fit depends on your scale, budget, and whether you want a self-service tool or hands-on migration support.
Challenges of Manual OneDrive to OneDrive Migration
Manual migration looks simple until you’re partway through it. The problems tend to show up in three distinct phases.
Before Migration
- Storage quota — the destination account may not have enough free space, especially with personal-to-business moves where quotas differ.
- Invalid file names — Windows and OneDrive both restrict certain characters; files with them will fail to upload.
- File path length — SharePoint Online and OneDrive for Business have a 400-character limit that applies to file paths and file names, and deeply nested folder structures from the source often exceed it at the destination.
- Large files — very large individual files can time out during upload on a standard connection.
- Sync preparation and bandwidth — uploading large volumes manually consumes significant bandwidth and time that isn’t always accounted for upfront.
Migration Tip: Rename or archive outdated folders before migrating. Reducing unnecessary data shortens migration time and makes post-migration validation much simpler.
During Migration
- Slow uploads and internet interruptions — manual transfers have no resume capability by default.
- Microsoft throttling —Microsoft implements tighter throttling limits on background apps, including migration tools, during weekday daytime hours, and throttling can’t be disabled or suspended even through a support ticket. Manual uploads during business hours run into this just as automated tools do.
- Duplicate files and sync conflicts — re-uploading files that already exist, or syncing the same folder from two locations, creates duplicate or conflicting versions.
- Locked files — files open on another device can fail to transfer.
- Long migration time — without batching or automation, large migrations can take days of active effort.
After Migration
- Missing permissions — after migration, all advanced NTFS permissions are removed, and manual re-uploads don’t recreate any permission structure at all — everything defaults to owner-only access.
- Broken sharing links — links generated in the source account point nowhere once files are manually re-uploaded to a new location.
- Version history limitations — manual uploads only carry over the current file version, not its history.
- Metadata changes — creation dates, modified dates, and authorship metadata are often reset to the migration date.
- Missing files and folder inconsistencies — large manual migrations are prone to silent gaps that aren’t obvious until someone goes looking for a specific file weeks later.
- Validation work — someone has to manually confirm that everything transferred correctly, which is time-consuming without an audit log.
Native and professional tools reduce these risks specifically because they preserve permissions, maintain sharing link redirects, and log what was and wasn’t migrated — the exact gaps that manual migration leaves open.
Best Practices for OneDrive to OneDrive Migration
- Clean unnecessary files first. Removing outdated or duplicate files before migration reduces transfer time and destination clutter.
- Run a pilot migration. Wave-based migrations with a pilot group help validate the process before a full rollout— start with a small group, ideally with a mix of file types and sharing configurations.
- Verify storage quotas on the destination account before starting, especially for personal-to-business or cross-tenant moves.
- Schedule migration during low-usage hours to reduce the impact of Microsoft’s throttling policies and minimize disruption to active users.
- Keep the source environment intact until the destination has been validated. Don’t delete source files immediately after migration completes.
- Validate migrated files against a checklist or export of the source folder structure.
- Check permissions and sharing links specifically, since these are the most commonly missed items in manual migrations.
- Perform delta or incremental migration where supported, so files added or changed after the initial pass aren’t left behind.
- Inform users before migration, particularly around any read-only windows or expected downtime.
- Test in a non-production account first if you’re evaluating a new migration tool or process for the first time.
Common Mistakes to Avoid
- Assuming drag-and-drop or download/upload preserves permissions and metadata — it doesn’t.
- Ignoring existing sharing links and assuming they’ll carry over automatically in a manual migration.
- Forgetting that version history isn’t preserved outside of native or professional tools.
- Migrating without first checking the destination account’s available storage.
- Skipping validation and assuming the migration completed successfully just because no error appeared.
- Deleting the source account or its data too early, before confirming the destination is fully accurate.
- Ignoring how shared and collaborative files behave differently from personal files during migration.
- Migrating during peak business hours, which increases both throttling delays and the chance of files being locked by active users.
Pros and Cons at a Glance
| Method | Pros | Cons |
| Manual | Free, no setup, simple for small transfers | No permissions, no sharing links, no version history, slow at scale |
| Microsoft Native | Cloud-to-cloud transfer, sharing-link redirects, high account limits per batch | Add-on licensing required, no incremental passes, PowerShell skills needed |
| Migration Tool | Permission and metadata fidelity, delta migration, reporting and support | Cost scales with data volume or user count |
Frequently Asked Questions
Is there a free OneDrive migration tool? Manual download/upload is free but limited to small transfers. Microsoft’s native cross-tenant migration requires a paid add-on license. Most dedicated migration platforms charge based on data volume or user count, though many offer free trials for evaluation.
Can I migrate without downloading files? Yes. Microsoft’s native cross-tenant migration and most professional migration tools move data directly between OneDrive environments without the files passing through a local device. Manual migration typically requires downloading first.
Does Microsoft have a migration tool? Yes — cross-tenant OneDrive migration through SharePoint Online PowerShell, and the SharePoint Migration Tool for file shares and SharePoint Server sources. Neither is designed as a simple point-and-click OneDrive-to-OneDrive tool for smaller migrations.
Can I migrate between Microsoft 365 tenants? Yes, using Microsoft’s native cross-tenant migration feature or a third-party migration tool. Native cross-tenant migration requires a separately licensed add-on and has specific prerequisites around encryption, legal holds, and account size.
Does migration preserve permissions? It depends on the method. Manual migration does not preserve permissions. Native cross-tenant migration and most professional tools do, though advanced NTFS-style permissions are generally removed even in supported migrations.
How long does migration take? This depends on data volume, number of users, network bandwidth, and Microsoft’s throttling policies. Small personal migrations can take minutes to hours; enterprise migrations with hundreds of users are typically planned in batches over days or weeks.
Will shared links continue to work? With native cross-tenant migration, a redirect is placed at the original OneDrive location so links continue working, provided the person clicking still has access on the destination. With manual migration, shared links generally break.
Can I migrate OneDrive Personal to OneDrive for Business? Yes, though this isn’t natively automated by Microsoft in most cases. It typically requires either a careful manual transfer for small amounts of data or a migration tool designed to handle the account-type difference.
Can I migrate OneDrive without administrator access? For a personal account, no admin access is needed — you’re just moving your own files. For a business or cross-tenant migration, you’ll need either Global Administrator or SharePoint Administrator rights on both the source and destination, since the process touches permissions and site provisioning that regular users can’t access.
Can I migrate encrypted files? Standard encrypted or sensitivity-labeled files usually migrate without issue, though the labels and encryption policies need to exist in the destination tenant as well. Files protected with Microsoft Purview Customer Key encryption are not supported by Microsoft’s native cross-tenant migration and need to be handled separately.
What happens to shared folders? Shared folders migrate along with their contents, but access for the people they were shared with depends on the method. Native cross-tenant migration preserves access through identity mapping and redirects; manual migration does not carry sharing settings over, so folders default to private on the destination.
Can I migrate OneDrive on Windows 11? Yes. Both manual migration (through File Explorer and the OneDrive desktop app) and Microsoft’s native tools work the same way on Windows 11 as on Windows 10. If you’re syncing OneDrive with SharePoint libraries as part of the process, see our SharePoint File Explorer guide for the Windows 11 setup steps.
Can I continue working during migration? With manual migration, yes, but files are at risk of being locked or creating duplicate versions if edited during the transfer. With native cross-tenant migration, the source OneDrive is set to read-only for a short window — typically a few minutes — while the move completes.
Conclusion
Choosing the right migration method depends on the size of your environment, the importance of preserving permissions and metadata, and how much downtime your organization can tolerate. Small personal migrations may only require manual steps, while business and cross-tenant migrations benefit from tools designed to reduce risk and simplify validation.
Enterprise migrations, in particular, tend to go more smoothly with a platform built for the job — one that handles permissions, sharing links, and batch scheduling without requiring PowerShell scripting or a separately licensed Microsoft add-on. SkyMigrate’s OneDrive migration software is built around that need, supporting tenant-to-tenant, user-to-user, and cross-domain OneDrive migrations with full permission and metadata fidelity.
