From File Server To SharePoint: Copy Or Reorganize?

Reorganize before you migrate. A file server is usually arranged around drives, folders, and inherited permissions. SharePoint works best when its structure reflects purpose, ownership, collaboration, access, and information lifecycle.

Plan the migration as an information and adoption project, with technology supporting the agreed working pattern.

Recommended Approach

Do not migrate everything first and decide how to organize it afterward. Work in manageable areas, such as a department, process, or project. For each area, decide what to keep, who owns it, where it belongs, and how people will work after the move.

Do not automatically move existing disorder to a new platform.

Migration Flow

Reserve Time And Capacity

A schedule based only on file count and transfer speed is incomplete. The technical copy is only one part of the work. Reserve named people and working time for:

inventory and content decision workshops;
owners to review, reorganize, and approve their information;
target structure, access, retention, and security design;
remediation of files, links, identities, and application dependencies;
pilot testing, feedback, and design changes;
communication, task-based training, and instructions for each audience;
cut-over validation, user support, and post-migration improvements.

These are planned project activities, not tasks for owners and Key Users to fit around their regular work. Agree on decision deadlines and escalation routes, and give each migration wave contingency for findings from the previous wave. Use the pilot to estimate the review and support effort; the number of files alone does not predict that effort.

If the people who understand the content have no scheduled capacity, the migration will wait for decisions even when the technology is ready.

1. Define Scope And Decision Rights

Start with the people who can make content decisions. A migration team cannot determine by itself whether an old contract may be deleted or whether a project folder should become a separate site.

For each migration area, assign:

a business owner who decides what is needed and who should have access;
a migration lead who plans scans, test runs, waves, and issue handling;
an IT or Microsoft 365 owner who prepares destinations, identities, security, and support;
a records, legal, or security contact when retention, confidentiality, or regulatory requirements apply.

Record the decision, approver, and date for deletion, archiving, destination, and exceptional access. This prevents technical staff from becoming the accidental owner of business information.

2. Inventory And Assess The Source

Use two complementary assessments. The business inventory explains what the content means; the technical scan shows what might fail or require remediation.

Business inventory	Technical inventory
Owner and users	File and folder count
Purpose and document types	Total size and large files
Active, historical, or obsolete	Last modified date
Confidentiality and retention need	Path length, names, and file types
Required access	Existing source permissions
Business applications and processes	Links, macros, and other dependencies

Treat existing permissions as evidence, not as the target design. Years of exceptions and individual access entries can hide the intended audience. Ask the owner to confirm who needs read, edit, or owner access in the new location.

Microsoft Migration Manager can scan and assess file shares and produce summary reports and detailed logs before migration. Use those results to find technical blockers, but do not expect a scan to decide ownership, value, or retention for you.

Check The Intended Target

Check whether the source files meet the destination requirements, including the planned site and library paths:

The complete decoded target path, including the file name, is no longer than 400 characters.
Each file is within the 250 GB upload limit. Check the chosen migration tool's limits separately.
Names pass the current restrictions for invalid characters and reserved names, such as CON and NUL.
Count unique permission scopes, where content has its own access rules instead of inheriting them. SharePoint supports 50,000 per list or library; Microsoft's general recommendation is 5,000. Prefer far fewer exceptions.

The path, size, and supported permission limits come from SharePoint service limits. Check OneDrive and SharePoint name restrictions before setting rename rules. A supported maximum is not a design target.

The 5,000-item List View Threshold is a separate query threshold, not a hard folder capacity. Test indexed columns and filtered views with realistic volumes, following Microsoft's List View Threshold guidance. Use SharePoint 5,000 Item View Threshold Explained for the differences between views, search, synchronization, and automation.

Set Migration Tool Acceptance Criteria

Choose a tool against the migration requirements. Require evidence that it can:

scan without copying and export detailed findings;
map sources to destinations and support the approved restructuring;
map identities and permissions, with documented handling of unsupported rules;
run initial and incremental copies with predictable handling of existing or changed files;
report failures, support retries, and account for expected, migrated, and excluded content.

Prove these requirements in the pilot. Record manual steps and unsupported cases, with an owner and an agreed solution, before accepting the tool for wider use.

Distinguish User Data From Application Data

