Sync Motion Logo

FTP modernisation without a big-bang cutover

Move on from your legacy system and modernise file transfers securely.

Exploded technical view of a legacy FTP server being modernised through transparent security layers into managed SFTP storage.

Sync Bridge for legacy systems · Keep existing workflows · Old and new run in parallel

Move from FTP to SFTP without rebuilding your workflows.

Modern clients move directly to SFTP. Legacy systems are modernised or go securely through the Sync FTP/FTPS to SFTP Bridge on the local network.

Move from FTP to SFTP without rebuilding your workflows.

Current environment

  • ERP & EDI
  • Machines
  • Backup jobs
  • Legacy software
SFTP capable

Direct SFTP connection

Local FTP/FTPS through Sync Bridge

FTP / FTPS only

SFTP · 22

Managed SFTP

Sync Motion SFTP

SFTP over SSH · port 22

On-premises modernisation

Your file server needs to stay in-house? We modernise it.

If data must not leave your site, we modernise your existing FTP server on premises. The insecure FTP service is replaced with a secured SFTP server on your own infrastructure.

With the enterprise package we handle planning, setup, and operations. Users, permissions, and directory structures stay in place, while updates and monitoring continue as a managed service.

Your path from an FTP server to SFTP.

The cutover is planned per connection, without changing every source system at once.

  1. 01

    Inventory
    the environment

    FTP servers, users, directories, data flows, schedules, and connected systems are documented.

  2. 02

    Classify
    each system

    For each client it is determined whether SFTP works directly or a local FTP/FTPS Bridge is needed.

  3. 03

    Prepare
    the target

    SFTP access, directories, and permissions are prepared; where required, Sync Bridge is installed locally.

  4. 04

    Pilot
    and verify

    A representative data flow is moved; transfer, file processing, and failure cases are checked.

  5. 05

    Cut
    over in stages

    Connections are migrated one at a time; the old FTP service is retired only after verification.

Typical legacy applications

No matter how old the system is, it is only retired once the new connection works.

ERP and EDI interfaces

File-based imports and exports move directly to SFTP or remain reachable through a local FTP/FTPS Bridge.

Machines and plants

Controllers keep sending CSV, XML, or log files to a familiar FTP endpoint on the production network.

Backup and archive jobs

SFTP-capable jobs receive a new target; existing FTP(S) jobs can point to the local Bridge.

Plesk and web hosting

Plesk uses Sync Bridge as its local FTP(S) backup target and reaches the SFTP storage behind it.

Cameras and recorders

Devices without SFTP support deliver exports to the Bridge inside the restricted local network.

Scripts and file clients

WinSCP, FileZilla, and automated scripts connect directly with the new host, port 22, and credentials.

Protocol comparison

FTP, FTPS, and SFTP compared.

SFTP is not encrypted FTP but a separate protocol over SSH. The client must support it – or connect through Sync Bridge.

CriterionFTPLegacyFTPSTransitionSFTPTarget
TransportDedicated FTP protocolFTP with TLSSSH File Transfer Protocol
Typical port21 plus data channels21 plus data channels22
EncryptionNone with plain FTPTLS, depending on client and configurationEncrypted SSH connection
Firewall behaviourMultiple connections and passive portsMultiple connections and passive portsOne outbound connection is sufficient
Role in the target architectureKeep only locally behind Sync BridgeTerminate locally at Sync Bridge when neededDirect connection to Managed SFTP

Managed SFTP

Managed SFTP instead of operating your own server.

The new SFTP endpoint is provided as a managed service. Connect existing clients, scripts, and systems over SFTP without operating a public SSH file service yourself.

For the United States market, Managed SFTP is provided on infrastructure in Chicago, USA.

View Managed SFTP

SFTP over port 22

Existing SFTP clients connect to the provided endpoint over the standard SSH port.

Password or SSH key

Access supports the authentication methods offered by the Managed SFTP service.

Encrypted storage

Files in managed storage are encrypted with AES-256.

From testing to scale

A free 5 GB access lets you test the connection; plans and storage can be expanded later.

Migration decision

Which migration route fits your environment?

The deciding factors are the protocols each connected system actually supports and the network boundaries that need to stay in place.

01

The client supports SFTP

SFTP can be configured in the ERP system, tool, script, or backup job.

Connect directly to Managed SFTP and test the data flow.

View Managed SFTP
02

The client only supports FTP(S)

The source system cannot technically be switched to SFTP.

Keep FTP(S) local and translate it to SFTP through Sync Bridge.

View Sync Bridge
03

The environment is mixed

Several systems, protocols, and dependencies need to be coordinated.

Combine direct and Bridge-based paths in a phased migration plan.

Discuss modernisation

FAQ

Questions about FTP modernisation.

01What is the difference between FTP, FTPS, and SFTP?

FTP has no built-in encryption. FTPS adds TLS to FTP. SFTP is a separate protocol over SSH and typically uses port 22, so an FTP client does not automatically support SFTP.

02Do all systems have to move to SFTP at the same time?

No. Assess, pilot, and cut over each connection separately. SFTP-capable systems migrate directly, while systems limited to FTP or FTPS can run through Sync Bridge in parallel.

03What happens to a system that only supports FTP?

It connects to Sync Bridge on the restricted local network. The Bridge opens the outbound SFTP connection over port 22, so no internet-facing FTP server is required.

04Do directory structures and file names need to change?

Not by default. Existing structures can usually remain. The pilot verifies permissions, file operations, and downstream processing before production cutover.

05Can I test SFTP before the migration?

Yes. A free Managed SFTP access with 5 GB can be used for connectivity and representative data-flow tests without payment details.

06How long does an FTP-to-SFTP migration take?

It depends on the number of users, directories, and connected systems. After the inventory, one representative data flow is piloted first; the remaining connections can then be moved in stages.

07Can the SFTP server remain in our own data centre?

Yes. If data must not leave your site, the existing FTP service can be replaced with a secured SFTP server on your own infrastructure. Planning, setup, updates, and monitoring can be provided as a managed service.

Next step

Check modernisation for a system.

Leave your email address, we will get in touch to discuss the next steps.