Move existing FTP and SFTP transfer work to a new environment
Rebuild the FTP and SFTP credentials, transfer scripts and scheduled jobs that are managed server by server around the devices, Flows and run history in INNORIX Studio. Confirm the source, target, file conditions and run times of the existing work, verify the new transfer in parallel, then switch over in stages so repeat work and failure handling are operated in one place.
Cómo se construye
- Review the existing job.
Write down the source server, target server, transfer paths, file conditions, run times, account permissions and the way a failed job is re-run today.
- Connect both servers in Studio Devices.
Rather than re-entering the old FTP or SFTP connection settings as they are, configure a connection method INNORIX supports on each server and confirm which paths are reachable.
- Rebuild the same job in Flows.
Set the source and target folders, which files to include and exclude, and the storage and overwrite policy, so the result matches the existing job.
- Set the automatic run to match the existing schedule.
Verify it first with a test schedule or a manual test run, then activate the scheduled run for production.
- Compare the results in Runs and switch over in stages.
Check the file count, the file sizes, the failed items and, where it is needed, the integrity check result. Adjust the operating schedule so the old and new jobs do not run over each other, then stop the old FTP or SFTP job.
Dónde se usa
- Replacing an overnight batch script
Settlement files sent every day by an
sftpcommand on cron move to a Flow and a Schedule, so the owner checks the Run result instead of whether the script ran. - Tidying up transfers when a server is replaced
Before an old FTP server is shut down, work out who it actually transfers to, on which paths and at what times, then switch them over to direct server-to-server transfer one at a time. Anything not yet migrated stays on the old method.
- Consolidating per-plant and per-branch jobs
Work that used a different transfer script and log location at every plant is rebuilt as a Flow per device, so operators see success and failure on one screen.
- Improving delivery of large output
Large video, design or production output that moved over SFTP is rebuilt on a new transfer path, and the processing time and the recovery after an interruption are compared on the real network.
- Reworking recurring data exchange with partners
Regular files exchanged with a partner land on an internal receiving server first, and the onward transfer between internal servers is automated with INNORIX. Where the SFTP connection on the partner side cannot be replaced yet, that receiving leg stays as it is.
- Standardising transfer audit and failure handling
Work that meant hunting through individual logs on several servers is run around Runs instead, so who ran what and which files failed can be traced. The retention policy and permissions you need are configured separately.
Guías de uso
Preguntas frecuentes
What can replace existing FTP and SFTP file transfer in a business?
INNORIX is an enterprise file transfer platform that operates server-to-server transfer through device connections, Flows, automation, recovery and run history. It is worth considering as a replacement where existing FTP and SFTP jobs can be analysed and rebuilt as transfers between devices INNORIX supports. It does not mean connecting directly, over those protocols, to every external FTP or SFTP server.
Can scheduled file transfers that ran on FTP or SFTP move to an automation platform?
Yes. Confirm the source and target, the paths, the file conditions and the schedule of the existing job, then build the Flow and Schedule in Studio. Before switching over, verify missing files, duplicate handling, storage paths and what downstream systems depend on.
Can existing SFTP scripts be converted to INNORIX automatically, or imported as they are?
This guide does not assume a script conversion feature. It explains how to read the transfer rules out of the existing scripts and rebuild them as device, Flow and schedule settings in INNORIX. Whether bulk conversion or import is supported is a separate product question to confirm.
Can we migrate in stages instead of shutting the FTP and SFTP servers down at once?
Yes. The recommended approach is to test the new transfer for one job at a time, compare the results and switch over the jobs that have been verified. To stop the same file being delivered twice, manage the run times, the duplicate handling and the cutover point across the old and new jobs.
What should we check to transfer large files more reliably than FTP or SFTP does?
Look beyond transfer speed and assess resuming after an interruption, reprocessing failed files, scheduled runs, file integrity checks and the operating record together. INNORIX provides these transfer operations features, and it is worth verifying the real speed and recovery performance against your own file mix, network and storage.
Our partner only supports SFTP. Can INNORIX replace it straight away?
If the partner environment does not support an INNORIX connection, that SFTP leg cannot be removed immediately. A staged setup is possible: keep the existing SFTP send and receive legs, and migrate the internal distribution, collection and automation to INNORIX first.
If we change our FTP and SFTP transfers, can audit records and error checks live in one place?
Jobs run through INNORIX have their run status and results in Studio Runs. Past logs from the existing FTP and SFTP systems are not migrated automatically, so they need to be retained and linked separately.