Business file transfer: pick the method by the job, not the brand

Size decides whether email is even an option

Email is the default for business file transfer because everyone already has it. It stops being an option the moment the file is large, and the failure is quiet. The message bounces, or gets silently trimmed by the recipient's mail system, and you find out three days later when they ask where it is.

If you're regularly sending video, design files, scans or a folder of exports, treat email as the notification and not the carrier. Send a link, and let the file sit somewhere built to hold it. I've written separately about what to do when a file is too big to upload and about sending several files at once by email, and both come down to the same move.

Frequency decides whether you need a system or a tool

A one-off transfer is a tool problem. A transfer that happens every night, with no human involved, is a system problem. This is the line between a link and managed file transfer (MFT), the enterprise category built around schedules, retries and audit logs.

If a job runs at 2am and someone needs to be told when it fails, you want MFT, and you want your IT team involved. I covered the protocols behind it (SFTP, FTPS, AS2) in secure file exchange, so I won't repeat them here.

If nobody in your business has ever described a transfer as "a job", you almost certainly don't need it. The bigger enterprise suites are a governance purchase more than a transfer one, which is what enterprise file sharing is about.

The other end decides more than the software does

This is the part most guides skip. Your tool might be perfect and the transfer still fails because of the person receiving it.

Their IT team might block the domain your link comes from. Their phone might not open the format. They might be signed into a personal account and hit an access wall. They might just not want to create yet another login to read one file, so they reply asking you to attach it, and you're back at email.

Before you commit to a method for a client or supplier you'll deal with repeatedly, ask them what they'd like. It takes one line. It's also the cheapest fix in this whole post. For a one-off with someone you don't know, pick the option with the fewest hoops for the recipient, not the fewest for you.

Business file transfer to people outside the company

Moving files inside a company is mostly solved by whatever drive your team already uses. The awkward case is the external recipient: a client, an investor, a supplier, a candidate.

There are roughly three approaches, and each has a catch.

A shared-drive link (Google Drive, OneDrive, Dropbox) is fine and free-ish, but access settings are easy to get wrong, and once a link is out you may not be sure who has it. A dedicated transfer service is better for large one-off sends, but the link usually expires on its own timer rather than yours. A portal or data room gives you the most control, and the most overhead for everyone involved. Direct link file sharing covers how links behave and where public ones go wrong.

What I'd look for is simple. Can the recipient open it without an account? Can you shut the link off after the fact? And can you tell whether it landed? Plenty of tools answer the first two. Very few answer the third.

Proof it arrived is not proof it was read

A transfer that completed is not a transfer that worked. The file arrived, and the person still never opened it. Or opened it, saw 40 pages, and read the first two.

For anything where the contents matter (a proposal, a set of accounts, a report someone's paying for), I care less about the delivery receipt and more about what happens next. That's the gap between sending a file and sending a document someone understands.

This is the one place I'll mention what I built. LiveDocument lets you share a PDF or an image as a single link, with a recorded video walkthrough attached and page-level analytics showing how long the reader spent on each page. If your job is "get this document to this person and know it landed", that's what it's for.

It isn't a transfer tool in the MFT sense. It's not storage, it doesn't move files between systems on a schedule, and it's not a data room. Access control covers link expiration, revocation and named-email restriction, not a full governance suite, and there's no watermarking or NDA gating. For the 2GB design pack or the nightly feed, use something else. For the proposal you'd otherwise attach and hope about, it's a better fit. I've compared it to the usual alternatives in file sharing software.

A short way to choose

Run the job through four questions, in this order.

1. How big is it? Over what email will carry, use a link.
2. How often? Nightly or automated, look at MFT. Occasional, a link is enough.
3. Who's receiving? Ask them, or pick the lowest-friction option for them.
4. Does it matter that they read it? If yes, you need more than a delivery receipt.

If you want the security side of this decision, secure file sharing for business starts with access control, which is where I'd start too.

For documents going to outsiders, see cloud document sharing for business.

FAQ