Upgrading legacy infrastructure to Microsoft 365 is a multi-step project. Whether you are decomissioning local Windows File Shares or migrating from on-premises SharePoint Server installations, understanding the technical steps ensures data integrity and preserves access controls.

This guide details the network prerequisites, planning phases, and tooling configurations needed to execute a successful enterprise migration.

1. Running the Pre-Migration Assessment

Before moving data, you must run an automated inventory scan to flag compatibility issues.

  • For Windows File Shares: Use Microsoft's Migration Manager to run a discovery scan on your shares. This flags path lengths exceeding 400 characters, illegal characters (*, :, <, >, ?, /, \, |), and blocked file extensions.
  • For SharePoint Server (2013/2016): Download and run the SharePoint Migration Assessment Tool (SMAT). SMAT generates reports on custom master pages, site templates, customized workflows, and large list views exceeding the 5,000-item threshold that could fail to render in SharePoint Online.

2. Setting Up the Migration Infrastructure

To move terabytes of data efficiently, configure local migration agents to balance the network load.

  1. Agent Installation: Set up one or more dedicated Windows Server machines to act as migration agents. These servers must have direct access to your local shares and a fast internet uplink.
  2. Network Ports & Protocols: Ensure port 443 (HTTPS) is open outbound. Configure your local firewalls to bypass proxy servers for Microsoft 365 endpoints, as packet inspection will throttle upload speeds.
  3. High Performance Config: Assign separate file shares to separate agents in the Migration Manager console. This distributes the encryption and compression workload across your infrastructure.

3. Mapping Identity and Permissions

Preserving security schemas is critical to prevent data leaks or broken access during the cutover.

  • User Mapping: Download the default user mapping template from the SharePoint Admin Center. Map your local Active Directory (AD) security identifiers (SIDs) to Microsoft Entra ID (formerly Azure AD) principal names.
  • Permission Conversion: The migration tool converts local NTFS permissions to SharePoint security scopes. NTFS "Read" maps to "Visitor", "Modify" maps to "Member" (Edit), and "Full Control" maps to "Owner".
  • Inheritance Rules: Map root folders to separate SharePoint Document Libraries rather than creating a single large library with broken inheritance. This keeps list view performance high.

4. Execution and Staged Cutover

Avoid bulk transfers during peak office hours. Instead, configure a staged cutover schedule:

  1. Initial Bulk Pass: Run a full scan and upload of all target shares. This can take days depending on data volume. The local files remain fully interactive for users during this phase.
  2. Incremental Delta Syncs: Run delta sync tasks nightly or weekly. The migration agent compares file hashes and uploads only new, modified, or renamed documents.
  3. Go-Live Cutover: Set the local file shares to Read-Only mode. Run a final incremental sync to capture the last changes, update DNS or mapping targets, and direct users to their new SharePoint Online libraries.

Expert Cloud Infrastructure Services

Configuring Migration Manager agents, handling SMAT reports, and mapping complex NTFS permission trees requires deep system administration experience.

If you are planning to move legacy file servers or SharePoint environments, see our cloud migration services. We can manage architecture, staged transfer, permission validation and cutover.