
Oct 13, 9:00 – 10:00 AM (UTC)
You're probably already moving files through Boomi Integration's SFTP Client Connector, a direct, one-off connection per flow, with nothing governing them as a group. See how routing that traffic through Managed File Transfer instead turns a scattered set of point-to-point connections into one governed relationship that MFT manages as client or server on your behalf.
*Note: The event time above is displayed in your current time zone.
A virtual webinar for Boomi customers already running file-based processes through Integration.
If your team moves files through Boomi Integration's SFTP Client Connector today, every one of those flows opens its own direct connection straight out to an external endpoint. Nothing sits above them: no shared inventory of connections, no single place to see who's connecting to what, no common governance layer. Payroll files out to providers. Bank statements in to finance. Employee data to scheduling. Bulk drops into the data lake. Each connection was hand-built, and each one is on its own.
We hear this from Boomi customers constantly, and it shows up in three places:
Cost > Development scales in a straight line: every file-based integration is a development effort that needs a specialist integration developer, so cost rises directly with the number of flows.
Efficiency > Runtime pays for the wrong work: file payloads run through the full integration runtime, so you're paying runtime charges just to move bytes. Flows also poll endpoints on a schedule instead of reacting when a file lands.
Governance > Rebuilt from zero, every time: key handling, logging, alerting, and retention get reinvented in every process, with no single audit trail and no central key store.
It gets worse with scale. Every acquisition, every new source system, every new partner or provider relationship adds one more direct connection to track, and none of it gets easier to govern centrally as the list grows.
In this session, we'll show how Boomi Managed File Transfer changes that shape entirely. Instead of dozens of direct connector-to-endpoint connections, Integration hands off to MFT once, and MFT takes over every external SFTP relationship from there, acting as client or server on your behalf. The result is one governed layer for every file transfer you run: real-time triggers instead of polling, and a single place for key management, logging, retention, and audit. Moving to MFT means retiring the SFTP Client Connector in Integration, not running both side by side.
What we'll cover
The problem: when every file move becomes an integration project
How the shift works: from direct SFTP connectors to a single governed MFT connection
Introducing Managed File Transfer: a purpose-built approach
Live demo: cost, efficiency, and governance in action
Q&A
Boomi
MFT Domain Expert
Boomi
MFT Field Engineer
CONTACT US