First check who uses the information: a person, an application, or both. Then choose the new storage location. The file type and current folder alone do not tell you enough.

Use pattern	Excel example	What to arrange
User data: people use the information themselves	A team edits a budget and discusses the figures	Choose shared storage. Assign an owner and show the team how to use it
Application data: software reads or writes data in the file	An application imports an Excel file. A user may start the import manually	Test whether the application can find, open, and process the file
Mixed use: people and applications use the same file	Staff enter data in a workbook. Another workbook, macro, or application uses that data	Test all files, links, and processing steps involved

User data can also belong to a team. Check before putting team files in one person's OneDrive. An Excel file can be used by both people and applications.

You can teach users where to find their files after the move. For applications, you need to update fixed paths. Sometimes you also need to change or replace the application. Then test whether the whole process still works.

If an application only accepts local file paths, keeping its data in SharePoint may require synchronization. The application needs the local copy to do its work. Synchronization does not make those local paths identical across users. Check whether the application supports cloud access before choosing this approach.

Example: Power Query Reads A Local File

User A creates a Power Query import in Summary.xlsx. The query reads Source.xlsx from a synchronized project folder. User B opens Summary.xlsx and tries to refresh the query. Both users have the source file, but its local path differs:

User	Local source path
User A	`C:\Users\userA\OneDrive - Contoso\Project A\Source.xlsx`
User B	`C:\Users\userB\OneDrive - Contoso\Project A\Source.xlsx`

The query still points to user A's local path. User B may not have that location or permission to read it. Refresh can therefore fail even though both files are fully synchronized. Synchronizing the source folder does not by itself change the query's source.

For this import, I recommend the Power Query SharePoint Folder connector:

In Excel, choose Data > Get Data > From File > From SharePoint Folder. Microsoft describes this option in its Power Query import guidance.
Enter the SharePoint site URL, for example https://contoso.sharepoint.com/sites/Projects. Use the site address, without a library or file path.
Sign in with an organizational account that can read the source. Filter the returned files to the intended folder and Source.xlsx before importing its data.
Select the required table or sheet. Check the query's transformations and load the result into Summary.xlsx.

The query now reads the source through SharePoint. Its source no longer depends on C:\Users\userA\... or a synchronized source folder. Each user still needs a working connection and access to the source. Test refresh as user B after changing and saving a value in Source.xlsx on SharePoint. Compare the result with that new value, rather than trusting data already loaded in the workbook.

For an existing query, update its source and check the later steps. A SharePoint folder connection returns a list of files. Select the intended file before processing its contents. Merely replacing a local path with an HTTPS address is not enough to change a local-file query into a SharePoint folder query.

Distinguish Power Query From Workbook Links

Power Query imports and transforms data. Workbook links refer to cells in another workbook. Changing the Power Query source does not automatically repair those links, macros, or other applications that expect local paths.

Excel can also store workbook links as relative paths. These links can keep working if the relative folder structure stays the same. A full path in the formula bar does not always mean Excel stored an absolute path. Check how the link is stored and how users open the workbooks.

For cell references between workbooks, Excel also supports workbook links using SharePoint and OneDrive addresses. For shared workbooks, I prefer these supported cloud links over links tied to a Windows profile. Create or repair the workbook link in Excel. Each user still needs access to the source workbook. Check whether link refresh is enabled, and test that changed source values appear. Other applications cannot always use these cloud access methods.

Include the organization's Excel version, workbook links, queries, macros, and imports in the process tests below.

Check How The Application Signs In

On a Windows file share, an application can often use the signed-in user's account. This can work through Kerberos authentication. A service or scheduled task may use a different account. Record which account reads and writes each file.

Access in the browser tells you little about access from an application. The application cannot automatically use your browser's sign-in cookies. It must support a way to sign in, for example through a connector. It also needs the right permissions.

Access through Microsoft Graph requires an access token. An application can act on behalf of a signed-in user (delegated access) or use its own identity (app-only access). Check which method the application supports.

Prevent Unplanned Synchronization Workarounds

If an application cannot open files in SharePoint, users may start synchronizing them. The application then uses a local copy. Work can become dependent on one staff member, computer, and sync client.

