Replace suitable SMB file servers with a managed file-sharing platform that keeps everyday file access familiar and gives your team control over each customer environment.
RushFiles moves everyday shared-file access away from the customer's file server while keeping the user experience familiar.
What users keep
Work with assigned Shares through File Explorer on Windows or Finder on macOS.
Reach the same files through desktop, web and mobile applications without relying on a traditional file-server VPN for everyday access.
Work with company files and share with customers or partners through the same service.
What the MSP gains
Manage each customer through its own company environment with separate users, files, capacity and settings.
Configure users, groups, Shares, access, security and recovery from one platform.
Deliver file access through RushFiles SaaS or On-Premise instead of maintaining a separate file-sharing stack for every customer.
RushFiles is designed for shared-file workloads. Applications that require SMB or UNC paths, databases, server-side processing or specialised file behaviour should be identified and tested before migration.
RushFiles separates service-provider administration, customer configuration and end-user file access. Your team operates the service centrally while every customer receives its own environment.
Create a separate RushFiles company for each customer. Keep customer users, data, capacity and configuration separated while managing the service through the reseller administration.
Your team can use a consistent administration model across customers without forcing every customer into the same setup.
Within each company, configure the users, groups, Shares, access permissions and security settings required for that customer.
Connect Active Directory or Entra ID where appropriate, assign access through users and groups, and organise existing customer folders around the required Share structure.
Users access assigned Shares through File Explorer on Windows or Finder on macOS. The same files can also be reached through the RushFiles web application and iOS or Android apps.
Internal file access, external sharing and recovery are handled through the same service instead of separate tools for office, remote and customer-facing work.
Configure access, security, sharing, recovery and deployment around the requirements of each customer.
There is no single replacement for every file server. The right destination depends on how the files are used, which applications depend on them and how the MSP intends to operate the service.
| Option | Best suited for | User experience | Main MSP consideration |
|---|---|---|---|
| RushFiles | Managed shared files, familiar desktop access, remote work, external sharing and multi-customer service delivery | File Explorer on Windows, Finder on macOS, web and mobile | Application-dependent workloads and existing permissions must be assessed and mapped |
| SharePoint and OneDrive | Microsoft 365 collaboration, Teams, intranets and Office-centric document workflows | Web, Teams, Office applications and OneDrive sync | Existing folder structures and user workflows may require redesign |
| Azure Files | Cloud-hosted SMB shares and workloads that require SMB-based access | Traditional SMB file-share access | Connectivity, identity, Azure administration and consumption costs |
| New server or NAS | Workloads that must remain local or depend on traditional infrastructure | Traditional network shares | Hardware, backup, remote access, security and lifecycle responsibility remain |
RushFiles is strongest where the customer needs structured shared-file access, familiar desktop workflows, remote availability and external sharing—and the MSP wants to operate those capabilities as a repeatable managed service.
Replacing one server is a migration project. Using one platform across suitable customer environments creates an ongoing service.
Create a separate RushFiles environment for each customer while managing the service through one reseller administration.
Standardise how your team configures shared files, access, security and recovery without forcing every customer into the same setup.
Deliver the service under your own brand, choose the deployment model and define how it is packaged for customers.
The result is a file-sharing service your team can deploy and support across multiple customers without maintaining a separate platform for each one.
Use RushFiles as an EU-hosted service or deploy it within infrastructure you control.
Start offering file sharing without operating the platform infrastructure yourself.
Operate RushFiles on your own servers or private cloud when you need greater control over infrastructure, storage, data location, and branding.
Copying files is rarely the difficult part. Permissions, connected applications and user workflows determine whether the migration will work.
Review the data, users, permissions and applications connected to the existing server. Separate shared-file workloads from anything that still requires SMB paths, server-side processing or specialist behaviour.
Create the customer environment and Share structure, configure access, and use RushFiles bulk tools to import users and upload data.
Test permissions, representative files, Windows and macOS access, external sharing and recovery with real users before completing the migration.
The File Server Exit Plan 2027 Workbook helps you turn an ageing file server into a documented replacement project.
Use it to:
Bring us the current environment, user requirements and known dependencies. We will help you determine where RushFiles fits and what should be validated before migration.
The completed environment-inventory section of the Workbook is enough to start.