SFTPPlus MFT vs IBM MQ MFT
Compare SFTPPlus MFT Server and Client with IBM MQ Managed File Transfer (MFT).
SFTPPlus MFT
- First year
- $4,750
- Following years
- $950
Licensing
- Perpetual licence availableSFTPPlus offers perpetual licences. IBM offers perpetual PVU licensing as well as the VPC subscription used in this example. Details
- Yes
- Licence price independent of CPU coresSFTPPlus is licensed per installation and capability. IBM MQ licensing uses processing capacity, such as VPCs or PVUs. Details
- Yes
- No per-file transfer chargeNeither compared self-managed software offering is billed by individual transferred file. Capacity and infrastructure still affect throughput and cost. Details
- Yes
- Included supported testing instanceSFTPPlus includes testing use under its licence and support terms. Supported IBM MQ test and staging environments need suitable non-production entitlements; IBM's free developer edition does not include that support. Details
- Yes
Runtime and deployment
- Windows and LinuxBoth support Windows and Linux. SFTPPlus MQ integration requires x64 and does not support Windows Server Core or Nano. Details
- Yes
- Java-free transfer runtimeSFTPPlus uses its bundled Python and C runtime. IBM MQ MFT uses a Java runtime. Details
- Yes
- No queue manager required for deploymentSFTPPlus can transfer directly between standard file endpoints. IBM MQ MFT requires queue managers for its agent network. Using the SFTPPlus MQ connector also requires a queue manager. Details
- Yes
- No external configuration databaseNeither product needs an external database for basic transfer configuration. IBM's optional database logger has separate database requirements. Details
- Yes
- Native z/OS agentIBM provides MFT for z/OS under the corresponding entitlements. SFTPPlus does not run natively on z/OS; it can connect from a supported host. Details
- No
File transfer protocols
- SFTP clientSFTPPlus initiates SFTP transfers directly. IBM's protocol bridge agent connects an MFT network to an external SFTP server; it does not host one. Details
- Yes
- FTP and FTPS clientsSFTPPlus initiates FTP and FTPS transfers directly. IBM's protocol bridge agent connects an MFT network to external FTP and FTPS servers. Details
- Yes
- Built-in SFTP, FTP, and FTPS serversSFTPPlus accepts partner connections. IBM MQ MFT's protocol bridge connects to external servers but does not provide partner-facing SFTP, FTP, or FTPS servers. Details
- Yes
- HTTPS browser uploads and downloadsSFTPPlus includes a browser file client. IBM removed the MFT Web Gateway in MQ 9.0, so MQ MFT alone does not provide a partner browser portal. Details
- Yes
- AS2 send and receiveSFTPPlus includes AS2. IBM MQ MFT does not provide AS2; a separate product is needed for that transport. Details
- Yes
- WebDAVSFTPPlus provides WebDAV services and client transfers. WebDAV is not an IBM MQ MFT protocol bridge transport. Details
- Yes
- IBM MQ file-to-message transfersBoth can exchange file content with application queues. SFTPPlus maps each file to one persistent binary message. Details
- Yes
- IBM MQ MFT agent protocolIBM coordinates transfers between its MFT agents. SFTPPlus connects to application queues and cannot replace an agent within that protocol. Details
- No
- SharePoint Online connectorSFTPPlus transfers documents using Microsoft Graph. IBM MQ MFT does not include a SharePoint Online connector. Details
- Yes
- Azure Blob and File Storage connectorsSFTPPlus has native Azure Storage clients. IBM MQ MFT does not include these cloud storage connectors. Details
- Yes
- Oracle table rows as file transfer endpointsSFTPPlus MFT reads and writes Oracle table rows as files using configured SQL. IBM MQ MFT can log transfer events to Oracle, but it does not provide this file endpoint connector. Details
- Yes
- Connect:Direct bridgeIBM provides a Connect:Direct bridge agent; the Connect:Direct node needs its own entitlement. SFTPPlus does not implement this protocol.
- No
Administration and integration
- Primary transfer administration toolsSFTPPlus Web Manager configures SFTPPlus MFT. IBM uses MQ Explorer, commands, properties, and REST APIs for MFT administration, with MQ Console for queue manager administration. Details
- Web Manager, CLI, API
- Command-line administrationBoth provide commands for transfer administration and operation. Details
- Yes
- Administration APISFTPPlus provides a JSON-RPC management API. IBM provides REST endpoints for supported MFT operations, including agent and transfer monitoring. Details
- Yes
- Configuration in one text fileSFTPPlus stores its configuration in an INI file. IBM MFT uses properties and XML files alongside MQ objects. Details
- Yes
Automation
- Scheduled transfersBoth support unattended transfers at configured times and repeated schedules. Details
- Yes
- Local folder monitoringBoth can trigger transfers when files appear in a monitored local directory. Details
- Yes
- Remote SFTP folder monitoringSFTPPlus polls remote SFTP folders for new files. IBM resource monitors cannot run on protocol bridge agents, so MQ MFT does not provide this polling workflow. Details
- Yes
- Transfer recoveryBoth provide recovery mechanisms after connection failures. SFTPPlus retries configured operations; MQ MFT recovers transfers within its agent topology. These are not identical delivery guarantees. Details
- Yes
- External processing commandsBoth can call external programs as part of transfer processing. Such programs have their own deployment and support requirements. Details
- Yes
Security and identity
- TLS for MQ connectionsBoth support TLS and client certificates for MQ connections, subject to compatible queue manager security settings. Details
- Yes
- Built-in OpenPGP file processingSFTPPlus encrypts, decrypts, signs, and verifies OpenPGP files. MQ Advanced Message Security protects messages, not OpenPGP files. Details
- Yes
- Partner web login with Entra ID, Okta, or GoogleSFTPPlus authenticates browser file transfer users through these providers. IBM MQ MFT alone has no partner web client. Details
- Yes
Other features
- Files larger than one MQ message over MQIBM MFT agents transport large files across multiple messages. The SFTPPlus MQ connector requires each file to fit in one message; this limit does not apply to its SFTP or HTTPS transfers. Details
- No
- Split file content into application messagesIBM supports splitting files by length or delimiters and assembling message groups into files. SFTPPlus MQ transfers use one message per file.
- No
- Native z/OS data set transfersIBM MFT handles z/OS data sets and generation data groups. SFTPPlus requires another service to expose mainframe data through a supported interface.
- No
High availability and audit
- File transfer audit logsBoth record transfer activity. SFTPPlus also records its user and administrator actions; IBM publishes MFT status and supports file and database loggers. Details
- Yes
- Automated transfer failoverSFTPPlus provides active and passive transfer nodes with a separate cluster licence. IBM supports highly available MFT agents. Cluster licences and redundant capacity are outside both prices. Details
- Cluster licence
Support
- Technical support and updates availableBoth displayed prices include support and software updates for their respective products. Details
- Yes
- 24/7 Severity 1 support for the entire deploymentIBM Software Subscription and Support includes continuous assistance for Severity 1 issues. The SFTPPlus price uses standard support, which covers office hours and two scheduled out-of-hours events; continuous coverage requires extended services. Details
- No
IBM MQ MFT
- First year
- $6,996
- Following years
- $6,996
Licensing
- Perpetual licence availableSFTPPlus offers perpetual licences. IBM offers perpetual PVU licensing as well as the VPC subscription used in this example. Details
- Yes
- Licence price independent of CPU coresSFTPPlus is licensed per installation and capability. IBM MQ licensing uses processing capacity, such as VPCs or PVUs. Details
- No
- No per-file transfer chargeNeither compared self-managed software offering is billed by individual transferred file. Capacity and infrastructure still affect throughput and cost. Details
- Yes
- Included supported testing instanceSFTPPlus includes testing use under its licence and support terms. Supported IBM MQ test and staging environments need suitable non-production entitlements; IBM's free developer edition does not include that support. Details
- No
Runtime and deployment
- Windows and LinuxBoth support Windows and Linux. SFTPPlus MQ integration requires x64 and does not support Windows Server Core or Nano. Details
- Yes
- Java-free transfer runtimeSFTPPlus uses its bundled Python and C runtime. IBM MQ MFT uses a Java runtime. Details
- No
- No queue manager required for deploymentSFTPPlus can transfer directly between standard file endpoints. IBM MQ MFT requires queue managers for its agent network. Using the SFTPPlus MQ connector also requires a queue manager. Details
- No
- No external configuration databaseNeither product needs an external database for basic transfer configuration. IBM's optional database logger has separate database requirements. Details
- Yes
- Native z/OS agentIBM provides MFT for z/OS under the corresponding entitlements. SFTPPlus does not run natively on z/OS; it can connect from a supported host. Details
- Yes
File transfer protocols
- SFTP clientSFTPPlus initiates SFTP transfers directly. IBM's protocol bridge agent connects an MFT network to an external SFTP server; it does not host one. Details
- Yes
- FTP and FTPS clientsSFTPPlus initiates FTP and FTPS transfers directly. IBM's protocol bridge agent connects an MFT network to external FTP and FTPS servers. Details
- Yes
- Built-in SFTP, FTP, and FTPS serversSFTPPlus accepts partner connections. IBM MQ MFT's protocol bridge connects to external servers but does not provide partner-facing SFTP, FTP, or FTPS servers. Details
- No
- HTTPS browser uploads and downloadsSFTPPlus includes a browser file client. IBM removed the MFT Web Gateway in MQ 9.0, so MQ MFT alone does not provide a partner browser portal. Details
- No
- AS2 send and receiveSFTPPlus includes AS2. IBM MQ MFT does not provide AS2; a separate product is needed for that transport. Details
- No
- WebDAVSFTPPlus provides WebDAV services and client transfers. WebDAV is not an IBM MQ MFT protocol bridge transport. Details
- No
- IBM MQ file-to-message transfersBoth can exchange file content with application queues. SFTPPlus maps each file to one persistent binary message. Details
- Yes
- IBM MQ MFT agent protocolIBM coordinates transfers between its MFT agents. SFTPPlus connects to application queues and cannot replace an agent within that protocol. Details
- Yes
- SharePoint Online connectorSFTPPlus transfers documents using Microsoft Graph. IBM MQ MFT does not include a SharePoint Online connector. Details
- No
- Azure Blob and File Storage connectorsSFTPPlus has native Azure Storage clients. IBM MQ MFT does not include these cloud storage connectors. Details
- No
- Oracle table rows as file transfer endpointsSFTPPlus MFT reads and writes Oracle table rows as files using configured SQL. IBM MQ MFT can log transfer events to Oracle, but it does not provide this file endpoint connector. Details
- No
- Connect:Direct bridgeIBM provides a Connect:Direct bridge agent; the Connect:Direct node needs its own entitlement. SFTPPlus does not implement this protocol.
- Yes
Administration and integration
- Primary transfer administration toolsSFTPPlus Web Manager configures SFTPPlus MFT. IBM uses MQ Explorer, commands, properties, and REST APIs for MFT administration, with MQ Console for queue manager administration. Details
- MQ Explorer, CLI, APIs
- Command-line administrationBoth provide commands for transfer administration and operation. Details
- Yes
- Administration APISFTPPlus provides a JSON-RPC management API. IBM provides REST endpoints for supported MFT operations, including agent and transfer monitoring. Details
- Yes
- Configuration in one text fileSFTPPlus stores its configuration in an INI file. IBM MFT uses properties and XML files alongside MQ objects. Details
- No
Automation
- Scheduled transfersBoth support unattended transfers at configured times and repeated schedules. Details
- Yes
- Local folder monitoringBoth can trigger transfers when files appear in a monitored local directory. Details
- Yes
- Remote SFTP folder monitoringSFTPPlus polls remote SFTP folders for new files. IBM resource monitors cannot run on protocol bridge agents, so MQ MFT does not provide this polling workflow. Details
- No
- Transfer recoveryBoth provide recovery mechanisms after connection failures. SFTPPlus retries configured operations; MQ MFT recovers transfers within its agent topology. These are not identical delivery guarantees. Details
- Yes
- External processing commandsBoth can call external programs as part of transfer processing. Such programs have their own deployment and support requirements. Details
- Yes
Security and identity
- TLS for MQ connectionsBoth support TLS and client certificates for MQ connections, subject to compatible queue manager security settings. Details
- Yes
- Built-in OpenPGP file processingSFTPPlus encrypts, decrypts, signs, and verifies OpenPGP files. MQ Advanced Message Security protects messages, not OpenPGP files. Details
- No
- Partner web login with Entra ID, Okta, or GoogleSFTPPlus authenticates browser file transfer users through these providers. IBM MQ MFT alone has no partner web client. Details
- No
Other features
- Files larger than one MQ message over MQIBM MFT agents transport large files across multiple messages. The SFTPPlus MQ connector requires each file to fit in one message; this limit does not apply to its SFTP or HTTPS transfers. Details
- Yes
- Split file content into application messagesIBM supports splitting files by length or delimiters and assembling message groups into files. SFTPPlus MQ transfers use one message per file.
- Yes
- Native z/OS data set transfersIBM MFT handles z/OS data sets and generation data groups. SFTPPlus requires another service to expose mainframe data through a supported interface.
- Yes
High availability and audit
- File transfer audit logsBoth record transfer activity. SFTPPlus also records its user and administrator actions; IBM publishes MFT status and supports file and database loggers. Details
- Yes
- Automated transfer failoverSFTPPlus provides active and passive transfer nodes with a separate cluster licence. IBM supports highly available MFT agents. Cluster licences and redundant capacity are outside both prices. Details
- Yes
Support
- Technical support and updates availableBoth displayed prices include support and software updates for their respective products. Details
- Yes
- 24/7 Severity 1 support for the entire deploymentIBM Software Subscription and Support includes continuous assistance for Severity 1 issues. The SFTPPlus price uses standard support, which covers office hours and two scheduled out-of-hours events; continuous coverage requires extended services. Details
- Yes
Comparison criteria
This comparison covers SFTPPlus MFT Server and Client and IBM MQ MFT supplied through MQ Advanced. The IBM column represents MQ MFT alone, without a partner-facing gateway. Its protocol bridge can connect to external FTP, FTPS, and SFTP servers but does not host those services for partners. Feature descriptions identify additional entitlements or external services where needed.
The SFTPPlus price includes Server and Client licences and standard support for one production installation. The IBM price uses IBM's indicative $583 per Virtual Processor Core (VPC) per month for MQ Advanced with AI Agents, or $6,996 per year for one VPC. It is an illustrative minimum subscription, not a capacity recommendation or a quote for an existing MQ customer's upgrade. An existing MQ Advanced entitlement with sufficient capacity may change the incremental MFT cost. Check IBM's licence guidance against your contract and topology.
The displayed prices do not include hosting, implementation, additional production instances, high availability, or optional z/OS and Connect:Direct entitlements. They also do not include an IBM partner gateway. For a comparison with an IBM partner-facing gateway, see SFTPPlus MFT vs IBM Sterling Secure File Transfer.
Why choose SFTPPlus MFT
SFTPPlus is a better fit when you need partner-facing file transfer services with predictable software costs and no dependency on an MQ MFT agent network. It includes partner-facing servers and client orchestration in one service, with web administration, PGP processing, and audit records. You can connect standard file protocols directly or retain IBM MQ integration for applications that need messages.
Its runtime does not require Java, an external application server, or a configuration database. It includes remote folder polling and SharePoint, Azure Storage, and Oracle connectors. Choosing SFTPPlus avoids operating MQ MFT when its agent capabilities are not needed. The IBM MQ MFT alternative solution describes a gradual migration using these capabilities.
When to retain IBM MQ MFT
IBM MQ MFT is a better fit for an established MQ agent network where agent-to-agent transfers are central to the workflow. It retains the monitoring, security, and recovery processes that operations teams already manage for MQ MFT. It transfers large files over MQ without requiring the entire file to fit in one message, supports file splitting and message group assembly, and integrates with z/OS data sets and Connect:Direct. SFTPPlus does not implement those agent and mainframe capabilities.
IBM also provides highly available agents and 24/7 assistance for Severity 1 issues under Software Subscription and Support. For an organization already entitled to MQ Advanced, these capabilities and the existing investment can outweigh the benefit of changing transfer platforms.
Evidence and updates
Reviewed on 13 October 2026 against SFTPPlus MFT 6 and IBM documentation, primarily for MQ 9.4, with current public pricing. This is a documentation comparison, not a performance benchmark or a measured infrastructure saving.
If a capability or licence term has changed, contact us with the product version and supporting documentation.