Have the application owner and IT approve this approach before the move. Check the security of the device and files. Agree on how to keep files up to date and restore them if needed. Also check whether work can continue without that staff member or computer. Follow the controls for synchronization and local data.

With approved synchronization, the sync client signs in to SharePoint. The application uses the local copy and gains no direct access to SharePoint. Include the time needed for changes to reach the next processing step in the process test.

Map Work Process Dependencies

Check both Office and non-Office applications. Some need a local or mapped path, a fixed folder name, or a service account. An application may also need to lock a file while it edits it. A sync client can sometimes provide a local path.

Trace each critical process from task to application, file, identity, and path. Test the complete task with the real Office or non-Office application. Opening the migrated file alone does not prove that linked files, imports, or background processing work.

Apply the same assessment to services, integrations, databases, and shared application data. Check their sign-in method, access requirements, and concurrent use before choosing cloud access, approved synchronization, or another storage design.

Complete this checklist before scheduling the affected migration wave:

Name the process owner, users, criticality, and acceptable outage.
Record every application, automation, macro, integration, service account, and scheduled task that reads or writes the files.
Record who uses each file: people, applications, or both. Note which other files depend on it.
Record mapped drives, fixed paths, shortcuts, input folders, output folders, and embedded links.
Record the account or application identity used by each application or task. Check how it signs in and which permissions it needs.
Test concurrent use, file locking, offline use, Files On-Demand, and the target path with the real application.
Choose and approve one outcome: use the browser, use a supported synchronized path, change the application, replace the process, or keep the dependency on managed storage temporarily.
Have the application owner and IT approve any use of synchronization. Check device security, up-to-date files, and how work continues without the usual user or device.
Define monitoring, support, rollback, and a date for removing any temporary exception.

3. Choose The Destination

Choose a destination for each coherent work area, not for the entire drive at once.

Information pattern	Recommended destination
Work files owned by one person and not yet part of a team process	OneDrive
Documents that a defined group actively creates and maintains	A Teams-connected SharePoint team site
Published reference information for a broad audience	A SharePoint communication site
Formal documents with a defined process, owner, and access model	A governed SharePoint site or document library
Application data or files used by both people and applications	Test the whole process first. Use SharePoint if the application supports it, or storage designed for the application. If you keep files elsewhere temporarily, assign an owner and an end date
Information that must be retained but is rarely used	An approved records or archive solution based on retention and access requirements
Obsolete, duplicate, or ownerless content with approved disposal	Do not migrate it

OneDrive, Teams, and SharePoint are not interchangeable folders. The destination determines ownership, lifecycle, access, and how people find and use the content. See Where Should This File Live? for the underlying choice.

Use a governed communication site or nongroup-connected SharePoint site when the organization must centrally manage publication, membership, or access. Use a group-connected team site when a defined group should collaborate and its owners can be accountable for membership. SharePoint does not keep ownership central by itself; the site type, groups, owners, and sharing settings create that operating model. Follow Govern Sharing In SharePoint before selecting the final destination.

Archive Is A Lifecycle Decision

Do not call content an archive merely because nobody uses it. Confirm its owner, required retention period, access needs, legal holds, and approved disposal process. Configure Microsoft Purview retention for SharePoint and OneDrive where policy or regulation requires it.

Use Which Microsoft Purview Solution Should You Use? when migration decisions also require sensitivity labels, DLP, records, evidence, or investigation controls.

4. Design The New Structure And Access

Do not automatically turn every top-level folder into a site. Create a site when content shares a clear purpose, owner, audience, and lifecycle. Use a separate site when the security boundary or ownership is materially different.

Use Site, Library, Or Folder: Where Should You Organize Documents? to work through this design before creating migration destinations.

Within a site:

use document libraries for distinct content sets or management rules;
keep folders understandable and reasonably shallow;
add metadata when people need to filter, group, search, or manage documents across folders;
prefer groups and inherited permissions over individual access and many exceptions;
define at least two suitable owners for important workspaces;
agree on naming, navigation, versioning, sharing, retention, and review before migration.

Make the structure explainable to a new employee without relying on knowledge of the old drive.

Govern Membership And Access

Verify Access Previously Blocked By Deny

The SharePoint Migration Tool permission guidance states that special permissions such as NTFS Deny are not preserved. A user excluded on the source could gain access through another permission on the destination. Verify other tools' behavior separately.

