Egnyte to SharePoint Migration: The Complete Guide

• Last updated: 09 November 2026
• Migration,SharePoint
• Editorial Team

Egnyte to SharePoint migration used to be a project you handed to a specialist and hoped for the best. Today, Microsoft’s Migration Manager, built into the Microsoft 365 admin center, copies Egnyte content directly into OneDrive, SharePoint, and Teams. It is free, it never deletes anything in Egnyte, and it supports files up to 250 GB. But Egnyte’s setup differs from Box and Google: before Migration Manager can connect, you have to create your own Egnyte API application, and before it can actually move data, you have to ask Egnyte to raise that application’s rate limits.

That setup, plus a handful of limits around permissions, versions, and external sharing, is where Egnyte migrations succeed or stall. This guide walks through the whole process, from the API app to cutover, for both SharePoint and OneDrive destinations. Every technical detail was checked against Microsoft’s current documentation, including a few places where older guidance is out of date: an earlier version of Microsoft’s own page cited a 15 GB file limit, and the current figure is 250 GB.

Why Move from Egnyte to SharePoint and OneDrive?

Organizations move from Egnyte to SharePoint and OneDrive to consolidate file storage under the Microsoft 365 subscription they already pay for, manage content with the same security and compliance tools as email and Teams, and reduce the number of platforms their IT team has to run. Egnyte is a capable platform, and many organizations run it alongside Microsoft 365 for good reasons, which our guide to how Egnyte integrates with Office 365 explains. The case for migrating usually comes down to simplification.

• One subscription. Files, mail, calendar, chat, and meetings sit in one place, so you stop paying for overlapping storage. If you want to confirm what you already own, see which Microsoft 365 plans include SharePoint.
• Files where the conversations are. Files shared in a Teams channel already live in a SharePoint site, so moving Egnyte content there removes a copy of the truth instead of adding one.
• Governance in one framework. Microsoft Purview applies retention, eDiscovery, and data loss prevention across files, mail, and chat.
• One identity. Users sign in with a single Microsoft Entra ID account instead of managing access in two systems.
• Better AI context. Microsoft 365 Copilot works across the content a person can already reach in SharePoint and OneDrive.

None of this means Egnyte did anything wrong. It means your priorities changed, and the migration should reflect that: move what people actually use, in a structure that suits SharePoint, instead of copying a decade of folders unchanged.

Is There a Free Egnyte Migration Tool?

Yes. Migration Manager, built into the Microsoft 365 admin center, migrates Egnyte documents, data, and users to OneDrive, SharePoint, and Teams at no additional license cost, and it replaced the older Mover tool for admin-led migrations. Egnyte support arrived in Migration Manager in 2022, and the tool copies content rather than moving it.

You start in the Microsoft 365 admin center, under Setup, then Migration and imports, where you select Egnyte to create a migration project. On the Microsoft side, you need to be a Global admin, a OneDrive or SharePoint admin, or hold the Microsoft 365 Migration Administrator role, and Microsoft recommends the role with the fewest permissions. On the Egnyte side, you need credentials with Read access to every Egnyte user account you plan to migrate. Migration Manager supports up to 50,000 tasks per tenant for cloud migrations. If your tenant is a government cloud, check Microsoft’s specialty environments support page, since availability differs there.

What Do You Need Before You Start?

You need an Egnyte developer account and API app, source credentials with Read access, the right Microsoft 365 role, pre-provisioned OneDrives, and a plan for the Egnyte settings that Migration Manager doesn’t carry. Our broader migration checklist covers the surrounding project.

• An Egnyte developer account. You need it to register the Egnyte Connect API application that lets Migration Manager connect.
• Source credentials. Egnyte credentials with Read access to every user account you plan to migrate.
• A Microsoft 365 migration role. Global admin, OneDrive or SharePoint admin, or the Migration Administrator role.
• Ready destinations. Users should exist and be licensed, and OneDrives must be pre-provisioned before you migrate. Otherwise OneDrive destinations will not pass validation and the migrations fail. Create the SharePoint sites and Teams you plan to use too.
• An identity inventory. List your Egnyte domains, groups, and users, because they must be mapped to Microsoft 365 counterparts.
• Cleanup. Look for restricted files, shortcut files, which are skipped, files over 250 GB, and folder trees deep enough that the destination path would exceed 400 characters.
• An Egnyte governance inventory. Migration Manager copies files, folders, and permissions. If you rely on Egnyte retention policies, legal holds, or data classification, document them now so you can rebuild equivalents in Microsoft Purview.
• A change freeze. Ask teams to stop renaming and reorganizing folders once migration begins.
• A pilot group. Pick a few users, including one with complex shared folders, to test the whole flow first.

How Do You Migrate Egnyte to SharePoint, Step by Step?

