SFTP Gateway Support

3.0

v2 to v3 Migration Overview

Overview

This section of our documentation will include a series of KB articles covering the topic of migrating SFTP Gateway from v2 to v3.

This page provides an overview of why you should upgrade to v3, as well as an outline of the overall process.

Version 2 is reaching EOL

SFTP Gateway v2 is reaching EOL on December 31, 2024.

Version 2.0 has served our customers well for several years, but with the release of Version 3.0 in 2023, we made significant advancements in security, scalability, and performance.

We will now focus on supporting and enhancing Version 3.0 to provide the most robust and reliable user experience possible.

For a limited time, Thorn Technologies is offering a special incentive on migration projects to help you move from SFTP Gateway version 2 to version 3. Discounts on the regular marketplace list price for 1 year and consulting services are available. Contact sales@thorntech.com to request a customized proposal.

Reasons to upgrade to version 3

SFTP Gateway v3 includes features that customers have requested over the years:

  • Read and write live files to Blob storage directly from your SFTP client (e.g. WinSCP)
  • Deploys as a single VM or in an HA configuration
  • Supports more than one Blob Storage Account
  • Supports multi-cloud (Azure Blob, AWS S3, Google Cloud GCS)
  • Supports multiple public keys per SFTP user
  • Configure key exchange algorithms from the web portal
  • Web admin users can log in via OIDC
  • and much more

There have also been a lot of performance and stability enhancements to v3. Our custom Java application can handle larger workloads. Also, v3 uses Blob storage as the SFTP file system, so you don't have to worry about running out of disk space.

Finally, SFTP Gateway v3 is also built on a more recent operating system (Ubuntu 22.04 LTS). So migrating can help you get caught up on security.

Migration outline and overview

Migrating from v2 to v3 involves taking a backup of v2 and importing it into v3. When you're ready, you can perform a DNS or IP cutover. This process is covered in this KB article.

Many customers have expressed that version 2 hosts critical production SFTP infrastructure, and they need a comprehensive plan to make sure the v2 to v3 migration happens as safely and smoothly as possible.

Based on helping customers migrate from v2 to v3, we have learned that there are a lot of preparatory steps you can perform in advance that do not impact production. And the more of these prep steps that you perform up front, the smaller the leap you take when performing the cutover.

Here are the high-level steps in a v2 to v3 migration (links to KB articles are coming soon):

  • Create a test user in v2
  • Make an application backup of v2
  • Deploy SFTP Gateway v3
  • Import your backup into SFTP Gateway v3
  • Make post-configuration changes to make v3 behave like v2
  • Verify server host keys
  • Configure key exchange algorithms
  • Plan your DNS or IP cutover
  • Testing and using pilot groups
  • Pre-cutover checklist
  • Performing the cutover
  • Sunsetting the v2 server
  • Maintenance mode and cost optimization
← PreviousNext →