Record these exclusions and have the business owner approve the replacement access design. In the pilot, test that excluded users cannot open the affected content.

Keep Membership Correct When Roles Change

File-server access is often based on groups maintained by IT or identity management. A group-connected SharePoint team site or Team can let workspace owners manage membership. If that membership does not follow an authoritative joiner, mover, and leaver process, a role change can leave someone without required access or with access that should have ended.

Assign who updates membership for each event, which identity source they use, and who checks that the change is complete.

For every destination, record whether membership is centrally managed, owner-managed, or hybrid. Name the business owner, at least two workspace owners, the identity source, the approver, the exception route, and the review date. Use Permissions And Ownership for the responsibility model. Check Microsoft's sharing and permissions guidance for membership management in group-connected sites and Teams.

Review all access paths. Direct file or folder sharing can create unique SharePoint permissions, and private or shared Teams channels use separate SharePoint sites. Check members, guests, sharing links, direct access, and channel sites separately. Follow Govern Sharing In SharePoint and Microsoft's Teams and SharePoint integration guidance.

Review Broad Access Before Copilot

Microsoft 365 Copilot respects existing permissions, but it can make accessible information easier to find and reuse. Before a broad rollout, correct oversharing, ownerless content, and obsolete access. Microsoft's secure and governed data foundation for Copilot explains the preparation.

Use Purview to discover, classify, and protect sensitive information. Labels do not replace access remediation, and a site or group label does not automatically label the files inside it. Check the scope of sensitivity labels for groups and sites.

Check for Everyone except external users access at site, library, folder, and file level. Have owners confirm where organization-wide access is intended and remove it elsewhere. Microsoft's data access governance reports can help identify broad sharing; check the reporting prerequisites before using them.

During a permissions review, consider Restricted Content Discovery for selected sensitive sites. It temporarily limits discovery in organization-wide search and Copilot. It does not change permissions or prevent direct access by an authorized user. Check the current licensing and administrative prerequisites, assign a review owner, and remove the restriction after access remediation is accepted.

5. Control Synchronization And Local Data Risk

I recommend this access order for shared documents:

Start from SharePoint or Teams.
Use a OneDrive shortcut when the task requires File Explorer. Select only the folders needed.
Use full library Sync only for a documented, approved exception.

Starting from SharePoint or Teams can include browser editing or opening files in a supported desktop app. Check the app's requirements. The Open in app feature described by Microsoft requires the OneDrive client and Files On-Demand.

Microsoft recommends OneDrive shortcuts over the Sync button. Shortcuts are available across devices; Sync connects a library to a specific device. Microsoft also reports better performance for shortcuts.

For File Explorer access, both methods use the OneDrive sync client. A shortcut can cover a specific folder or an entire library. Select only the content needed for the task. A shortcut alone does not reduce the amount synchronized.

For example, a team needs only the Project A folder. Add a shortcut to that folder rather than the library containing every project. Changes to Project A still synchronize through OneDrive. The shortcut limits the content involved; it does not remove the synchronization behavior.

Choose One Method Per Library

You cannot combine Sync and Add shortcut to My files for the same SharePoint library. This also applies when the shortcut targets a folder within that library. Follow Microsoft's explanation of this restriction.

Understand Shared-Library Conflicts

Each device tracks local files and changes. A saved change on one laptop may not have reached SharePoint yet. Another person can keep working with the version already there. Microsoft documents sync conflicts during offline or concurrent editing.

This can also happen with personal files across several devices. Shared libraries add other people's edits and folder moves. OneDrive has to keep those changes aligned across everyone's devices.

Example: A Connection Drops During Editing

User A opens Budget.xlsx from a synchronized project folder. Their Wi-Fi or VPN connection drops. They keep editing the local file, but their changes no longer reach SharePoint.

User B opens the same workbook from SharePoint. They change the figures and save. Their changes reach SharePoint while user A is still working offline.

When user A reconnects, OneDrive has two sets of changes to handle. Supported apps and formats can merge changes through co-authoring. Some changes need manual review or a separate saved copy. The result depends on the application, file type, and when changes arrive. A successful upload alone does not prove that both people's intended changes remain. Check the figures as part of the pilot.

Example: A Folder Moves While A File Is Open

