Retiring the File Server: Migrating to SharePoint and OneDrive Without the Chaos

For many businesses, the file server has been part of the IT environment for years. It holds everything from client documents and financial records to project files and internal procedures. People know where to find things, and for the most part, it does the job.

But older file servers can also bring challenges. Hardware needs replacing, operating systems reach end of support, remote access can be cumbersome, and permissions often become difficult to manage as teams and business requirements change.

Moving files to Microsoft SharePoint and OneDrive can provide a more flexible way to store, access and collaborate on business information. It can also reduce reliance on on-premises infrastructure and create a stronger foundation for Microsoft 365 tools.

However, a successful migration involves more than copying files from one location to another. The way information is organised, who can access it and how staff work with it all need to be considered.

Here’s what businesses should think about before making the move.

Why Planning Matters Before You Migrate

One of the biggest mistakes businesses can make is treating a file server migration as a simple data transfer.

The quickest approach is to copy the existing folder structure into SharePoint, carry across the current permissions and give staff access to the new location. While migration tools can make this relatively straightforward, it doesn’t necessarily mean the result will be well organised or secure.

Consider what’s likely to have accumulated on an older file server over the years:

• Access groups created for projects that finished long ago

• Individual users given direct access to folders

• Permissions inherited from parent folders that no longer make sense

• Shared folders opened to everyone for convenience

• Old documents and duplicate files that are no longer needed

Simply copying everything across can carry these issues into the new environment.

This is particularly important when you consider how easily information can be searched and accessed across Microsoft 365. If your business plans to introduce Microsoft Copilot, reviewing access permissions becomes even more important. Copilot works within the permissions a user already has, so poorly managed access can mean people are able to discover information they shouldn’t be seeing.

We cover this in more detail in our guide to Microsoft Copilot readiness.

A migration is a good opportunity to review what information you hold, who needs access to it and how it should be organised. Getting these decisions right at the beginning can save considerable time and rework later.

Technical Considerations Before You Migrate

There are several Microsoft 365 and Windows limitations worth understanding before moving large volumes of data. Identifying these early helps avoid migration delays and problems for staff once the new environment is in use.

SharePoint file path limits

SharePoint has a maximum decoded file path length of 400 characters. This includes the site, document library, folders and file name.

Older file servers often contain deeply nested folders with long names, which can quickly exceed this limit. For example, a document stored several folders deep under a project, client and approval structure may have a much longer path than expected.

These files may need to be renamed or reorganised before migration.

Windows file path considerations

If staff synchronise SharePoint libraries to their computers using OneDrive, Windows file path limitations also need to be considered.

A file may successfully migrate to SharePoint but still cause issues when someone tries to access it through a synchronised folder on their computer. Keeping folder structures and file names manageable helps avoid this.

File sizes and storage

SharePoint supports individual files up to 250 GB and individual sites up to 25 TB. Microsoft 365 tenant storage is generally allocated as 1 TB plus 10 GB per licensed user, with additional storage available for purchase.

Storage requirements should be calculated before migration, particularly for businesses with large document libraries or years of accumulated data.

OneDrive synchronisation limits

Microsoft recommends keeping the total number of items synchronised across all SharePoint libraries and OneDrive locations to 300,000 per user.

This is a performance recommendation rather than a hard limit, but exceeding it can lead to slow synchronisation, delays and a poor user experience.

For businesses with large file servers, this needs to be considered when deciding which libraries staff should synchronise to their devices.

Library views and permissions

SharePoint also has thresholds that influence how document libraries should be designed. For example, the 5,000-item list view threshold can affect how large libraries are displayed and queried.

Large numbers of unique permissions can also make an environment more difficult to manage.

These considerations generally favour a well-planned structure with sensible libraries, clear permissions and appropriate use of metadata, rather than simply recreating a large, deeply nested file server.

What Shouldn’t Move to SharePoint?

SharePoint is well suited to business documents and collaboration, but it isn’t the right home for every type of file.

Some information and applications need to remain on a server or use a different storage solution.

Databases and business application data

Some business applications rely on files stored directly on a network share. These may include databases or application data that needs to be accessed in a particular way.

SharePoint isn’t designed to operate as a traditional file system for these applications. Moving this information without understanding how the application works can cause performance or compatibility issues.

Applications and processes that rely on file paths

Older applications, scripts, scanners, integrations and label printers may reference a specific network location, such as an S: drive or a UNC path.

Moving the files doesn’t automatically update those references. These dependencies need to be identified and addressed before the old server is switched off.

Large active design and media files

Some large files, particularly CAD assemblies, BIM models and video production files, may not be suited to a typical SharePoint and OneDrive working arrangement.