You create an Egnyte API app, request a rate limit increase, connect Migration Manager and scan, review destinations, map identities, and then migrate and monitor. Microsoft describes six steps, and the two Egnyte-specific ones come first.

• Create an Egnyte API application. Sign in to an Egnyte developer account, select Get API Key, and create a new application. Enter your Egnyte domain for testing, and select the options to issue a new key for the Egnyte Connect API and for Egnyte protect, so Egnyte generates your application key and secret.
• Request a rate limit increase. A new Egnyte application will likely be too limited to migrate content. Check your current limit in the developer account, then ask Egnyte support to raise the application’s rate limits, in calls per second and calls per day.
• Connect, scan, and copy to the migration list. In the Microsoft 365 admin center, go to Setup, then Migration and imports, and select Egnyte. Connect using your Egnyte domain, application key, and application secret, scan the folders, download the reports, and add the ones that are ready to your migration list.
• Review destination paths. Choose a OneDrive, a SharePoint site and library, or a Teams channel for each task, editing the proposed destination where needed. Pre-provision OneDrives first, and remember that a destination can’t be changed once migration starts.
• Map identities. Map your Egnyte domains, groups, and users to their Microsoft 365 counterparts so metadata and permissions migrate correctly.
• Migrate and monitor. Start the migration and watch the progress and reports. After a task completes once, selecting Migrate again runs a delta sync that copies only new or modified files.

Two details are worth keeping in mind as you work through these. Unsupported files generate item-level errors during scanning and migration but don’t change the final status of a task, so a task can show Ready to migrate or Completed even when some files won’t move. Read the reports instead of trusting the status. And because Migration Manager works folder by folder, you can scan and migrate in waves, which is how larger projects stay manageable.

Why Do the Egnyte API App and Rate Limit Matter So Much?

Egnyte limits new applications, so a brand new API app will typically connect without trouble but be too constrained to migrate real volumes of content, which makes requesting a rate limit increase the most important Egnyte-specific step. It is also the step most likely to surprise you, because everything appears to work until you try to move data.

• Create the app. In your Egnyte developer account, select Get API Key, then Create a new application. Microsoft’s suggested entries are a name such as “My migration app,” the type Publicly Available Application, and a current user base of New app, with your own Egnyte domain as the testing domain.
• Pick the right APIs. Select the options to issue a new key for the Egnyte Connect API and for Egnyte protect. Egnyte then generates the keys you will paste into Migration Manager.
• Connect. In Migration Manager, enter your Egnyte domain, application key, and application secret, and select Connect to Egnyte.
• Check your limit. Your Egnyte developer account shows your application’s current rate limit.
• Ask for more. Contact Egnyte support and request that the application’s limits be raised, stating the calls per second and calls per day you need. Microsoft’s sample request is short and specific, and yours should be too.

Treat the application key and secret like passwords, because they open access to your Egnyte data. Start the request early, since it depends on Egnyte’s support team, and build that lead time into your schedule instead of discovering it on cutover week. If you need help with the app, Egnyte’s developer support can assist.

Can You Migrate Egnyte to OneDrive?

Yes. Migration Manager can send Egnyte content to OneDrive, SharePoint, or Teams, and personal Private folders usually belong in the owner’s OneDrive while team-owned Shared folders belong in SharePoint or Teams. You choose the destination for each task.

• For OneDrive, enter the user’s email address or OneDrive URL, plus an optional folder.
• For SharePoint, enter the site URL, the library, and an optional folder.
• For Teams, select the team and the channel.
• For many tasks, upload destinations in bulk with a CSV template. Migration Manager validates the file when you upload it, and Microsoft strongly recommends completing the validation.

Pre-provision OneDrive for every user you are migrating, or the destinations will fail validation. If you are unsure where each type of content belongs, our comparison of where OneDrive ends and SharePoint begins will help. If a destination site doesn’t show up in the picker, remember that SharePoint admins only see sites where they are at least a member, new sites can take a couple of hours to appear, and the CSV upload is the reliable fallback.

How Should You Structure Egnyte Content in SharePoint?

Don’t copy a decade of folders into one giant library. Map shared folders to sites and libraries that reflect how teams actually work, keep paths short, and decide what to leave behind before you migrate. Migration Manager will copy whatever you point it at, so the design work is yours.

• Map by ownership. Send each department’s or team’s Shared folders to its own site or library, and use a Teams channel when the work is organized around a team.
• Keep folder depth shallow. A destination path over 400 characters will not migrate, and the site and library names are part of that path, so deep Egnyte trees need flattening.
• Leave dead data behind. Archive or delete content nobody has opened in years instead of paying to migrate and govern it.
• Simplify permissions. Move toward group-based access in Microsoft 365 rather than recreating every folder-level exception.
• Plan for file servers too. If you are retiring network shares as well, it is worth designing one structure for both, and our guide to moving file server shares into SharePoint covers that side.