User A moves Projects/Project A to Completed/Project A. User B still has Budget.xlsx open from the original folder on their laptop. The move reaches SharePoint before user B's device receives it.

User B saves their work. Their application may still use the old path. OneDrive now has to process the folder move and user B's saved changes. If the application creates a file at the old path, files can remain in both locations. A duplicate or part of the old folder structure can then appear. Some applications handle the move without this problem. Test the actual application before accepting the working pattern.

An application can also block synchronization while a file is in use. Plan large moves when colleagues can close the affected files. Let pending changes finish synchronizing before reorganizing shared folders.

More Situations To Include In The Pilot

Use the examples that match the team's work:

Situation	What to check
Someone uses a desktop and a laptop that has been offline for days	Save different changes on both devices. Reconnect the laptop and check which changes reach SharePoint
A laptop goes to sleep before an upload finishes	Resume the laptop and confirm that the pending changes arrive before another person continues
Someone moves or renames thousands of files during daily work	Check open files, pending changes, and the resulting folder locations
An application, antivirus tool, DLP tool, or backup tool holds a file open	Check whether the file is locked and whether synchronization resumes after it is released
Colleagues edit the same non-Office file	Verify whether the application supports co-authoring and how it handles conflicting saves
A large library has many pending changes, or the client is outdated or shows errors	Check client health and whether changes finish syncing within the team's required time
Someone copies a synchronized folder into another synchronized location	Check which copy colleagues edit and whether they can identify the agreed working file
Someone reconnects OneDrive, or loses and later regains library access	Check what happens to pending local edits when synchronization resumes

Before choosing another sync client, review the process and storage choice. Another client still has to handle user A's offline edits and user B's changes. It must also handle folder moves and applications using old paths. Assess its support, security, administration, and costs against the requirements. Use the application and process assessment before approving it.

Protect Local Data And Plan Recovery

Oversharing can expose information to unintended people. Synchronization can also affect the files themselves: OneDrive synchronizes additions, changes, and deletions between the device and the cloud. An accidental deletion, destructive application, or compromised device can therefore affect the shared cloud copy and other synchronized devices. Treat synchronization as an access method, not as a backup.

Risk	What can happen	Required design response
Oversharing	Broad membership, direct permissions, or links expose information to unintended people	Remediate access and follow Govern Sharing In SharePoint
Local exposure	Locally available or always-available files can be read through an unlocked or compromised user session	Require managed device controls, disk encryption, screen locking, incident response, and appropriate download restrictions
Propagated deletion or damage	A synchronized deletion or modification can reach SharePoint and other devices	Configure versioning and recovery options, and test the recovery procedure
Excessive synchronization	Large libraries, too many synchronized items, or widespread offline copies can affect storage, network use, and sync reliability	Synchronize only what the work pattern requires, use Files On-Demand, and test against the current OneDrive and SharePoint limits
Incompatible process	An application expects a mapped drive, fixed path, locking behavior, or local data file	Resolve the dependency before cut-over or keep an explicitly managed temporary exception

Files On-Demand can keep file contents online until needed. Users can make files always available, and applications can download online-only files when they access them. Treat this as a storage and synchronization control, not a security boundary.

SharePoint permissions do not by themselves protect every downloaded copy. Require managed and compliant devices, device encryption, strong sign-in and locking, and appropriate controls for unmanaged devices.

When the information risk and licensing justify them, add Purview sensitivity labels with encryption, protection that extends SharePoint permissions to downloaded files, or Endpoint DLP. A classification-only label does not stop someone using an authorized, unlocked session from reading the file.

Before enabling synchronization for a site or library:

Approve which roles need synchronization and which libraries they need.
Keep Files On-Demand as the normal pattern and document justified offline exceptions.
Check item counts, path lengths, available storage, bandwidth, and the current synchronization limits.
Confirm the device-management, encryption, lock, remote-action, and unmanaged-device requirements.
Decide whether sensitive files need encryption, extended protection on download, Endpoint DLP, or a no-download pattern.
Test deletion, version restore, recycle-bin recovery, and the incident escalation route.
Include removal of synchronized data and access in the leaver, lost-device, and device-replacement processes.

6. Clean Up And Remediate