While these files can sometimes be stored in SharePoint, the experience may not be ideal when applications need to open and save large files repeatedly, particularly over slower internet connections.

For construction, engineering and design businesses, it’s important to assess these requirements individually. SharePoint may be suitable for project documentation and supporting information, while active design files may need a different solution.

Old archives and information no longer required

A migration is also a good opportunity to review old information.

There may be years of archived documents, duplicate files and records that are no longer needed. Moving everything simply because it exists can add unnecessary storage costs and make information harder to manage.

Consider what needs to be retained, what should be archived and what can be securely disposed of in line with your business and record-keeping obligations.

How Should Your Files Be Organised?

Once you’ve established what needs to move, the next decision is how information should be structured in Microsoft 365.

Two important considerations are how SharePoint and Teams will work together, and whether to use folders, metadata or a combination of both.

SharePoint or Microsoft Teams?

Microsoft Teams and SharePoint are closely connected. When you create a Team, a corresponding SharePoint site is created to store the files shared within that Team.

This works well for departments and groups that regularly collaborate. However, creating a Team for every type of information can quickly lead to unnecessary sites and confusion.

Some content, such as company policies, reference documents and published procedures, may be better suited to a dedicated SharePoint site rather than being stored within a Team that staff rarely use.

The structure should reflect how people work and how information needs to be accessed.

Folders or metadata?

Most staff are familiar with traditional folder structures. They know where to save a document and how to navigate through folders to find what they need.

SharePoint also supports metadata, which allows documents to be categorised by information such as client, year, document type or status. This makes it easier to filter, search and organise information without relying on multiple layers of folders.

A fully metadata-driven structure can work well in some environments, but it may be a significant change for staff who have used traditional folders for years.

For many businesses, a practical approach is to use a simpler folder structure supported by metadata where it adds value.

The goal isn’t to make the structure as sophisticated as possible. It’s to make information easy to find, easy to manage and appropriately secured.

Making the Transition Easier for Your Team

The technology is only one part of a successful migration. Staff also need to understand what’s changing and how to work in the new environment.

People become familiar with the way their existing file server works. They know which drive to open, where their department’s documents are stored and where to save completed work.

When that changes, even a well-designed SharePoint environment can initially feel unfamiliar.

Common questions include:

• Where has everything gone? Staff need to understand the new structure and where their familiar documents are located.

• Why does it work differently? SharePoint and OneDrive have different ways of accessing, opening and synchronising files.

• Can I still access files offline? This needs to be configured appropriately, particularly for staff who work away from the office.

• Where should I save new documents? Clear guidance helps prevent staff reverting to desktop folders or creating their own storage locations.

A little preparation can make a significant difference.

Before the migration, explain what is changing and why. Give staff a short introduction to the new environment, show them where their commonly used files will be located and explain how to access and save documents.

It’s also worth having someone available to answer questions during the initial transition. A pilot with one department before rolling the change out across the business can help identify issues and improve the experience for everyone else.

Supporting Staff in the Field and on Site

For businesses in construction, engineering, field services and community care, access to information away from the office is an important consideration.

SharePoint provides cloud-based access to business documents, but staff may not always have a reliable internet connection when working on site or travelling.

The OneDrive synchronisation client allows selected files and folders to be made available offline, so staff can continue working when connectivity is limited. Changes can synchronise once a connection is available again.

However, this needs to be planned as part of the migration.

Consider:

• Which document libraries do field staff need access to?

• Should files be synchronised to devices for offline access?

• Do laptops and tablets have enough storage?

• How will staff manage documents when connectivity drops?

• How will multiple people work on the same documents?

Thinking through these requirements before the migration helps ensure the new environment supports the way your people actually work.

What Does a SharePoint Migration Involve?

A successful migration generally follows a number of stages. The exact approach will depend on the size and complexity of your existing file server, the volume of data and how your business operates.

Microsoft provides migration tools, including Migration Manager within the SharePoint admin centre, to help move files from network file shares and other supported platforms.

The technology helps with the transfer, but planning and preparation are what make the difference.

A typical migration involves the following steps.

1. Discover and assess

Start by understanding the existing environment.

This includes reviewing how much data is stored, how folders are structured, which files are actively used, where permissions have been applied and whether any applications rely on the existing network drives.

2. Design the new environment

Plan the SharePoint sites, document libraries, folder structures and metadata.

Most importantly, establish who should have access to each area of information and how those permissions will be managed.

3. Prepare and remediate

Before moving data, address issues identified during the assessment.

This may include shortening file paths, resolving permission issues, removing duplicate or unnecessary information and deciding what should be archived rather than migrated.

