It Never Pays to Roll Your Own File Transfer System for Large Files

by Ipswitch Blog Posted on December 29, 2015

Picture a rural health system sending large, high-res brain scans from a stroke patient to a city hospital for analysis. Now picture a field engineer sharing 3-D AutoCAD files of a new oil field with decision-makers at corporate. Imagine an enterprise migrating stored data from an old data center to a new one. Today's collaborative workforce, in almost every industry, depends on big file transfer capabilities.

When it comes to many professional indulgences, you've enjoyed the advantages of "rolling your own." But big file transfers, despite your good intentions to save money, are't something to do by yourself. When you take an honest look at the simplicity (and security) of today's managed file transfer solutions, it makes no sense to go solo. DIY file transfer systems puts a big strain on your already overextended IT department, and poses big challenges for regulatory compliance due to the security risks involved.

DIY File Transfer Systems for Larger Files Make No Sense

Without clear policies in place, employees usually send large files over email or use a consumer file transfer application. With Microsoft Exchange, for instance, you have a 10-gigabyte default attachment size limit; Gmail has a 25GB limit. MIME encoding bloats the file even more, which confuses your users ("How can my 20GB attachment be too big when the limit says 25?" They'll ask). Even if it gets out of your network, the recipient rejects the attachment, resulting in delivery failure. Plus, when you're backing up your email servers, these large attachments require a lot of storage space.

When delivery fails, your senders usually open up your worst enemy: the consumer file transfer app, such as Dropbox, which doesn't actually transfer the file to a recipient. Instead it stores it in a cloud, and the recipient gets a link. The safety of your file, therefore, depends on third-party cloud security. If employees use several different apps, you've not only lost control of data security in transit; you have no idea where sensitive data lives.

Why Not Automate With FTP?

Many IT departments develop ad hoc file transfer scripts to meet the varying needs of their customers. Your IT department may even be using legacy scripts created by employees who've since left the company. It's also likely they're not updating these scripts to satisfy the demands associated with transferring a high volume of large files, both in and out of the enterprise. With usernames, IP addresses are libraries constantly in flux; it's inconvenient for IT to tweak automation scripts all the time. When it comes to large file transfers, there's no reason for your IT department to be coordinating a process they should have delegated a long time ago.

The inconvenience of updating automation scripts isn't FTP's biggest hindrance. Big file transfers via FTP can be incredibly slow depending on your network's upload speeds. When the transfer hits a firewall, or when sessions time out, FTP doesn't support automated transfer resume.

Also, opening additional ports means increasing your network security risk, and FTP transfer itself just isn't secure. A Ponemon Institute study shared by Computer Weekly revealed that 44 percent of IT leaders felt they had no ability to control user access to sensitive documents. Additionally, six in 10 admitted sending sensitive files to the incorrect recipients. Imagine a large healthcare organization sharing a patient's file from a picture-archiving and communication system (PACS) over FTP and delivering it to the wrong recipient or exposing it to a data breach. Or imagine a critical patient file arriving hours later over FTP while a patient anxiously awaits scan results. A managed file-transfer solution, automated from within the PACS workflow, would eliminate these problems.

Rolling Your Own Just Isn't Worth It

Rolling your own is usually about two things: thriftiness and craftsmanship. In terms of the latter, though, few IT decision-makers can create a file transfer system that's as fine-tuned as a managed solution. And when you face significant costs related to lost files, process management or regulatory fines, rolling your own becomes pretty expensive.

Going with an MFT solution will take a lot of work and worries off your plate.


Ipswitch Blog
View all posts from Ipswitch Blog on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
More from the author

Related Articles

Managed File Transfer (MFT) vs. File Transfer Protocol (FTP)
This article provides the detailed features comparison needed when the need for file transfer moves from occasional to operational.
File Transfer vs. SOAP?
"Why are we still FTP'ing files to each other in 2010?"
Is PSD2 Good for Banks And How Should IT Teams Implement It?
The EU’s PSD2 directive (a revised payment service directive) aims to regulate electronic payments in EU member countries. It has no impact on traditional paper-based transactions.
How to Choose the Right Managed File Transfer Solution
For the purposes of this post, we are concerned with two relevant options, namely File Transfer Protocol (FTP) and Managed File Transfer (MFT). The second, being managed, obviously offers more features than a standard file transfer solution. But, which solution is best...
How to Avoid Scripting Nightmares for File Transfers
Scripting is a popular and powerful choice to automate repeatable file transfer tasks. It can be horrifying, though, to discover just how many scripts are relied on for the successful operation of your infrastructure. This and the time they take to execute are sure to...
Prefooter Dots
Subscribe Icon

Latest Stories in Your Inbox

Subscribe to get all the news, info and tutorials you need to build better business apps and sites

Loading animation