Have the business owner approve whether content should be migrated, archived, or deleted. Investigate content that:

is duplicated, obsolete, or has no owner;
has not been used within the agreed review period;
cannot be opened or is password protected;
depends on mapped drives, fixed paths, shortcuts, macros, or applications;
has names, types, sizes, or paths reported as migration issues;
has permissions that cannot be mapped to active Microsoft 365 identities.

Do not use last modified date as the only deletion rule. Some records are rarely opened but must still be retained. Conversely, a recently modified duplicate is not necessarily valuable.

After remediation, scan again against the approved destination. Renaming or moving a folder changes the target paths of its contents and can affect dependencies. Keep the updated findings with the migration wave's decisions. Resolve blockers or approve a different destination before scheduling the copy.

7. Prepare Users And Practice The New Working Pattern

Prepare people before each migration wave. Explain why the work is changing, where documents will belong, which old habits must change, and what users can expect during the transition. Use the agreed structure and access rules in the training. Show where the team's existing documents belong in the new structure.

Name an adoption lead who coordinates training, instructions, and feedback with the migration lead. Reserve preparation, practice, and support time for local Key Users or champions. Ask managers to make that time available and explain the agreed working pattern to their teams. Microsoft's champion resources can help organize this local support.

Set learning goals for each audience:

Audience	What to practice
End users	Find and save documents in the right place, edit together, share a link, check who has access, and restore an earlier version. Recognize when synchronization is approved and how to request help
Key Users and workspace owners	Coach colleagues, maintain useful metadata and views, handle membership within their authority, and escalate access or content decisions
IT and service desk	Diagnose missing access and sync problems, use recovery procedures, and route application or security incidents to the right owner

Before cut-over, let representative users practice their real tasks in the configured destination with their normal permissions. Use representative content with approved access. Make the exercises follow the document collaboration working pattern. Record where users get stuck and change the instructions or design before repeating the test.

At cut-over, provide short task instructions, the new locations, and a named support route. During aftercare, offer drop-in sessions, repeat exercises where needed, and collect questions through one agreed channel. The adoption lead should review these with Key Users and IT so recurring problems lead to a correction in training, configuration, or the working pattern.

Check readiness through tasks users can complete independently. Attendance alone does not show that a team can work in the new location. Resolve learning or usability problems that prevent essential work before cut-over. Give other problems an owner, an agreed solution, and a follow-up date.

8. Pilot With A Representative Group

Choose a pilot that contains realistic complexity: folders, Office files, special permissions, links, larger files, and users with different working patterns. A technically easy folder proves very little.

Validate these four areas:

Content And Migration Results

Compare the inventory, approved exclusions, expected content, migrated content, and failures. Record the reasons for differences and obtain the business owner's approval.
Confirm that the tool meets the agreed scan, mapping, restructuring, incremental-copy, retry, and reporting requirements.
Test names, paths, and representative documents in the intended browser, Teams, or synchronization workflow.

Access And Protection

Verify the expected access for owners, members, visitors, and approved exceptions.
Run the required negative access tests for former members, role changers, expired guests, obsolete direct permissions, and old sharing links.
Test source Deny exclusions and unintended Everyone except external users access with the affected accounts.
Test managed- and unmanaged-device behavior and applicable Purview protection with representative sensitive files.

Applications And Processes

Users And Support

Test search, metadata, views, navigation, sharing, and approval processes.
Have representative users complete their key tasks independently. Assign owners and solutions for remaining non-blocking learning or usability problems.
Make task instructions available and confirm that users know where to request help.
Confirm who provides support at cut-over and how they handle access, synchronization, and application problems.
Agree on rollback criteria, the decision maker, and the recovery procedure.
Record the business owner's and IT owner's pilot acceptance.

Do not cut over with unintended access, failed critical processes, users unable to complete essential tasks, or missing support and rollback arrangements. Resolve these blockers first. Only accept other issues with named owners and agreed end dates.

Microsoft's file share migration guidance recommends an incremental pilot followed by a cut-over. Use the pilot findings to update the destination design, remediation rules, communications, and wave plan before scaling up.

9. Migrate In Waves And Cut Over

Migrate by work area so that each wave has an accountable owner and a known audience. Plan three decisions for each wave: accept the cut-over, complete aftercare, and retire the source.

