How to migrate from SharePoint to Nextcloud
Move SharePoint Online libraries to Nextcloud team folders: inventory sites, copy with rclone, rebuild permissions and links, and plan pages, lists and flows.
In short
- A copy from SharePoint Online brings the files, their folders and their modification dates, and only the current version of each file.
- Permissions and sharing links never transfer: they are read from the site sharing report and Microsoft Graph, then rebuilt as Nextcloud team folders, advanced permissions and new links.
- Pages, lists, metadata columns and Power Automate flows stay in SharePoint unless moved on purpose, to Outline, a table, collaborative tags or n8n.
- Each site goes read-only on its cutover day before a final rclone pass, and once it closes its old links can redirect to a page that explains where the files went.
On this page (13)
Moving from SharePoint Online to Nextcloud is a copy followed by a rebuild. The files in the document libraries copy across with their folders and dates. Almost everything SharePoint keeps around them does not: permissions, sharing links, version history, metadata columns, pages, lists and Power Automate flows are each rebuilt, archived or retired, and that sorting is most of the work. This guide covers the order we do it in, from the inventory to the day each site goes read-only.
If you are leaving the rest of Microsoft 365 as well, the Microsoft 365 migration guide puts this move in its place among the other workloads.
Why teams move from SharePoint to Nextcloud
Three reasons come up most often.
- Where the sensitive files sit. Document libraries hold contracts, HR records and board papers. Nextcloud keeps them on storage you name: your own hardware, or a region you choose.
- Permissions you can explain. Years of broken inheritance and item-level sharing make “who can open this folder” a hard question in SharePoint. Nextcloud team folders take their members from directory groups, so access follows the directory and a leaver loses it everywhere at once.
- Files and pages, each in a tool built for it. Many sites mix a file share, an intranet and a few lists. Nextcloud holds the files and Outline holds the pages people read.
What you give up is SharePoint’s depth: libraries driven by metadata, content types and retention labels, co-authoring with anyone on Microsoft 365, Power Automate triggers on every library, and Copilot over your files. And where people keep a full Microsoft 365 licence for other reasons, SharePoint comes with it, so the case for moving is control over the files rather than a smaller bill.
What comes across and what does not
Copied
- Files and the folder tree of each library
- Modification dates
- The current version of each file
Rebuilt, archived or retired
- Permissions and sharing links
- Earlier versions of each file
- Metadata columns and content types
- Pages, lists and Power Automate flows
- OneNote notebooks
The concepts map onto Nextcloud like this.
| SharePoint | In Nextcloud |
|---|---|
| Site and its document library | Team folder (Group folders app) |
| Owners, Members and Visitors | Directory groups with share, write or read on the folder |
| Folder with unique permissions | Advanced permissions on that folder |
| Sharing link to people outside | Share link with a password and an expiry date |
| Version history | Nextcloud versions, from the day of the move |
| Metadata columns | Collaborative tags, or folders |
| Check-out | Temporary file lock |
| Retention labels | Retention rules on tags, for deletion only |
| Site pages | Outline collections |
| Lists | A table rebuilt from a CSV export |
| Power Automate flows | n8n workflows |
Step 1: inventory the sites
- List the sites. In the Microsoft 365 admin center, Reports, Usage, SharePoint, the Site usage tab lists every site with its owner, last activity date, file count and storage used, and counts how often files were shared through Anyone and company-wide links. It exports to CSV. Site URLs stay hidden until a global administrator clears “Conceal user, group, and site names in all reports” under Settings, Org settings, Services, Reports.
- Include the Teams sites. Every team keeps its files in a SharePoint site, and each private or shared channel has a site of its own. They are easy to miss, and often hold the most active files.
- List what sits on each site: document libraries, lists, site pages, OneNote notebooks, and the flows that use them. In the Power Platform admin center, Manage, Inventory lists every cloud flow in the tenant with the person who created it and the connectors it uses, trigger included, and downloads as CSV.
- Sort. Each site moves, goes to a read-only archive, or is retired. Sites nobody has opened in a long time are usually archived rather than moved.
Keep the export. It is the checklist the rest of the migration is measured against.
Step 2: read the permissions and sharing links
No copy tool carries SharePoint permissions across, so read them before anything moves.
- The site sharing report. On each site, a site admin opens Settings, Site usage, and runs the report under Shared with external users. Despite the name, the CSV lists every unique file, user, permission and link on the site, members and guests alike. It leaves out Anyone links, and links that were emailed but never opened.
- Microsoft Graph for the rest. The permissions endpoint returns the effective permissions on a file or folder, sharing links included, and marks inherited ones with
inheritedFrom. Run as an account that owns the content, a script over the libraries in scope finds the folders where inheritance was broken and the Anyone links the report leaves out. - Which links still matter. Owners decide which external links must keep working the morning after the switch. The rest are not reissued.
The result, per site, is a short map: which groups had which level, which folders had their own permissions, and which external links to recreate.
Step 3: prepare sign-on, groups and team folders
Before any file moves, people need accounts and groups that follow your directory.
- Sign-on. Nextcloud signs in over OpenID Connect against Keycloak or Entra ID. Its OpenID Connect app creates each account at the first sign-in and can create groups from the token’s groups claim. By default Entra ID sends group object IDs rather than names, and the app can look the names up through Microsoft Graph. Our identity services set this up.
- One team folder per site or library, created in Administration settings, on the Team folders page (Group folders in some releases). Each group gets write, share and delete rights to match the site: owners usually share and delete, members write, visitors read.
- Advanced permissions only where SharePoint had folders with unique permissions. They are enabled per team folder and allow or deny read, write, create, delete and share for a group or a user. Where someone matches several rules, allow wins, so check the result with the owner. A library full of exceptions is often better split into two team folders.
- Storage and editing. Object storage as primary storage from the first day, Redis for file locking, and Collabora Online connected and tested with your heaviest Word, Excel and PowerPoint files before anyone moves.
Step 4: copy the libraries with rclone
A browser download suits a handful of files: Microsoft caps it at 10,000 files. The OneDrive sync client would push everything through a laptop. The bulk copy runs on a server with rclone.
- Connect to SharePoint. rclone’s OneDrive backend reads SharePoint document libraries: in
rclone config, pick the site by URL or by search, with one remote per library. It runs as a migration account that can read every site in scope, or as an app registration with read-only application permissions such asSites.Read.All, granted by an administrator. The rclone OneDrive notes say which sign-in methods SharePoint currently accepts; read them before you choose. - Connect to Nextcloud over WebDAV, at
https://cloud.example.com/remote.php/dav/files/USERNAME/, with rclone’snextcloudvendor setting and an app password. The migration account is given access to each team folder, so the team folders appear at the top of its files. - Run a first pass with
rclone copywell before the cutover, while people keep working in SharePoint. Modification times are kept. rclone hides OneNote notebooks unless--onedrive-expose-onenote-filesis set, which suits most moves: notebooks get their own decision in step 6. - Check what arrived. SharePoint modifies Office files after upload, so their reported size and checksum can differ from what is downloaded, and the rclone documentation gives the flags that skip those checks. Verify afterwards with
rclone check --download, which compares the content on both sides, and compare file counts with the inventory. - Rerun as often as you like. Each pass copies only what changed since the last one. The final pass runs during the freeze in step 7.
Version history
Only the current version comes across. The Microsoft Graph versions endpoint lists the earlier versions of a file and returns their content, but SharePoint keeps them only as long as its version limits allow, and not with their full metadata. Where a library has a legal reason to keep its history, archive those versions read-only rather than replaying them into Nextcloud. Nextcloud’s own history starts at the move: a version on every change, thinning to one a week after thirty days, and never more than half the available free space.
Writing straight to disk
If a Nextcloud keeps its files on local disk, a very large copy can be written into the data directory and indexed with occ files:scan, or occ groupfolders:scan for a team folder. With object storage as primary storage, which is how we deploy it, Nextcloud needs exclusive access to the bucket, so every file goes in through WebDAV.
Step 5: rebuild access and reissue links
- Prepare the group assignments for each team folder from the map in step 2, walk them through with the site owner, and switch them on at the cutover.
- Set advanced permissions on the folders that had their own.
- Reissue the external links on the keep list as Nextcloud share links with a password and an expiry date, and tell the recipients. In the sharing settings, administrators can enforce both for every public link.
- Map the metadata that drives a process. The Graph list items endpoint returns each file’s column values. Columns that matter become collaborative tags; the Files automated tagging app tags new uploads by rule; the Retention app deletes tagged files after a set age. Retention counts age from the upload or the last change, so check what that means for migrated files before a rule goes live.
- Replace check-out with the Temporary files lock app, which lets someone lock a shared file while they work on it.
Step 6: move pages, lists, notebooks and flows
- Pages. The Graph pages endpoint, with
$expand=canvasLayout, returns the text web parts of a modern page as HTML. Outline imports Word and Markdown files, and takes HTML files dropped into a collection. Other web parts, such as news, list views and highlighted content, are rebuilt or dropped. BookStack does the same job under the MIT licence. - Lists. Each list exports to CSV, up to 30,000 rows per export, or to Excel. A list that behaves like a database becomes a NocoDB table created from that file; a simple one becomes a spreadsheet in the team folder.
- OneNote notebooks. Their pages move by hand into Outline, or the notebook is kept as an archive.
- Flows. Rebuild in n8n the flows the inventory shows still running. The owner of each one exports it from My flows, Cloud flows, Export, Package (.zip), or with its solution if it sits in one, and that export is the specification to rebuild from. n8n’s Nextcloud node reads, writes and shares files, and the method is the one in our Zapier to n8n guide.
Step 7: cut over, site by site
The cutover for one site, in order
- Pilot: Move one busy site first and fix what its owners find.
- Freeze: On the day, set the site read-only with
Set-SPOSite -LockState ReadOnly; SharePoint shows a read-only notice. - Final pass: Run rclone once more, check the counts, and open the team folder to its groups.
- Clients: Stop syncing the library in the OneDrive client and install the Nextcloud desktop and mobile apps.
- Close: After a read-only period, lock the site with
NoAccess; with a redirect address set for the tenant, old links land on a page that explains the move.
SharePoint usually comes with the Microsoft 365 licence, so there is often nothing to cancel on its own. The licences come down when the other workloads leave as well.
Running Nextcloud in production
A migrated document store needs more than a single container: PostgreSQL for the metadata, an S3-compatible bucket for the files, Redis for locking, and backups that take the database and the bucket at the same moment, because a restore needs both. Nextcloud does not skip major versions, so upgrades run in sequence, tested on a copy first.
Pilae operates Nextcloud this way, on your premises or on dedicated machines in Pilae Cloud, with daily encrypted backups stored offsite and, on Enterprise, a restore test every month recorded in the console. For a feature comparison first, see the SharePoint alternative page.
Let Pilae run the move
Pilae runs SharePoint to Nextcloud migrations at a fixed price: the inventory, the permission map, sign-on, the copy, the rebuild of pages, lists and flows that are kept, and a cutover site by site. Then we operate Nextcloud for you under a contract that, from the Business plan, includes a monthly availability commitment with service credits. See migration services for what the fixed price covers, or tell us how many sites you run and we will scope it.
Questions
What happens to metadata columns, pages, lists and Power Automate flows?
Can people keep editing in Word and Excel?
Is Nextcloud open source?
Let us run the move for you
An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.
- Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
- CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.