What Carries Over from Egnyte, and What Doesn’t?

Migration Manager copies the files and folders each Egnyte user can access, in both Private and Shared folders, and re-shares them when identities are mapped, but it moves only the latest file version and does not recreate external sharing links or share with external collaborators. Anything a user can’t access in Egnyte is excluded from the migration.

• Copied. All accessible files and folders within each Egnyte user, in both Private and Shared folders.
• Latest version only. Older versions of a file are not transferred.
• External sharing. External sharing links are not recreated, and content is not shared with external collaborators.
• Skipped. Shortcut files are skipped in Egnyte migrations, and restricted files are not migrated.
• Limits. Files over 250 GB and destination paths over 400 characters are excluded.

What Happens to Permissions, Sharing Links, and Versions?

Microsoft says that when identities are fully mapped, content is automatically re-shared after migration so each user keeps access as before, but external links must be recreated by hand and only the latest version of each file moves. Each of these deserves a deliberate plan.

• Permissions depend on mapping. The re-sharing works because Egnyte users and groups are mapped to Microsoft 365 accounts. An unmapped user or group is the usual reason someone can’t open files after migration, so finish identity mapping before you start, and verify access with a pilot group.
• External sharing is manual. Migration Manager deliberately doesn’t share with external collaborators, a policy meant to protect your organization from exposing sensitive data automatically. Inventory external shares first, recreate the ones that matter afterward, and tell outside partners where files moved.
• Versions need a decision. If version history matters for legal, engineering, or regulated content, keep Egnyte available as a read-only archive for a defined period, or use a tool that supports versions.
• Notifications can be customized. Migration Manager lets you tailor the email notifications that track progress, so decide who needs to hear what.

How Do Delta Syncs and Cutover Work?

After a task completes once, selecting Migrate again runs a delta sync that compares the destination with the source and copies only new or modified files, so you can migrate in the background and catch up just before cutover. It also means you must not rearrange anything mid-migration.

• Content changes. Edits and new files in Egnyte are copied during the next incremental run, replacing the earlier versions at the destination.
• Renames cause duplicates. If a folder or file name changes, it is treated as a brand new object, and a whole folder’s worth of data can be copied again. Microsoft’s example is a path changing from /Sales/Clients to /Global Sales/Clients, which leaves two copies of the Sales folder.
• Avoid restructuring. Make major directory changes before or after the migration, never during. When sharing permissions are transferred, both owners and collaborators receive the duplicates.
• Your source stays intact. Migration Manager copies rather than moves, so Egnyte is untouched until you retire it.

A sensible cutover runs the initial migration well ahead of time, repeats delta syncs while people keep working, announces a date when Egnyte becomes read-only, runs a final delta sync, reviews the reports, and only then retires Egnyte. Our Dropbox migration guide shows the same cutover pattern for another cloud source.

Is There Another Way? Third-Party Tools and Managed Migration

Yes, but Migration Manager is the right starting point for most organizations, and third-party tools or a managed migration are worth considering when you need versions, finer permission control, or a hard deadline met without internal admin time. Capabilities and pricing vary a lot by vendor, so test any shortlisted tool against your own requirements instead of trusting a feature list.

• Migration Manager. Free, admin-led, built into Microsoft 365, and good for straightforward moves where latest-version-only is acceptable.
• Third-party migration platforms. Often add finer control over scheduling, permissions, and metadata, and some handle version history. Verify each one’s Egnyte support before you commit.
• A managed migration. A partner plans, runs, and validates the project, including the Egnyte API setup and rate limit request.

What Are the Most Common Egnyte Migration Mistakes?

The most common mistakes are skipping the Egnyte rate limit request, forgetting to pre-provision OneDrive, and rearranging folders while the migration is running. Nearly all of them come from skipped preparation.

• Skipping the rate limit request. The app connects, then the migration crawls or fails.
• Not pre-provisioning OneDrive. OneDrive destinations fail validation, and the migration fails with them.
• Leaving identities unmapped. Users then can’t open their files after migration.
• Trusting a green status. Unsupported files don’t change the final task status, so check the reports.
• Rearranging during migration. Renames and moves create duplicates on the next delta sync.
• Locking destinations too early. A destination can’t be modified once migration starts.
• Forgetting external sharing. External links aren’t recreated, so outside partners lose access without warning.
• Ignoring governance. Retention, legal holds, and classification don’t come across with the files, so rebuild them in Purview.
• Mirroring a deep folder tree. Paths over 400 characters won’t migrate.

How Long Does an Egnyte to SharePoint Migration Take?

