How file servers and legacy systems move to SharePoint.
An inventory shows what comes along, a target structure takes it in, waves and a pilot carry the migration, and on cutover day the old system is switched off.
The project files of the construction department have sat on the file server for years, next to the old intranet and a dozen approval workflows from SharePoint Designer. The inventory has one row per folder, site or workflow, filled from the scans with size, last change and owner; your owners fill in the decision, target and wave columns. Running projects move, closed ones go to the archive, a folder of old scans stays behind, and every page of the old intranet is looked at once: carry over, revise or archive. Storage Monster shows stale files, versions and possible duplicates along the way, as a scan without write access. The inventory reads metadata and permissions and no document content, and we check licences and storage in the target before the first step.
02
The target structure stands before the first file moves.
Deep folder trees become sites with libraries, and metadata such as project number, phase and document type organises the documents that the path used to organise. What is information for many moves into the communication sites and hubs of the intranet, what one team works on into its team site, and Access databases or Excel lists into Dataverse or lists. Individual shares on folders are mapped to groups in Entra ID; shares that went further than needed we flag for a decision, and the owner of the area signs off every removed or narrowed share. Your owners decide the structure before the first file moves, and your team carries it on after handover.
03
A pilot goes first, waves follow, cutover day closes it.
One area with real content goes first and shows what arrives and what does not; the waves then follow in the order your owners set, areas with personal data only once groups and labels have been checked in the target. A first run transfers the inventory while your team keeps working, a second run fetches the changes since the first. An announcement, a reminder shortly before the window and a message after cutover with a short guide and a contact person make sure nobody hunts for their project folders on the first working day. On cutover day the old area goes read-only, test cases with real documents check opening, versions, search and permissions, and the inventory comparison counts per area what arrived and what was deliberately left behind. Only after acceptance does the old area move to the archive and the system get switched off.
04
Every source has its tool.
File servers as well as Google Drive, Box, Dropbox and Egnyte move with Migration Manager to SharePoint and OneDrive, SharePoint Server with the SharePoint Migration Tool, both tools from Microsoft that carry versions, authors and modification dates along. In a merger or spin-off, mailboxes, OneDrive, SharePoint and Teams move from tenant to tenant. Confluence is not on the list of sources and moves through the interface of the wiki: spaces become sites, pages become modern pages, attachments become libraries, links are rewritten, and macros need a decision per template. Whether the knowledge moves at all, you decide on these criteria:
Users: who reads, who writes, and do these people work in Microsoft 365 anyway?
Integrations: do Jira, development tools or business systems hang off the wiki, or Teams, documents and search off SharePoint?
Content: how many pages, attachments and macros, and which templates and links have to survive?
Permissions: can the spaces of the wiki be mapped to groups and sites, for guests too?
Search: does a person find knowledge and documents in one place today or in two?
Switching cost and upkeep: clean-up, mapping, links, training and operations after the move, set against maintaining two systems.
05
Old workflows do not move along, they are rebuilt.
The SharePoint 2013 workflow platform, on which many approvals built in SharePoint Designer ran, is switched off in SharePoint Online, and on SharePoint Server the 2010 and 2013 platforms are being phased out. The move is the moment to look at every workflow once: which approval is still needed, who is responsible, which deadline applies? What stays is rebuilt in Power Automate or in SP Approvals, with an accountable person, a deadline and a history; a multi-stage approval is modelled in SP Approvals, a handover between systems in Power Automate. Forms from InfoPath move into lists with forms or into an app, and every new workflow runs with a connection that belongs to a person or a service account.
06
After the decision for Server: Subscription Edition, updates, operations.
Business applications, extensions or requirements on data residency can keep SharePoint in-house. The path then leads from 2016 and 2019, which have received no security updates since 14 July 2026, to the Subscription Edition, which Microsoft carries on with feature updates such as 26H1; that one brings Document Intelligence and the modern people card to every farm and allows the Everyone claim to be excluded from the people picker. Operations follow a fixed rhythm: check the release notes, install the update in a test farm, agree functional checks and maintenance windows, then production, with recovery in the plan. What a farm needs on top, from databases to authentication, is covered on the SharePoint Server technology page; and a farm in-house gets an inventory too, because the question of which site stays, moves or goes to the archive arises there just the same.
What you decide.
SharePoint Online or SharePoint Server Subscription Edition?
Options
1SharePoint Online when Teams, partner access, Copilot or the intranet in Teams are part of the picture
2Subscription Edition when business applications, extensions or requirements keep the data in-house
3Both for a transition period, with a rule on what lives where
Our recommendation: SharePoint Online for the intranet and collaboration, because Teams, the SharePoint app, Copilot and guests run there and your IT patches no farm. The Subscription Edition for business applications that depend on extensions, on authentication in your own network or on requirements on data residency; it receives feature updates and stays supported. Both side by side only with a rule on which content lives where, so that search finds one truth. The decision rests on your customisations, your data residency and your operating model.
What we advise against: Carrying on with 2016 or 2019 because the farm still runs. Without security updates it stays on the network only as long as the move takes.
What comes along, what is cleaned up, what stays behind?
Options
1Move everything, clean up in the target
2Move what is current, archive what is outdated, leave duplicates and orphaned folders behind
3Only what changed in the last few years
Our recommendation: What is current moves, what is outdated goes to the archive, duplicates and orphaned folders stay behind, and your owners decide that per row of the inventory with size, last change and owner in front of them. The archive stays readable and gets the retention your rules require; retention periods from law or contract apply before any clean-up. What arrives in the target is what your team still needs, and search finds it there.
What we advise against: Moving everything and tidying up later. Nobody tidies up in the target, and Copilot then answers from the outdated material too.
Confluence or SharePoint for the knowledge?
Options
1SharePoint when your team works in Microsoft 365 and documents, Teams and search live there
2Confluence stays where development and Jira shape daily work
3Both, with a rule on which knowledge belongs where
Our recommendation: If your team works in Microsoft 365, knowledge in SharePoint sits where documents, Teams and search already are, with the same permissions and the same search, and Copilot answers from it. Confluence remains sensible where development and Jira shape daily work and the wiki is part of the toolchain. Decide on the criteria above, tried out with representative pages, templates and roles, and count clean-up, mapping, links and training into the move.
What we advise against: A move in which macros and templates are to be translated one to one. Every template needs a decision on what it becomes in SharePoint.
Status and sources.
As of: October 2026
Since 14 July 2026
SharePoint Server 2016 and 2019 without support.
Extended support for SharePoint Server 2016 and 2019 ended on 14 July 2026, together with SharePoint Designer 2013, InfoPath 2013 and Project Server 2016 and 2019. There are no more security updates and no support; anyone still working on these versions migrates to SharePoint Online or to the Subscription Edition.
Microsoft has switched off the workflow platform that many workflows built in SharePoint Designer ran on. We inventory your workflows and rebuild them with Power Automate or with SharePoint Approvals.
Migration Manager for file shares, Google Drive, Box, Dropbox and Egnyte.
Microsoft's own tools cover file shares and the cloud storages Google Drive, Box, Dropbox and Egnyte through Migration Manager, and SharePoint Server through the SharePoint Migration Tool. Mover is retired. For moves between tenants there is OneDrive migration; migration of whole SharePoint sites between tenants is in private preview. Confluence is not on the list of sources.
Subscription Edition 26H1: Document Intelligence and modern people card.
The 26H1 feature update of SharePoint Server Subscription Edition brings Document Intelligence and the modern people card into the standard release for all farms and allows the Everyone claim to be excluded from the people picker to avoid accidental sharing.
This is how we put it into practice: inventory, pilot, waves and inventory comparison with the tools from Microsoft, with templates to download. Data migration
The actual cutover takes a short window that we schedule with you, because the first run transferred the inventory beforehand and the second fetches only the changes since the first. Before it come inventory, decisions and target structure, after it test cases and the inventory comparison; how many weeks that adds up to depends on the number of areas and on how quickly your owners decide, and the pilot shows it for your case.
Do versions, authors and modification dates come along?
Yes. Migration Manager and the SharePoint Migration Tool carry versions, authors and modification dates, and the inventory comparison checks them per area. The target sets the limits: paths beyond the length SharePoint allows, file names with characters it rejects and very large files appear in the report as deviations and are handled one by one.
What becomes of individual shares on folders?
They are mapped to groups. For each folder with its own rights, the old individual shares sit next to the group that replaces them; shares that went further than needed go to the owner of the area for a decision. After the transfer one test person per role signs in and checks what they see. The chapter on permissions and sharing describes the model the shares move into.
Do we have to change the folder structure before the move?
Not the old one, but you set the new one: deep folder trees become sites and libraries, and metadata takes over what the path used to organise. The mapping of old folders to new targets is in the inventory, and the tool moves the content there. Folders that stay remain possible inside libraries; only the rights should no longer hang on them.
What about a SharePoint Server that still carries business applications?
Inventory, decide, separate. Sites with business applications, extensions or authentication in your own network stay on a Subscription Edition farm with a fixed update rhythm; intranet, collaboration and documents move to SharePoint Online. A rule sets what lives where, so that search finds one truth. The SharePoint Server technology page covers the operation and next steps of a farm.
Can we carry over Confluence pages with macros?
Pages, attachments and links yes, macros not one to one: every template and every macro needs a decision on what it becomes in SharePoint, a modern page with web parts, a list or a document. Before the move we check representative pages, templates and roles, and the inventory states per space how many pages and attachments move.
Next chapter · Chapter 7
Intranet cost: which levers move the bill.
How does the meter run for an intranet, and what moves the bill?