4. Run a pilot migration

Choose a department or group of users and move a portion of their data first.

This gives the team an opportunity to test the new environment, identify any problems and provide feedback before the wider migration begins.

5. Migrate in stages

For larger environments, data can be migrated in planned stages or department-by-department.

A preliminary transfer can take place while staff continue using the existing file server, followed by a final synchronisation before the business switches to the new location.

6. Transition and support staff

Once the migration is complete, staff need to know where to access their files and how to work in the new environment.

The old mapped drives should be removed or made unavailable for normal use once the transition is complete, helping avoid confusion about which location contains the current version of a document.

Support should also be available during the initial period to help resolve questions and any issues that arise.

7. Decommission the old file server

Once the new environment is operating as expected, the old server can be retained temporarily in a controlled, read-only state if required.

After the agreed transition period and any necessary checks, it can be decommissioned.

The time required will vary considerably. A relatively straightforward environment may take a few weeks, while a business with large volumes of data, complex permissions or application dependencies will need more planning and preparation.

This is why an assessment should come before a fixed migration quote.

More Than Just Replacing Your File Server

Moving to SharePoint and OneDrive can deliver benefits beyond retiring ageing hardware.

For many businesses, it creates an opportunity to improve how information is stored, accessed and managed across the organisation.

Benefits can include:

• Better access to information: Staff can access approved business documents from different locations and devices, without relying on a traditional office file server or VPN connection.

• Easier collaboration: Teams can work on shared documents, manage versions and collaborate without emailing multiple copies back and forth.

• Improved information management: A well-designed structure and appropriate permissions make it easier to manage business information.

• Greater flexibility: Staff can work across office, home and site locations, with access configured to suit their needs.

• A stronger foundation for AI: Well-organised information and appropriately managed permissions help prepare your Microsoft 365 environment for tools such as Microsoft Copilot.

It’s important to remember that moving to SharePoint doesn’t automatically make your information secure or replace the need for backup. Microsoft 365 security controls, appropriate access management and a suitable backup and recovery strategy remain important.

The real value comes from combining the right technology with a well-planned structure and ongoing management.

Frequently Asked Questions

Can SharePoint fully replace a file server?

For most business documents and collaboration needs, yes. However, databases, some business applications, files with hardcoded network paths and certain large design or media files may need a different solution. These should be assessed before migration.

What is the 400-character path limit in SharePoint?

The full file path, including the SharePoint site, document library, folders and file name, cannot exceed 400 characters. Older file servers often have deeply nested folder structures that need to be shortened or reorganised before migration. Windows path limitations should also be considered for users synchronising files to their devices.

How much storage does SharePoint provide?

The standard SharePoint tenant storage allocation is generally 1 TB plus 10 GB per licensed user, pooled across the organisation. Individual sites can support up to 25 TB, and individual files can be up to 250 GB. Additional storage can be purchased if required.

How many files can staff synchronise to their computers?

Microsoft recommends keeping the total number of items synchronised across all SharePoint libraries and OneDrive locations to 300,000 per user. This is a performance recommendation rather than a hard limit, but exceeding it can affect synchronisation performance.

Should we copy our existing folder structure into SharePoint?

Not without reviewing it first. Your existing structure may contain unnecessary folders, outdated permissions and information that no longer needs to be retained. A migration is a good opportunity to simplify the structure and make information easier to manage.

How long does a file server migration take?

It depends on the amount of data, the complexity of the existing environment and the number of applications or processes that rely on the file server. A straightforward migration may take a few weeks, while more complex environments can take considerably longer. An assessment will help establish a realistic timeframe.

Can staff access SharePoint files without an internet connection?

Yes. Using the OneDrive synchronisation client, selected files and folders can be made available offline. This needs to be configured appropriately, particularly for staff who regularly work on site or in areas with limited connectivity.

Ready to Move Beyond Your File Server?

Moving to SharePoint and OneDrive is about more than retiring old hardware. It’s an opportunity to improve how your team accesses, shares and manages business information.

With the right planning, your business can benefit from better collaboration, improved information management, greater flexibility and a stronger foundation for AI tools such as Microsoft Copilot.

At TechPath, we help businesses assess their existing IT environment, plan their Microsoft 365 architecture and manage the migration process. We also help establish the security controls and ongoing management needed to get the most out of your Microsoft 365 environment.

The first step is understanding what you have, what needs to change and how to make the transition as straightforward as possible for your team.

Thinking about retiring your file server? Contact our Brisbane team to discuss your Microsoft 365 migration.

Find out more about our Microsoft 365 services.