The owner approves the content list, destination, and access model.
IT resolves scan findings, rescans, and prepares the destination.
The migration team performs an initial or incremental copy.
Users practice and validate the destination before the agreed deadline.
The source becomes read-only and the team migrates the final changes.
The team compares the inventory with the results and validates permissions, critical files, and business processes. The owner approves documented differences.
The business owner and IT accept the cut-over against the criteria below. Users switch to Microsoft 365 and aftercare starts.

Publish the cut-over time, write-freeze rules, new locations, support route, and rollback criteria in advance. Resolve blockers before switching users. Avoid leaving both locations writable; duplicate working copies make it unclear which version is authoritative.

Name the aftercare lead, service desk contact, local Key Users, and escalation owners before cut-over. Prepare short support instructions for missing access and sync problems, including checks before retrying and when to escalate. Schedule a review of recurring questions, unresolved defects, and training needs.

Agree on a read-only period for the old share, its access rules, and a retirement decision date. Base the period on validation, operational, and retention needs. Keep the source read-only through aftercare and until retirement is approved. A read-only source does not replace backup or the recovery plan.

Definition Of Done

Record each of the following decisions separately. Unintended access or a failed critical process blocks acceptance. Other issues need an owner, an agreed solution, and an end date.

Accept The Cut-Over

The business owner has approved the content, structure, and destination. The migration results match the inventory and approved exclusions, or the owner has approved documented differences.
Access tests pass. The membership source, sharing model, workspace owners, access-review owner, exception route, and review dates are recorded.
Critical links, applications, and complete business tasks pass their tests or have been replaced by tested alternatives.
Representative users complete essential tasks independently. Training and task instructions are available for the affected users.
IT has confirmed retention, recovery, device protection, and rollback arrangements.
The service desk and aftercare team are available with support instructions, escalation owners, and a scheduled review.
The source is read-only and Microsoft 365 is the agreed working location.

Complete Aftercare

The scheduled review has taken place. The team has addressed recurring support problems and provided further training where needed.
Operational owners have accepted the remaining non-blocking issues, with named owners, solutions, and end dates.
The aftercare lead and service owner have approved the handover to regular support, including instructions, recovery procedures, responsibilities, and review dates.

Retire The Source

Aftercare is complete. The business owner and IT have confirmed that required records, legal holds, and recovery needs are covered before retiring the source.
The retirement decision, executor, and date are recorded. Critical links and processes no longer depend on the old share.
The old location has been retired according to the approved plan.

Measure success by findability, correct access, owner acceptance, process continuity, and reduced use of the file server. Copied item counts are only part of the evidence.

Common Migration Mistakes

Copying everything one-to-one.
Creating a site for every top-level folder.
Reviewing permissions only after migration.
Assuming that SharePoint keeps access centrally managed without configuring ownership, membership, and sharing.
Leaving old and new storage writable for too long.
Missing Excel links, macros, shortcuts, and application dependencies.
Treating adoption as an afterthought, so users lack a clear new working pattern and fall back to the file server or local copies.
Making only the technical migration partner accountable.
Treating copied item count as the definition of success.

Recommended Approach​

Migration Flow​

Reserve Time And Capacity​

1. Define Scope And Decision Rights​

2. Inventory And Assess The Source​

Check The Intended Target​

Set Migration Tool Acceptance Criteria​

Distinguish User Data From Application Data​

Example: Power Query Reads A Local File​

Distinguish Power Query From Workbook Links​

Check How The Application Signs In​

Map Work Process Dependencies​

3. Choose The Destination​

4. Design The New Structure And Access​

Govern Membership And Access​

Review Broad Access Before Copilot​

5. Control Synchronization And Local Data Risk​

Understand Shared-Library Conflicts​

Example: A Connection Drops During Editing​

Example: A Folder Moves While A File Is Open​

More Situations To Include In The Pilot​

Protect Local Data And Plan Recovery​

6. Clean Up And Remediate​

7. Prepare Users And Practice The New Working Pattern​

8. Pilot With A Representative Group​

9. Migrate In Waves And Cut Over​

Definition Of Done​

Accept The Cut-Over​

Complete Aftercare​

Retire The Source​

Official Microsoft Documentation​

Related Guides​