Replace WinSCP Scripts with Xferity — Secure Managed File Transfer (MFT)
Replace WinSCP Scripts with Xferity
Section titled “Replace WinSCP Scripts with Xferity”WinSCP scripts work well at small scale. They become a liability when you have more than a few partners, inconsistent credentials handling, and no clear way to answer “what ran and when?”
Why WinSCP scripts become a problem
Section titled “Why WinSCP scripts become a problem”- credentials stored in scripts or WinSCP session storage scattered across machines
- SSH host keys accepted implicitly, not verified explicitly
- no retry logic — partial failures require manual intervention
- task history is the only investigation record
- adding a new partner means copying and modifying an existing script
- PGP encryption handled as a separate manual step
How Xferity replaces them
Section titled “How Xferity replaces them”| WinSCP script behavior | Xferity equivalent |
|---|---|
| Session with stored password | Partner definition with env: or vault: secret reference |
| StrictHostCheck=off | Partner fingerprint: SHA256:... or known_hosts_path |
put localfile remotepath | Upload flow with file matching and schedule |
| Manual rerun on failure | xferity resume <flow> with idempotency |
| Windows Task Scheduler trigger | schedule_cron in flow definition |
| No visibility | xferity flow history and xferity trace |
Migration path
Section titled “Migration path”See Tutorial: Migrating From Scripts for a step-by-step migration walkthrough.