Skip to content

Why your CRM files belong in cloud storage, not on your web server

18th November 2026

4-minutes read

Your admin system's documents are quietly filling your web server. Here’s why that’s a business risk, what you can do about it and the costs of changing

Most CRM and admin systems built for small businesses start life on a web server. Customer records sit in a database, and when someone uploads a signed contract, a product photo or a scanned invoice, the file is saved into a folder alongside the application code. It works, and for the first year or two nobody gives it much thought. The trouble is that a web server is built to run software and serve pages quickly, not to act as the long-term home for every document a business produces. As the uploads folder grows, so do the costs and risks of keeping it there.

What goes wrong when files live behind the CRM

Capacity

The first problem is capacity. Hosting plans and virtual servers come with a fixed amount of disk, and that disk is shared with the operating system, the database, logs and local backups. When uploads fill it, the whole system can stop working, not just the file area. Upgrading usually means moving to a larger server plan, so you end up paying for extra processing power and memory simply because you needed more space.

Backups

Backups become slower and more fragile. A server holding a few hundred megabytes of code can be backed up in minutes; one holding tens of gigabytes of PDFs and images takes far longer, costs more to store elsewhere and is more likely to fail partway through. Restoring after a failure takes longer too, which matters when the CRM is how your team takes orders or answers customers.

Security

Security is the third concern. Files saved under the web root can, through a misconfigured folder or a predictable file name, become downloadable by anyone who guesses the right address. Uploaded documents often contain personal data covered by UK GDPR, so an exposed folder of ID scans or contracts is a potential reportable breach rather than a minor embarrassment. Keeping files on the same machine as the application also means a single compromise exposes both the records and the documents.

Portability

Finally, there is portability. When files are tied to one server, changing host, adding a second server for resilience or rebuilding a site turns into a large file-copying exercise. Developers end up writing synchronisation scripts to keep servers in step, which is exactly the work a dedicated storage service already does.

Let the application point to the files instead

The better pattern is for the CRM to keep only a reference to each file (its name, owner, date and location) while the file itself sits in a service designed for storage. The application uploads through that service's API and, when a user needs a document, either streams it back or issues a short-lived signed link. The web server stays lean, application backups shrink to the code and database, and storage can grow without anyone touching the server.

There are two broad families of service to choose from, and they suit different kinds of file.

Collaboration platforms: SharePoint and Google Drive

If your staff already use Microsoft 365 or Google Workspace, storing CRM documents in SharePoint or Google Drive has obvious appeal. People can open, edit and share files with tools they already know, permissions follow existing staff accounts, and version history is built in. For documents people actively work on, such as proposals, contracts awaiting signature or project files, this is often the most practical home.

The storage comes bundled with your licences. Microsoft gives each organisation a pooled allowance of 1TB plus 10GB per eligible licence. Beyond that, the Extra File Storage add-on costs about £0.15 per GB per month on an annual commitment, or around £150 per TB per month, which is expensive for bulk material such as image libraries. Google Workspace Business Standard includes 2TB of pooled storage per user, shared across the organisation, which for a small team may be more than the CRM will ever need.

The drawback is that these platforms are designed around people rather than applications. Their APIs are capable but take more setup, typically registering an app and managing OAuth tokens, and their usage limits suit staff browsing files better than a system writing thousands of them. They make a good home for documents, but a poor one for every thumbnail and export a CRM generates.

The principle stays the same: let the web server run the application and let a storage service do the storing

Object storage: Amazon S3

Object storage is built for software. You create something called a "bucket", which is simply a repository for files. Your code writes files into it and you pay for what you store and what you move. Amazon S3 is the best-known example and is supported by almost every framework and library. In the London region, S3 Standard costs about £0.018 per GB per month, or roughly £18 per TB.

Storage is only part of the bill, though. Data leaving AWS for the internet is charged at about 7p per GB once you pass the first 100GB each month, and requests are billed separately. A CRM that mostly stores files and rarely serves them will find S3 affordable; one that serves large images to the public all day may find transfer charges outweigh the storage itself.

Lesser-known options worth considering

Several smaller providers offer S3-like storage, which means code written for Amazon usually works after changing little more than the endpoint and access keys. Backblaze B2 is the most established of them. It charges about £5.20 per TB per month, the first 10GB is free, and downloads are free up to three times the amount you store, then less than 1p per GB. For a business holding a terabyte of documents, that is well under a third of the S3 storage price and a small fraction of SharePoint's add-on rate, with fewer surprises on the invoice.

Wasabi takes a flat-rate approach without egress fees, and raised its price to about £6 per TB per month from July 2026; it also applies a 90-day minimum storage period, so files deleted soon after upload are still billed. Cloudflare R2 costs about £11 per TB per month and does not charge for data leaving the service, which makes it attractive when files are downloaded or displayed frequently, such as product images on a website.

The trade-off with smaller providers is a narrower set of surrounding services and, in some cases, fewer data centre locations. If your compliance obligations require data to stay in the UK or EU, confirm which regions a provider offers before you commit.

Choosing the right fit

For most small businesses the answer is a combination. Documents that staff need to open and edit belong in SharePoint or Google Drive, where the licences you already pay for cover the space.

Bulk files the CRM receives or generates, such as images, attachments, exports and archives, belong in object storage, where the cost per terabyte is far lower and the API is designed for software rather than people.

Several of these providers bill in US dollars, so the sterling figures above are approximate conversions at around 75p to the dollar and will move with the exchange rate. Check current rates before you build them into a budget.

Whichever services you choose, the principle stays the same: let the web server run the application, and let a storage service do the storing.

Stuck with an old admin system that costs your business in lost time or high running costs? Call Rubiqa on 01332 331332 and ask for Jeremy

Learn moreArrow
Jeremy Flight

Jeremy Flight

Technical Director

Related articles