Telecom File-Sharing Platform Migration Guide

Replacing the platform behind your telecom file-sharing service? Plan accounts, data transfer, customer access, applications, testing and cutover.

Replacing a Telecom File-Sharing Platform: Accounts, Data and Customer Access

Replacing the platform behind a customer-facing storage or file-sharing service involves moving or recreating customer accounts, transferring data, mapping access, adapting integrations and managing the change in customer experience. Copying files is one part of that work.

Telecom operators, ISPs and broadband providers may reach this point because of supplier retirement, a contract review or requirements the current platform no longer meets. The reasons providers review their file-sharing platform are covered separately.

Whatever the trigger, establish which logins, sharing links, applications and workflows can continue, and which will change. The plan should reflect the service customers use today, whether that is individual subscriber storage, business file sharing or both.

Start with the service your customers use today

Document the live service before choosing a migration method. The method depends on what customers actually use, including configurations and workflows that may have changed since the service was launched.

Record the following:

  • Account structure. Subscriber storage accounts, business customer environments with multiple users, or both. The two differ in permissions and migration sequencing.
  • Account status. Active and inactive accounts, including which inactive accounts still hold data.
  • Data in use. Stored volume, file count and recent activity, measured rather than estimated from allowances.
  • Sharing. Shared folders, permission levels, external users who are not your customers, and public links in circulation.
  • Applications. Which web, desktop and mobile clients customers use, and which versions are in use.
  • Connections. Identity, provisioning, usage reporting and billing connections to your own systems.
  • Supplier constraints. Export methods, any rate or volume limits on export, and contractual deadlines for access and deletion.

Account count, stored data, file count and activity all affect migration planning. Accounts determine provisioning and rollout work, while data volume, file count and ongoing changes affect the transfer.

Several teams hold parts of this picture. Product knows the packages sold, operations and support know the exceptions, and technical teams hold the integration detail. The outgoing supplier confirms export methods and limits, while the incoming supplier confirms what its import process accepts.

Establish what can move and what must be recreated

Work through the service element by element and decide, with both suppliers, what transfers and what must be created on the destination.

Service element What to confirm What the migration plan must specify
Customer accounts and identifiers Which account attributes can be exported, and whether identifiers from your systems can be carried across How accounts are created on the destination, how they are matched to your customer records, and how customers first authenticate
Files and folder structure Export and import formats, folder depth, path length and character limits, and any file-size ceiling Which structure is reproduced as-is, what is reorganised, and who approves the target structure
Permissions and shared access How each permission level on the source corresponds to a level on the destination, including external participants An explicit mapping table, the treatment of unmapped cases, and who signs it off
Public sharing links Whether links depend on supplier-specific identifiers, domains or access tokens, and what the destination can issue Whether links are recreated, redirected or allowed to expire, and how affected customers are told
File versions, metadata and activity history Which versions, timestamps, ownership records and audit entries the source can export and the destination can accept What is migrated, what is retained separately, and which omissions are explicitly approved against service, contractual and retention requirements
Storage allowances and account status How allowances, suspensions and closures are represented on each platform How each status is applied on the destination and kept in step with billing

Creating accounts is different from migrating credentials. Confirm whether a supported credential-migration method exists. Where credentials cannot transfer, plan for authentication through an identity system you control or a password-setting and account-activation process.

Transferring current files does not establish that version history or activity logs can move with them. Those records may require separate exports and imports that either platform may not support.

Permissions need an explicit mapping between the source and destination models, including a decision on any permission with no equivalent.

Public links may depend on identifiers, URLs or access tokens issued by the outgoing platform. Preservation, redirection and recreation are options to assess, with feasibility verified on both sides. Do not assume a link survives because the domain stays the same, or that every link must break.

Plan customer login and application changes

Decide early what customers will have to do. That determines the instructions they need and the support your team should prepare.

Start with authentication. If customers sign in with their telecom identity through your own identity system, that may continue, subject to the destination supporting the required method.

If credentials are held by the outgoing platform, confirm whether a supported migration method exists. Where credentials cannot transfer, plan a password-setting or account-activation step.

Then review the client applications. Confirm whether customers must install a different desktop or mobile application, or whether an existing one can be reconfigured. Where a desktop client synchronises files locally, establish what happens to the local copy and to edits not yet uploaded.

Depending on client behaviour, connecting a new application to an existing synchronised folder can produce duplicate folders, conflicting edits or unnecessary reuploads. Test the proposed process and provide instructions based on the result.
Service name, domain and branding changes belong in the same plan. A familiar name and appearance help customers recognise the service, but sessions, links and stored credentials may still change.

Distinguish standard client applications from branded ones, since branding scope varies by platform and deployment. With RushFiles, SaaS supports branding for the web portal, domain and system emails, while full desktop and mobile application branding requires On-Premise. The scope of branding across the web portal and applications is documented separately.

Any replacement or reconfiguration of customer applications needs to be included in the rollout plan.

Reconnect provisioning, reporting and billing

The replacement platform must support the account lifecycle behind your customer service.
Work through each event your systems trigger: creating an account on activation, changing a storage allowance, suspending for non-payment, and cancelling with the agreed treatment of stored data.

For each event, confirm whether the destination supports the action, how it is invoked and what confirmation your systems receive. Usage reporting needs the same assessment: what is measured, at what granularity and how often, and whether that matches what billing expects.
Decide which identifier links a customer in your systems to an account on the destination. Record the mapping during migration so operations and support can trace each account afterwards.

While both platforms are live, define which system controls provisioning and which usage records feed billing for each migration group. This helps prevent duplicate accounts, missed changes and duplicate charges.

