Sync files between SFTP servers automatically
DocEvent polls one SFTP server on a schedule and delivers every new file to another over SSH. SFTP-to-SFTP mirroring, migration and partner collection with host-key verification on both ends and a full audit trail — no scripts required.
From
SFTP Pull
To
SFTP
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How SFTP Pull to SFTP routing works
SFTP Pull
DocEvent connects to your SFTP server on a schedule and collects new files.
DocEvent Channel
SFTP Server
Files are pushed securely to an SFTP server over SSH.
1
File arrives via SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to SFTP
SSH key or password authentication. Standard port 22. Configurable remote path.
Common use cases
Real workflows that teams automate with a SFTP Pull → SFTP channel.
- Collect files from a partner's SFTP server and re-deliver them to your own
- Migrate between SFTP providers while both stay live
- Relay files from a bank or insurer portal into your regional SFTP servers
- Mirror an SFTP drop zone across environments or companies
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP Pull or SFTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder.
DocEvent connects to your SFTP server on a schedule and collects new files.Destination:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other destinations from SFTP Pull