From shared drive to document system: the move in six steps

Almost every company starts the same way: a shared folder on the server, a few subfolders by year and by client, and the unwritten rule that everyone knows where their things go. It works for years. Then it stops working, and almost never because of anything dramatic. It simply becomes the case that finding something costs more time than it is worth.

This article helps you tell whether you are at that point, what a document management system genuinely changes, and how to make the move without stopping the business.

Six signs that the time has come

You do not need all of them. Three is enough.

File names have become a language. Quote_Miller_v3_final_NEW_ok.docx is not untidiness. It is an attempt to squeeze into a name what the folder cannot store: the version, the status, and who decided.

Someone asks “who deleted this?” and nobody can answer. A file that disappears from a shared folder leaves no trace. The best answer available is to restore yesterday’s backup and hope.

Permissions have become impossible. The accountant should see only invoices, the warehouse only delivery notes, payroll only the people who should see payroll. With folders you end up creating one folder per combination, and then a document lives in three places.

Search finds nothing. You are looking for an invoice and remember only the amount and the month. If that is not in the file name, you will not find it. Operating system search looks at names, not contents, and in scans it looks at nothing at all.

Working away from the office is awkward. People at a client site or on the road need the VPN, and the VPN is the thing that fails precisely when it is needed.

Nobody knows which version counts. Two people edit the same file on the same afternoon, and one of the two edits vanishes without anyone noticing until it is too late.

What a shared drive will never do

To be fair: a shared folder is not a bad tool. It does exactly one thing, hold files, and it does that well. What it does not do:

• keep earlier versions, retrievable and attributed to the person who made them;
• log who did what, meaning opened, moved, deleted, shared;
• search inside documents, including scans, which to a computer are just images;
• grant permissions per document rather than only on the folder above it;
• remember deadlines, such as a contract that renews automatically in two months;
• guarantee a reliable restore, because the network recycle bin is a convention, not a feature.

None of this is fixed by a better naming convention. These are limits of the tool.

What about SharePoint, Drive, Dropbox?

They are a step up from the folder on the server: synchronisation, access from outside, version history and a search that also looks inside files. For many teams that is enough, and it would be dishonest to claim otherwise.

Where they stop being enough is when documents stop being merely files and become business objects with a state: an invoice that has to be checked, approved and paid; a contract that expires; a certificate that loses validity. A file store knows no state, sends no reminder, and cannot tell you which contracts end in the next ninety days. It knows where the file is, and that is all.

So the useful question is not “which one is better”, but: do my documents have a life, or are they just files to keep? If they have a life, you need a system that follows it.

The move in six steps

The method that works in small companies is always the same, and the hard part is not the technical one.

1. Take stock, half a day. Look at the folder and answer three questions: how many gigabytes, which document types keep recurring (invoices, contracts, quotes, delivery notes, certificates, photos), and since when. You do not need a precise inventory, just the order of magnitude.

2. The new structure: few folders, many attributes. The most common mistake is rebuilding the same folder tree in the new system. A document system finds things by content and by attributes: document type, client, date, status. A handful of containers is enough. If you are creating your twentieth subfolder, you are almost certainly moving the problem rather than solving it.

3. The cut-off date. Pick a day: from then on, everything new goes into the system, no exceptions. This step decides the outcome, because it ends the period in which documents live in two places.

4. What moves and what stays. Not everything needs migrating. A practical rule: what is still alive moves, meaning active clients, running contracts, the current and previous financial year. The rest stays where it is, read-only, as a depot you can consult. Migrating twenty years of history before anyone has learned the tool is the surest way never to finish.

5. The people, one hour well spent. One hour together, everyone in the same room, with their own real documents. Not a presentation: upload a real invoice, search for a real contract, restore something that was deleted. Anyone who leaves that hour having found something on their own will use the system afterwards.

6. Close the old door. Two weeks after the cut-off date, set the old drive to read-only. As long as it stays writable, someone will keep saving there in good faith, and you will have two archives instead of one. Everyone postpones this step, and it is the one that decides whether the project is finished.

The five mistakes that sink the move

1. Recreating the old structure. If the folders are identical, you have only changed where the mess lives.
2. Migrating everything. The project becomes endless and people lose faith before they see the benefit.
3. No cut-off date. Without a date, the coexistence of two systems becomes permanent.
4. Leaving the old drive writable. See above. It happens every time.
5. Starting with rules instead of documents. Perfect classification schemes take three weeks to design and three days to abandon. Better to start with four document types and add more when they are genuinely needed.

How long it really takes

For a ten-person company with a few hundred gigabytes, the realistic calendar looks like this: half a day taking stock, a couple of hours deciding the structure, one day for the first import, one hour of training, then two weeks of normal use during which you adjust what does not fit. Total effort stays under one person-week, spread across roughly fifteen days.

What stretches the timeline is never the file upload. It is deciding who may see what. That question belongs on day one, not on the last day.

How it works in Blina Space

The first import is a drag and drop of whole folders: the structure is preserved, but from then on it is no longer the only way to find things. Every document goes through OCR, so a scan or a photo of a delivery note also becomes searchable text.

Permissions are granted by department or by person, not necessarily along the folders. Every action lands in the activity log, earlier versions stay available, and the recycle bin allows a restore: the three things the shared drive never had.

Contracts add expiry reminders, incoming invoices add the path from check to approval. That is exactly the difference between keeping files and following documents.

And when you want to leave, the documents export. An archive you cannot take with you is an archive that has bought you, and that applies to us too.