The existence of an API does not establish that the functions you need are supported or already integrated. Some workflows may use existing configuration or a manual process during a short transition. Others require integration work. The scope depends on the source platform, the destination platform and your own systems.

Transfer the data and verify the result

Confirm the supported transfer methods before estimating the work.
Establish which export methods the source supports and which import methods the destination accepts. Then assess data volume, file count, throughput and any export rate limits.

Where the destination runs on infrastructure you operate, as with a deployment on your own infrastructure, your team also needs to prepare the destination capacity and network access required for the import.

Decide whether an initial transfer can run while the existing service remains available. If it can, establish how later changes will be captured.

A delta transfer moves changes made since the initial copy. Do not assume either platform supports it. If incremental transfer is unavailable, agree how changes made during the move will be reconciled. Depending on the migration method, this may require a period when uploads and edits pause.

Define how failed transfers are detected, retried and escalated, and who reviews exceptions before customer access changes.

Validation should cover file contents and access outcomes. File counts and total bytes are useful starting checks, but do not establish that the migration is complete or correct. Use integrity checks where supported, test permissions against the agreed mapping and run representative workflows: open a file, share one internally, share one externally, and confirm that an administrator has the intended access.

Be explicit about what does not carry over. Moving files does not automatically bring versions, timestamps, sharing links, audit records or every piece of source metadata.

Use a pilot to decide the cutover and rollback approach

Cutover is the point at which customers begin using the replacement platform. Use a pilot to test the transfer and access changes before setting the wider rollout.
Choose a pilot that reflects the service. For subscriber storage, test activation, login, storage allowance changes and personal file access on the devices customers use. For business customers, include shared folders, permission levels, external participants and administrative tasks.

Include known exceptions, such as unusually large accounts or non-standard configurations, so the pilot tests more than the simplest migration path.

Agree:

  • Written acceptance criteria, defined before the transfer starts.
  • A rehearsal of the data transfer and the customer access change.
  • Migration in account groups or complete business customer environments, so related users move together.
  • A final synchronisation or agreed write pause, where the transfer method requires it.
  • A go or no-go decision with named owners and an agreed decision time.
  • A rollback decision point.

Rollback becomes harder once customers have created or changed data on the destination.

Returning them to the old platform requires a decision about how those new files and changes will be captured and reconciled. Keeping the old system available is not, by itself, a complete rollback plan.

A functional pilot tests whether workflows behave correctly. It does not establish throughput or capacity for the full customer base. Agree separately how production-scale performance will be validated, using representative load testing, a phased rollout or another suitable method.

Communicate the change and retire the old platform

Keep customer communication proportionate to what customers need to do. A change requiring no action may need only a short notice. One requiring a different application needs clear installation and sign-in instructions.

Tell customers why they are receiving the message, what is changing and what remains available, whether action is required, any planned interruption or restriction, and where to find instructions and support.

A hypothetical example for customers who must install a replacement application:
We are updating the platform behind your storage service. You will need to install a replacement app and sign in using the instructions we provide. Before making changes to the existing app or its folders, follow our migration guide so any pending uploads and local files are handled correctly. We will confirm the changeover date, any access restrictions and where to get support before the move.

After cutover, monitor login and file-access problems, provisioning and billing exceptions, support-ticket patterns, reports of missing or inaccessible files, and failed migration jobs. Give that monitoring a defined period and a named owner.
Retire the outgoing service only once validation is complete and the agreed retention and contractual requirements are met. Confirm any required final export, agree how deletion will be documented, and establish who holds retained copies and for how long.

Assessing RushFiles as the replacement platform

RushFiles is a partner-only file-sharing and storage platform. Operators manage their own customer offer, pricing, billing and first-line support. Business customers can be administered as separate environments through a reseller panel.

SaaS and On-Premise deployments are available, affecting who operates the infrastructure during and after migration.

RushFiles documents bulk user import and bulk data upload tools for creating users with defined roles and uploading data into a share-based folder structure. These tools support specific import operations. Their availability does not establish that passwords, source permissions, public links, file versions or application settings will transfer. Confirm each against the source platform and proposed migration method.

Tooling described for business customer environments also needs assessment against a subscriber account structure. The starting points are on the file-sharing services for telecom providers page.

Discuss your existing service and migration requirements

Frequently asked questions

Can customers keep their existing login after a platform migration?

Sometimes. If customers authenticate through an identity system you control and the destination supports the required method, the login may remain familiar. Where credentials are held by the outgoing supplier, confirm whether they can migrate. If they cannot, plan a password-setting or account-activation step.

Will existing file-sharing links continue to work?

That depends on how links are constructed and handled by both platforms. Supplier-specific identifiers, domains or access tokens may prevent direct transfer. Assess preservation, redirection and recreation with both suppliers, then test the agreed approach before telling customers which links will continue to work.

Can file versions and permissions move with the files?

Treat them separately from the current files. Versions can transfer only where the source can export them and the destination can import them through a supported process. Permissions need an explicit mapping between the two models, including decisions for any access level without an equivalent.

Can the service remain available during migration?

That depends on how the transfer handles files that change during the move. An initial copy may run while the source remains available, with later changes reconciled before cutover. Some methods require a write pause or access restriction. Agree and test the approach before promising continuous availability.

What determines how long the migration takes?

Account count, data volume, file count, export and import restrictions, ongoing changes, integration work, validation and the pace of customer rollout all affect timing. The estimate should include account preparation, data transfer, testing, customer access changes and post-cutover checks. User numbers alone are insufficient.