A small environment can finish in a couple of weeks, while hundreds of users typically take several weeks including planning, the Egnyte rate limit request, and validation. The table below is a planning estimate, not a Microsoft figure, so pilot a small group to measure your real throughput.

Users	Typical Project Length
Under 25	2 to 3 weeks
25 to 250	3 to 6 weeks
250 to 1,000	6 to 10 weeks
1,000+	10 to 16 weeks or more

Large data volumes, deep folder trees, many shared folders and groups, and a slow Egnyte rate limit approval all push a project toward the top of its range.

Should You Do It Yourself or Use a Managed Migration?

Do it yourself when you are moving a modest number of users with simple sharing and have admin time for the Egnyte API setup, and use a managed migration when you have complex folders and groups, need exact permissions or versions, or face a hard deadline.

Situation	DIY Is Fine When	Managed Makes Sense When
Egnyte API setup	You have developer access and time to chase Egnyte support	You want it handled without the back and forth
Shared folders and groups	A handful, with clear ownership	Many folders, nested groups, or unclear ownership
Versions and permissions	Latest version and re-shared access are acceptable	Older versions or exact permissions must be preserved
Deadline and risk	Flexible timing	A hard cutover date or compliance requirements

If you are weighing options for a larger project, our migration services cover every layer.

Moving Other Storage Services Too?

Egnyte is rarely the only repository. We have guides for migrating Box to SharePoint, moving Google Drive to OneDrive and SharePoint, and, once everyone is in Microsoft 365, moving content between OneDrive accounts.

How Does Apps4Rent Help with Egnyte Migrations?

Apps4Rent plans and runs the full migration, from the Egnyte API setup and rate limit request to cutover and validation, so permissions, shared folders, and deadlines are handled as one project instead of a series of manual steps.

• Assessment. A review of your Egnyte folders, users, groups, sharing, restricted files, and path lengths.
• Egnyte connection. Setting up the API application and handling the rate limit request with Egnyte.
• Structure design. Deciding what lands in OneDrive, SharePoint, and Teams, and how groups and permissions map.
• Pilot and migration. A pilot first, then controlled waves with delta syncs ahead of cutover.
• Validation and support. Reports reviewed, results checked before Egnyte is retired, and 24/7 phone, chat, and email support throughout.

FAQs About Egnyte to SharePoint Migration

1. Does Microsoft have a free tool to migrate Egnyte to SharePoint?

   Yes. Migration Manager, built into the Microsoft 365 admin center, migrates Egnyte documents, data, and users to OneDrive, SharePoint, and Teams at no additional license cost. It copies content and never deletes anything in Egnyte.

2. How do I connect Migration Manager to Egnyte?

   Create an Egnyte Connect API application in an Egnyte developer account, which generates an application key and secret. Then, in Migration Manager, enter your Egnyte domain, application key, and application secret and select Connect to Egnyte.

3. Why do I need to request a rate limit increase from Egnyte?

   Egnyte imposes limits on new applications, so a new app will likely connect but not be able to migrate content at the pace you need. Check your limit in your Egnyte developer account and ask Egnyte support to raise it, stating the calls per second and calls per day you need.

4. Can I migrate Egnyte to OneDrive instead of SharePoint?

   Yes. Migration Manager supports OneDrive, SharePoint, and Teams destinations. Personal Private folders typically belong in the owner’s OneDrive, and you must pre-provision OneDrive for those users or the destinations will not pass validation.

5. Does the migration keep Egnyte permissions?

   Microsoft says that when identities are fully mapped, content is automatically reshared after migration so each user retains access as before. Items a user cannot access in Egnyte are excluded, so verify access with a pilot group before the full migration.

6. Does Migration Manager keep Egnyte file version history?

   No. During an Egnyte migration only the most recent version of each file is transferred. If you need older versions, keep Egnyte available as a read-only archive or use a tool that supports version history.

7. What is the maximum file size for an Egnyte to SharePoint migration?

   Microsoft’s current documentation lists 250 GB for Egnyte to Microsoft 365 migrations. Older documentation cited 15 GB, so ignore guides that still repeat that limit.

8. What can’t Migration Manager migrate from Egnyte?

   External sharing links are not recreated, external collaborators are not shared on migrated content, shortcut files are skipped, and restricted files, files over 250 GB, and files whose destination path exceeds 400 characters are not migrated. Items the user cannot access are also excluded.

9. How long does an Egnyte to SharePoint migration take?

   A small environment can finish in a couple of weeks, while hundreds of users typically take several weeks including planning, the Egnyte rate limit request, and validation. Pilot a small group first to measure real throughput.

10. When should I use a managed migration instead of doing it myself?

    Consider a managed migration when you are moving many users, have complex shared folders and groups to map, need older versions or exact permissions preserved, or cannot afford failed files. Apps4Rent plans, runs, and validates the whole project as one engagement.