Acronis Cyber Files Alternative for MSPs

Assess RushFiles as an Acronis Cyber Files alternative, including customer management, deployment, user migration, data transfer and areas to validate.

Acronis Cyber Files Alternative: Is RushFiles the Right Fit for MSPs?

Acronis Cyber Files, previously called Acronis Files Advanced, and Acronis Files Connect reached end of life on 31 December 2025, with extended support available until 31 December 2026, as set out in Acronis' official end-of-life notice. The lifecycle dates and the first planning steps are covered in the Acronis Cyber Files and Files Connect end-of-life guide.

RushFiles can be evaluated as an alternative for MSPs using Acronis Cyber Files for managed file sharing, but suitability depends on the customer's existing configuration, workflows and deployment requirements. This article deals with fit rather than timing: where the alignment is strong, how requirements map across, and what has to be checked for each customer.

When RushFiles may be a suitable fit

The alignment is closest where an MSP wants to keep delivering file sharing as a managed service under its own commercial model. Specifically, where the provider needs to:

  • Manage separate customer environments from one reseller platform
  • Retain control of service packaging, pricing, billing and the customer relationship
  • Offer SaaS or On-Premise deployment, depending on the customer
  • Provide file access through Windows, Mac, web and mobile applications
  • Support both internal and external file collaboration
  • Prepare users and data for migration in bulk

Where an Acronis environment exists mainly to support protocol-level or client-specific file access, the fit is less direct and needs separate assessment.

How Acronis Cyber Files requirements map to RushFiles

The table below shows how the requirements that usually drive an Acronis file sync and share replacement map to the RushFiles model, and what the MSP still needs to confirm in each case.

How Acronis Cyber Files requirements map to RushFiles

How Acronis Cyber Files requirements map to RushFiles

Requirement to assess RushFiles approach What the MSP should validate
Customer environments Separate customer organisations managed from one reseller platform. Customer ownership, administrative boundaries and required separation.
Users and roles Bulk CSV import with Admin, Internal and External roles. How existing Acronis users and roles map to the RushFiles model.
Shares Folders can be matched to existing shares, and missing shares can be created during bulk upload. The target share structure for each customer.
Folder structure The folder structure can be kept intact during bulk upload. Saved paths, shortcuts, scripts and other dependencies.
Permissions Access can be configured within each customer environment. How source permissions map to the agreed target model.
Deployment Available as SaaS and On-Premise. Hosting, infrastructure and data-location requirements.
External collaboration Internal and external users can access and share files. Existing customer, contractor and supplier workflows.

Treat the table as a discovery framework rather than a statement of feature parity. The right-hand column highlights the questions that need to be resolved before confirming the migration approach for each customer.

What still requires customer-specific discovery

Some requirements cannot be judged from the product in use. For each customer, establish:

  • The permission model in place, including exceptions granted outside the standard structure
  • Authentication and identity requirements
  • How external sharing currently works for clients, contractors and suppliers
  • Integrations, scripts, mapped paths and saved shortcuts that reference the file structure
  • Hosting and data-location requirements
  • Any protocol-specific or client-specific functionality in use
  • How the customer uses Acronis Files Connect, if it is also installed

RushFiles should not be presented as a universal replacement for every Acronis Files Connect use case. Files Connect may be used for specific Mac and Windows file-access functions, so those requirements need to be assessed separately.

How RushFiles supports migration preparation

Two RushFiles tools help reduce repetitive setup work when preparing users and data for migration.

User migration through CSV import supports:

  • Importing users in bulk
  • Creating users with Admin, Internal or External roles
  • Defining whether users can create shares
  • Creating private shares during import
  • Importing users into a specific company

The bulk upload tool supports:

  • A share-based folder structure
  • Matching folders to shares
  • Creating shares when they do not exist
  • Keeping the folder structure intact
  • Controlling overwrite behaviour for remote, local or newer files

Together these reduce the account-by-account and folder-by-folder work involved in standing up a new environment, which matters when several customers are being prepared in sequence. Users, roles, shares, permissions and sharing workflows still need to be mapped and validated against the agreed target environment before and after each import.

Confirm the fit with one customer environment
The practical way to decide is to run one representative but manageable customer environment on the platform. Choose one with a real permission structure and some external collaboration, rather than the largest account in the portfolio.

That evaluation should confirm user and role mapping, the share and folder structure, permission configuration, external collaboration, access from desktop, web and mobile, the administrative effort required from your own team, and whether the chosen deployment model suits the customer.

Assess your first Acronis environment

The Acronis Replacement Planning Workbook gives you a structure for documenting one customer environment and identifying what needs to be mapped or validated before a decision.

Download the Workbook to assess your first environment, or book a migration-planning call to review a specific customer with us.