IBM MQ MFT alternative with predictable file transfer costs

SFTPPlus MFT is a cost-effective alternative to IBM MQ Managed File Transfer when your main requirement is exchanging files with partners and business applications. It brings together file transfer servers, automated client transfers, encryption, and audit records in one service. You can keep existing IBM MQ applications while changing how files reach them.

Decide which parts of MQ MFT to replace ​

Start by separating file delivery from application messaging. If a workflow only moves files between systems, SFTPPlus can transfer directly over standard protocols without involving MQ. You can retire the queue managers and MQ MFT agents dedicated to that workflow once their other dependencies have been checked.

When business applications still use MQ messages, keep their queue manager and change only the file delivery boundary. SFTPPlus can provide partner access without requiring partners to install MQ MFT agents.

SFTPPlus does not replace the queue manager or act as an MQ MFT agent within an existing agent network. Use the IBM MQ integration reference to check the supported endpoints and technical constraints before selecting a migration candidate.

Reduce the components you operate ​

SFTPPlus has a self-contained runtime. It does not require Java, an external application server, or a configuration database. This gives an operations team fewer runtime dependencies to deploy, patch, and monitor for a standalone file exchange service. It also makes SFTPPlus easier to deploy in a container or on Kubernetes. The Web Manager brings administration into the same service.

Compare the proposed hosting, backup, monitoring, and support effort with your current deployment. Keeping an existing MQ estate may be economical when staff and infrastructure already support it. Removing a component only saves money if the remaining applications no longer depend on it.

Predictable licence costs as transfer volumes grow ​

An SFTPPlus MFT Client licence costs US$1,900 and includes automated transfers to IBM MQ and other supported destinations. Add the US$1,900 Server licence when partners need to connect to your SFTP, FTPS, HTTPS, or AS2 services. Both capabilities run in the same installation.

Check the current pricing and maintenance terms before ordering.

The licences do not cap users, concurrent connections, transfer counts, file sizes, or CPU cores.

IBM MQ MFT costs depend on queue manager capacity and existing entitlements. Our IBM MQ MFT comparison compares SFTPPlus MFT with IBM MQ MFT alone.

Plan a gradual migration ​

The Server and Client price includes transfer scheduling, retry handling, PGP file protection, and audit logging. There are no separate protocol or partner packs for the supported connectors. Account for any external business processing that your current workflow performs, since changing the transfer software does not automatically replace that processing.

Agree access policies, log retention, recovery procedures, and support hours before comparing final quotes.

1. Inventory the current transfers, partner interfaces, delivery requirements, and dependencies on MQ agents or mainframe data sets.
2. Select a workflow that can use standard file protocols or the supported SFTPPlus queue connector.
3. Use the included testing environment to verify delivery, failure recovery, access controls, and the audit evidence your operators need.
4. Move that workflow into production with a rollback plan, then remove unused MQ MFT components after confirming that no other application needs them.

IBM MQ MFT is a better fit when you need its agent network, large-file transport over MQ, or native z/OS data set transfers. You can retain those workflows and use SFTPPlus for partner-facing file exchange. The feature comparison explains both products' strengths and limitations.

Request a trial or contact our team with your current topology and the transfers you want to simplify.