Ask most small businesses “where are your documents,” and the honest answer is: everywhere. A contract lives in an email thread from 2022. The signed version is on someone’s Google Drive. The invoice for the same project is in Dropbox, forwarded from an accountant. A related PDF is sitting in a downloads folder because someone opened it once and never filed it. None of this is unusual. It’s also not an archive — it’s just the accumulated residue of getting work done.
Why “inbox plus drives” isn’t an archive
An archive implies a few properties: everything relevant is in it, it’s organized enough to be searched, and there’s one reasonably authoritative version of each document. Email and cloud drives, individually, satisfy none of these by design — and that’s not a criticism of email or cloud storage, which are good at what they’re built for (communication and file sync). The problem is using them, together and informally, as a substitute for an archive.
Email is a stream, not storage. Attachments arrive as a side effect of a conversation. There’s no guarantee the important ones get pulled out, filed, or even survive a mailbox cleanup. Searching email for an old attachment means guessing the sender, the approximate date, and the words in a subject line that may no longer make sense out of context.
Cloud drives fragment by person and by habit. Different team members save to different drives, in different folder structures, with different naming conventions. “The contract” might be an accurate description of four different files across four different drives, each an editable draft at a different stage.
Nothing connects the pieces. The invoice, the contract it relates to, and the email thread that negotiated it usually have no link between them at all. Finding one doesn’t help you find the others — you have to remember that they’re related and go hunting separately for each.
What this fragmentation actually costs
The cost isn’t abstract. It shows up as:
- Time spent searching — multiplied across every person who needs the same document and doesn’t know where the “real” copy lives.
- Duplicate and conflicting versions, because saving a new copy is easier than finding the existing one.
- Missed obligations, because a deadline buried in an email attachment from six months ago doesn’t surface itself.
- Risk during handovers, when a departing employee’s personal drive folders quietly take organizational knowledge with them.
- Slower audits, renewals, and due-diligence requests, because “gather everything related to X” means checking four systems by hand.
None of this requires anyone to be careless. It’s the predictable result of documents arriving from several independent sources with no shared destination.
What consolidation actually fixes
The fix isn’t “use fewer tools” — email and cloud drives aren’t going away, and they shouldn’t. It’s making sure documents that arrive through those channels end up in one place that’s actually searchable, rather than staying scattered where they landed.
This is what import connectors are for. Rather than manually downloading an attachment and re-uploading it, or copying a file from a shared drive into a separate system, an import connector pulls the relevant documents in automatically and makes them part of one searchable archive alongside everything uploaded directly. Paperplane supports this for the sources documents actually accumulate in: Gmail, Outlook and IMAP mailboxes are synced on a recurring schedule (from every 15 minutes to daily), so new email attachments keep arriving in the archive. Google Drive, SharePoint, Dropbox and file servers (FTP, FTPS, SFTP) are imported folder by folder as one-time imports, which suits bringing existing files over. The point isn’t the number of connectors — it’s that documents from these places become searchable alongside every other document in the archive, instead of requiring someone to notice each one, download it, and re-file it by hand.
Consolidation also means duplicates become visible instead of invisible: when the same document arrives through two channels, having it land in one archive at least surfaces the overlap instead of quietly maintaining two disconnected copies forever.
What it doesn’t fix by itself
Importing documents into one archive doesn’t automatically organize them well, and it doesn’t decide retention or access policy for you — those still need deliberate folder structures, tags, and permissions on top. It also doesn’t retroactively fix years of scattered files the moment you connect an account; a real migration takes a first import pass and some cleanup. What it does reliably fix is the ongoing problem for email: new attachments arriving in a synced mailbox no longer have to be manually rescued to become part of a searchable, shared archive. For drives, a one-time import brings existing folders over; files added there later need another import or a direct upload. That’s the difference between an archive and a collection of places documents happen to end up.