Service

SharePoint
Migration

Move from on-premise SharePoint Server to SharePoint Online — migrating sites, document libraries, lists, pages, and permissions with complete structural fidelity.

Overview

What this migration involves

SharePoint migrations are structurally complex. SharePoint Online has architectural differences from SharePoint Server that require careful planning and mapping before migration begins.

CloudyNex assesses your SharePoint Server environment in detail — cataloguing sites, subsites, content types, custom solutions, and workflows — then builds a migration plan that preserves what matters. Still on SharePoint 2016 or 2019? Both reached end of support on 14 July 2026, with no extended security update option.

What we migrate
  • SharePoint sites and subsites
  • Document libraries and lists with content
  • Site permissions and security groups
  • SharePoint pages and web parts
  • Content types and managed metadata
  • Custom list configurations
How It Works

The migration path

A clear, structured path from source to destination — with CloudyNex managing every step.

SharePoint Server (On-Prem)
Sites · Libraries · Lists
via CloudyNex
CloudyNex
Migration engine
arrives at
SharePoint Online
Microsoft 365 · Always on
Business Challenges

What makes this migration complex

01
Custom solutions and workflows

On-premise SharePoint often has custom-built workflows and solutions that do not exist in SharePoint Online. These must be catalogued and either rebuilt or replaced during migration.

02
Permission inheritance

SharePoint permission inheritance is complex. Unique permissions at item, library, and site level must be carefully mapped to avoid access gaps post-migration.

03
Large site collections

Very large site collections with millions of items require staged migration approaches and careful management of API throttling limits.

Our Process

How we run the migration

01 — Inventory
Site inventory
Full inventory of sites, subsites, document libraries, list items, custom solutions, and workflows.
02 — Assessment
Compatibility check
Each site assessed for SharePoint Online compatibility. Blocking issues, custom solutions, and workflow dependencies identified.
03 — Planning
Migration plan
Migration batches defined by site collection. Permission mapping documented. Custom solution rebuild plan agreed.
04 — Pilot
Pilot site migration
Representative site collection migrated to validate tool configuration, permission mapping, and content fidelity.
05 — Migration
Batch migration
Site collections migrated in planned batches. Content verification run after each batch before proceeding.
06 — Hypercare
Post-migration
7-day support. Permission verification checks. Source farm maintained until sign-off.

Need help with this migration?

Contact our migration specialists today.

Request a Free Consultation
FAQ

Frequently asked questions

SharePoint 2010 and 2013 workflows cannot run in SharePoint Online and must be rebuilt as Power Automate flows. We catalogue all workflows during discovery and advise on the rebuild approach.
Yes. Site, library, and item-level permissions are migrated. We conduct permission verification checks post-migration to confirm access is correct before decommissioning the source.
Farm solutions and sandbox solutions cannot run in SharePoint Online. These are catalogued during discovery and either rebuilt as modern SharePoint Framework solutions or replaced with equivalent functionality.
Get Started

Ready to move SharePoint
to the cloud?

Tell us about your environment. We will assess the complexity and give you a clear, written migration plan.

No commitment required · Response within one business day · sales@cloudynex.co