Acronis Cyber Files Cloud Migration Guide

Acronis Cyber Files Cloud File Sync & Share support is ending. Learn what to move, what to recreate and how to test a replacement with one customer.


Acronis Cyber Files Cloud File Sync & Share: What Service Providers Need to Replace

Acronis lists 31 December 2026 as the end of extended support for standard File Sync & Share in Acronis Cyber Files Cloud. Extended support for the advanced notarization and eSignature functionality ended on 1 June 2026, according to the same Acronis lifecycle notice.

If you deliver file sharing to multiple customers, start by checking which customer environments use the service and what each needs to keep. One customer may only need its shared folders and user access restored. Another may have external links in active use, a branded portal, or signed documents and verification records to preserve. That difference determines what you need from a replacement and what you should test before switching.

What is ending in Acronis Cyber Files Cloud?

Acronis’s notice covers two functions within Cyber Files Cloud:

Acronis Cyber Files Cloud support dates

Acronis Cyber Files Cloud support dates

Functionality End of life and mainstream support End of extended support
Standard Files Sync and Share 31 December 2025 31 December 2026
Advanced Files Sync and Share: Notarization and eSignature 31 December 2025 1 June 2026

‍

These dates describe the support lifecycle of the listed functions. Ask Acronis or your distributor to confirm how long each affected customer can access and export data. The notice does not set a universal date for account access or data deletion.

If your customers use the on-premises products, see the separate Acronis Cyber Files and Files Connect end-of-life guide. Keep any Acronis backup or security services the customer still uses out of this file-sharing migration plan.

What do you need to move or recreate for each customer?

Create one inventory per customer tenant. Start with the services in use and who administers them, then work through what users and external recipients need to do after the move.

Acronis Cyber Files Cloud migration checklist

Acronis Cyber Files Cloud migration checklist

Area What to record What to verify before switching
Customer environments Active tenants, storage volumes, customer administrators and hosting requirements Each customer has a separate environment with the right administrators, storage and data location.
Users and access Internal users, external collaborators, sign-in methods, folder owners and permission exceptions Each role has the right access. Test both a person who should see a restricted folder and one who should be denied.
Files and folders Active folders, required versions and any files that must be kept separately A sample export includes the files and versions you expect. Check how folders and ownership are set up in the new service.
Shared links Links customers still use, their owners, and any expiry or access restrictions Identify which links need replacing. Test a new link as the recipient and agree who will send it or update it where it is published.
Branding and daily access Portal address, branded invitations, and web, desktop or mobile workflows Users can find the new portal, recognise invitations and complete a routine task on the devices they use.

‍

Before choosing a replacement, mark each item as transfer, recreate or keep separately. For example, you might transfer a project folder, recreate its external link and keep an older version in an archive. Assign an owner to each item that needs manual work.

What if customers use notarization or eSignature?

Preserve existing records. List the completed signed documents, notarized file revisions and supporting records the customer needs to keep. Acronis explains that downloading a notarized file does not also download its certificate. Save the certificate separately with the matching revision and test how the customer will verify it later.

Plan for pending and future requests. Identify any signing requests that are still open and agree with the customer which can be completed before the move and which may need to be reissued. If signing continues after the migration, test the proposed workflow separately: send an invitation, have an external recipient sign, and check that the completed document and required records can be retrieved. Include any identity checks the customer relies on.

How do you test a replacement with one customer?

Choose a customer that reflects the work you need to repeat across your customer base. A useful pilot includes a restricted folder, a real external sharing workflow and the devices users depend on. If only some customers use signing, include a separate signing test for one of those customers.

  1. Export a sample and compare it with the source. Include a shared folder and any older file versions the customer needs. Record what the export contains and what needs separate handling.
  2. Set up the target environment and test access. Sign in as an administrator, an internal user and an external collaborator. Check that each can see and do only what you intended.
  3. Run a real task from start to finish. Ask a user to open and update a file from their usual device. Have an external recipient open a replacement link. If branding is part of the service, check the portal and invitation they actually see.
  4. Agree what has to pass before the switch. Record what worked, what still needs to be recreated, who will notify users, and who signs off. Agree when to postpone the switch if a required workflow fails.

Plan your first Acronis Cloud migration

If you’re evaluating RushFiles for the file-sharing part of the move, the Acronis replacement page explains how to set up separate customer environments and what to scope before running a pilot.

Download the Acronis Replacement Planning Workbook to record which customers are affected, what users need to keep and what you want to test first.

Already have a customer in mind? Discuss your migration to review the environment and scope a pilot.