Moving off JSCAPE
Stop patching your JSCAPE server. Keep everything your partners rely on.
Your JSCAPE MFT Server is an internet-facing server you patch, license and watch yourself. SFTP.cloud runs that part for you. Your hostname, accounts, keys and storage stay as they are, and the inbound port on your network closes.
JSCAPE details checked against Redwood, JSCAPE and NVD sources on 18 October 2026.
Who patches the server
You, on every release
We do
Inbound ports on your network
Open to the internet
None. The Connector only dials out
Hostname, accounts and storage
Yours
Still yours, unchanged
01Why teams move
A file transfer server is the first thing attackers scan for. Yours is on your network.
Running JSCAPE yourself means you own its exposure: the open port, the patch window and the server that holds your files and partner credentials.
September 2023CVE-2023-4528
Remote code execution as root or SYSTEM.
Unsafe deserialization in the JSCAPE MFT Server management interface let an attacker run arbitrary Java code, including operating system commands, on every version before 2023.1.9. Every self-hosted server stayed exposed until its own team installed the fix.
Every dayInbound port
Your server answers anyone who connects.
Partners reach JSCAPE through a port open to the internet, so does every scanner and botnet. Each login attempt lands on a machine inside your network, next to your files.
Every releaseYour team
Patching is your job, on your schedule.
JSCAPE ships regular releases. Each one is yours to test, schedule and install on every server you license, while partners wait for the maintenance window to end.
On SFTP.cloud, partners connect to us. Your network has no inbound port left to find.
How we secure it02What you keep
Your partners keep connecting the way they do today. One thing changes.
Most migrations stall on the partners: nobody wants to ask a hundred companies to change their scripts. You only need to tell them about one thing.
What stays the same
Hostname, accounts, files.
Export your JSCAPE users into the SFTP.cloud CSV template and import it, or create accounts through the API. See the CSV template
- Keep your hostname, such as sftp.yourcompany.com, with a DNS record
- Import usernames, passwords and SSH public keys, so nobody resets a password or swaps a key
- Bring folder permissions across with each account
- Point your Storage Connector at the disk or share JSCAPE uses today. No files move
What changes
The server’s host key.
SFTP clients check a server’s host key on every connection. SFTP.cloud has its own, so partners see a new fingerprint the first time they connect.
- Send partners the new fingerprint before you switch DNS
- Partners who pin host keys in scripts update one value
- Interactive clients ask once, then connect as before
Same address, same login, same files. A new key, announced in advance.
03Migration steps
Six steps, with JSCAPE running until the last one.
You run the migration yourself, following our documentation. Nothing is switched off until your partners are already working on SFTP.cloud.
- 01
Start a trial and connect your storage.
Install a Storage Connector next to the disk, share or bucket JSCAPE writes to today. It only makes outbound connections.
- 02
Import your accounts.
Export users from JSCAPE into the SFTP.cloud CSV template: usernames, passwords, SSH public keys, home folders and permissions. Import it in the Portal or through the API.
- 03
Test with one partner.
Run both side by side. Ask a friendly partner to connect to SFTP.cloud directly and confirm uploads land where they did before.
- 04
Announce the new host key.
Send partners the SFTP.cloud host key fingerprint and the date of the switch, so pinned keys are updated in time.
- 05
Switch DNS.
Point your hostname at SFTP.cloud. Partners keep the address and credentials they already use.
- 06
Retire the JSCAPE server.
Once traffic has moved, close the inbound port, shut the server down and let the licence lapse.
Your partners change one key. You stop running a server.
Not ready to retire JSCAPE?
Keep it, and close its inbound port anyway. SFTP.cloud can sit in front of your existing SFTP server as its storage, so partners connect to us and your JSCAPE server is no longer reachable from the internet.
04Before you decide
What JSCAPE does that SFTP.cloud does not.
SFTP.cloud covers SFTP, FTPS, FTPES and HTTPS. If you use JSCAPE for more than that, check these first. Each comes with a trade-off worth weighing.
- 01
Partners on AS2 or OFTP2.
SFTP.cloud does not offer AS2 or OFTP2. If EDI partners require them, you need another service for those connections. The trade-off is keeping a server for them, so move every SFTP and FTPS partner and shrink what is left exposed.
- 02
WebDAV or plain FTP.
SFTP.cloud does not accept unencrypted FTP or WebDAV. Partners still on plain FTP move to FTPS or FTPES, which most FTP clients already support. The trade-off is one client setting per partner, in exchange for no passwords sent in clear text.
- 03
JSCAPE MFTaaS, Redwood’s hosted version.
JSCAPE MFTaaS is hosted and managed by Redwood, which removes the patching. The trade-off is that you change platform anyway, and the server your partners connect to runs on Redwood’s infrastructure instead of handing files straight to storage you own.
You do not need the JSCAPE Gateway either. With no inbound port, there is no DMZ to proxy.
05FAQ
Moving off JSCAPE, common questions.
Can I keep my current SFTP hostname?
Yes. Point your existing hostname, such as sftp.yourcompany.com, at SFTP.cloud with a DNS record. Partners keep the address they already use.
Will my partners have to change anything?
Only the host key. SFTP.cloud cannot reuse your JSCAPE server’s host key, so partners see a new fingerprint the first time they connect. Send it to them before you switch DNS.
Do partners need new passwords or SSH keys?
No. The SFTP.cloud CSV template carries usernames, passwords, SSH public keys and folder permissions, so partners sign in exactly as before.
Do my files have to move?
No. Your Storage Connector can point at the same disk or network share JSCAPE uses today, and files keep landing there.
Does SFTP.cloud store my files?
No. Files stream through the Storage Connector you run next to your storage and are never written to a disk we own. The Connector only makes outbound connections, so there is no inbound rule to your network.
Does SFTP.cloud support AS2?
No. SFTP.cloud supports SFTP, FTPS, FTPES and an HTTPS web client. Partners that need AS2 or OFTP2 will need another service.
Do you migrate it for me?
Migration is self-service and documented step by step. You can run SFTP.cloud alongside JSCAPE for as long as you need before switching.
Can I keep JSCAPE and just close the inbound port?
Yes. SFTP.cloud can use your existing SFTP server as its storage. Partners connect to SFTP.cloud, which passes files to your JSCAPE server over an outbound connection, so the server is no longer exposed to the internet.
Run it next to JSCAPE for fourteen days.
Connect the storage JSCAPE uses, import a few accounts and test with one partner before anything changes. No credit card, and nothing to cancel if it is not for you.
Want the details first? Read about security or SFTP for on-premises storage.