ShareFile to SharePoint Online Migration moves your ShareFile account — Citrix ShareFile until 2024, a Progress product since Progress Software completed the acquisition on October 31, 2024 — into Microsoft 365: Shared Folders become SharePoint Online document libraries, each employee's My Files & Folders becomes their OneDrive, and any library a team works in can be connected to a Teams channel. What moves: folders, files, version history and timestamps where the migration tool supports them, folder permissions mapped to Microsoft 365 groups, and active shared links re-issued from SharePoint or OneDrive. What does not: ShareFile workflows, e-signature envelopes and audit trails, the client portal experience, and FTP endpoints and integrations. Fixed $2,500 for the standard scope — one ShareFile account into one tenant, up to 250 GB, 50 top-level folders and 50 employee users — delivered in 7 days; larger estates are quoted in writing from the inventory. A third-party migration tool license, where one is used, is passed through at cost, Microsoft storage add-ons are billed to you, and you pay after you approve delivery.
ShareFile is a capable secure file-exchange product, and most organizations that leave it do so for one reason: they already pay for SharePoint Online and OneDrive inside Microsoft 365 and want one place for documents, one identity, one set of sharing rules, and Teams and Copilot working on the same files. Accounting, legal and advisory firms — ShareFile's core market — are the typical callers, usually with a mix of departmental Shared Folders, per-person folders, and client-facing folders with active share links. ShareFile was a Citrix product; Progress Software completed its acquisition of the ShareFile business from Cloud Software Group on October 31, 2024, and it is sold as Progress ShareFile today. The admin console, the folder model and the API are the same product, so the method below applies whichever name is on your contract. Microsoft's own Migration Manager has no ShareFile connector (at the time of writing it reads file shares, Google Drive, Box, Dropbox and Egnyte), so we use one of two routes and tell you which at kickoff. The default is a cloud-to-cloud migration tool with a ShareFile API connector — for example CloudFuze, Movebot or DryvIQ, licensed at cost — which copies folders, files, timestamps, version history and folder permissions directly from ShareFile into SharePoint and OneDrive and supports delta passes. The alternative, for small estates where versions are not wanted, is a staged export: ShareFile content lands on a file share we control and Microsoft's Migration Manager agent moves it into SharePoint; that route carries current versions only, which the inventory states folder by folder. Either way the work runs as a pilot, a bulk pass scheduled for evenings and weekends in your region (Microsoft throttles background migration traffic harder during weekday daytime), a delta pass that catches changes made since the bulk copy, and a cutover where ShareFile goes read-only and people work from SharePoint, OneDrive and Teams. The pattern is the same one we use for Dropbox and Box moves; only the connector differs. A worked example, no customer name: a 40-person accounting firm with a 180 GB ShareFile account — 32 top-level Shared Folders (one per client group plus Tax, Audit, HR and Admin), 38 employee My Files & Folders totaling 40 GB, and around 120 client users holding share links on 9 of the folders. The inventory maps the 32 Shared Folders into 6 document libraries on 3 SharePoint sites (Clients, Firm Operations, Tax Season), with the Clients site connected to a Teams team; the 38 personal folders become 38 OneDrive accounts; the 9 externally shared folders get new SharePoint sharing links sent to the same outside people; version history moves for the client libraries and current versions only for the HR and Admin archives, which the firm chose to keep transfer volume down. That estate sits inside the standard scope, so the price is the fixed $2,500 and the schedule is the 7-day plan below. Estimate your migration: the Microsoft 365 migration estimator prices mail and file moves from Google Workspace, Exchange, another tenant and file servers at the figures printed on each service page. ShareFile is not yet one of its file sources, so for the ShareFile part use this page's figure — $2,500 inside the standard scope — and the estimator for everything else moving at the same time. The quote itself comes from three numbers you can read in the ShareFile admin console: total storage used, the count of top-level Shared Folders, and the count of employee users. Inside the caps, the quote is $2,500; above any one of them, we quote in writing from the inventory before work starts, and the method does not change — only the number of batches and days.
Confirm the three scope numbers against the ShareFile admin console, export the folder tree, the employee and client user lists and the active share links, and agree the migration route (API connector or staged export).
Map every top-level folder to a site, library or OneDrive, translate folder rights into groups, and decide version history folder by folder; you sign the mapping workbook and the permission map.
Build the sites, libraries, groups and Teams connections, migrate one Shared Folder and two personal folders, and verify counts, permissions and versions on the pilot before anything else moves.
Run the bulk copy in batches scheduled for evenings and weekends in your region, monitor throttling and retries, and resolve name, path and size exceptions as they surface. ShareFile stays fully in use.
Apply the permission map, re-issue sharing links for the external shares you confirmed, and brief your users on what changes at cutover.
Catch everything added or changed since the bulk copy, set ShareFile read-only, and switch users to SharePoint, OneDrive and Teams.
Reconcile source and target, hand over the verification report and exceptions list, and hold the closure call. ShareFile stays read-only until you decide to close the account.
7 days for the standard scope — up to 250 GB, 50 top-level folders and 50 employee users — following the plan above: inventory and mapping on day 1, pilot on day 2, bulk copy on days 3 to 5 in evening and weekend batches, delta pass and cutover on day 6, verification and closure on day 7. ShareFile stays in use until day 6. Larger estates add bulk-copy days in proportion to volume and are quoted in writing with their own timeline.
Progress. ShareFile was a Citrix product; its parent became Cloud Software Group, and Progress Software completed its acquisition of the ShareFile business from Cloud Software Group on October 31, 2024. It is sold as Progress ShareFile today. For the migration nothing changes: the admin console, the folder model (Shared Folders, My Files & Folders, employee and client users) and the API that migration tools use are the same product, so the method on this page applies whichever name is on your contract.
They are translated, not copied. ShareFile grants rights per user per folder; SharePoint grants Read or Edit to groups. We build a permission map from the ShareFile folder rights export: each top-level folder gets a readers group and an editors group (Microsoft 365 or SharePoint groups), people are placed in them according to what they could do in ShareFile, and deep per-subfolder exceptions are consolidated to the folder level you agree on. You sign the map before the pilot, and the verification report tests named people against it.
ShareFile share links and file-request links cannot be carried over and stop working when the account is closed. You confirm which external shares matter (the inventory lists every active one), and on day 5 we issue SharePoint or OneDrive sharing links for those folders to the same recipients. Outside people who need an ongoing login become Entra ID guests with access to specific libraries rather than ShareFile client users. The branded client portal itself is not recreated — see what is not included.
Yes, until the cutover on day 6. The bulk copy runs while ShareFile is fully in use; the delta pass then catches everything added or changed since. From cutover ShareFile is set read-only so nothing new lands there, and it stays read-only — not closed — until you accept the verification report and decide to end the subscription. Closing the account is your call and your action; keeping it read-only for one more billing cycle is a sensible safety net.
On the API-connector route, yes, where the tool supports it — ShareFile keeps unlimited versions by default, and SharePoint libraries keep up to 500 major versions per file by default at the time of writing. On the staged-export route only the current version moves. Because versions multiply transfer volume, the inventory marks version history in or out folder by folder; most firms keep it for live client work and skip it for archives.
Migration Manager has no ShareFile connector at the time of writing — it reads file shares, Google Drive, Box, Dropbox and Egnyte — so a direct ShareFile move needs a cloud-to-cloud tool with a ShareFile API connector, for example CloudFuze, Movebot or DryvIQ, licensed at cost and chosen at kickoff for your estate. For a small estate where versions are not wanted, we can instead stage the content on a file share and let Migration Manager finish the job, which avoids the tool license. Either route gets the same pilot, bulk, delta and verification steps.
$2,500 fixed covers everything on this page for one ShareFile account into one Microsoft 365 tenant, up to 250 GB, 50 top-level Shared Folders and 50 employee users, delivered in 7 days, with payment after you approve delivery. Not in the fee: Microsoft licenses and storage add-ons, and a third-party tool license where one is used, both passed through at cost. Above any one cap, send the three numbers from the admin console and you receive a written fixed quote from the inventory before work starts.
Every user who will own a OneDrive or open a library needs a plan that includes SharePoint Online and OneDrive. Microsoft 365 Business Basic ($84 per user per year), Business Standard ($168) and Business Premium ($264) all do — Microsoft list price, October 2026 price list, annual commitment — and so do the Office 365 and Microsoft 365 enterprise plans. Standalone SharePoint (Plan 1) and OneDrive for business (Plan 1) cover people who need only the storage. Licenses must be assigned before the pilot on day 2; Microsoft 365 Business Basic is the usual starting point for a firm that has no Microsoft 365 yet, and we can supply the licenses at list price.
They do not move. Workflows and approval rules are rebuilt in Power Automate or SharePoint as separate work if you want them; e-signature envelopes, in-progress requests and signature audit trails stay in ShareFile, while signed PDFs saved in folders move as ordinary files; the branded client portal and its file-request lists are replaced by SharePoint or OneDrive sharing links and, where needed, guest access. Professional services firms planning the target structure may find how law firms should structure SharePoint for compliance a useful read before the mapping workshop.