File Offload
Your files move to external storage, and nobody notices.
by Bluemark
Written locally, kept far away
Business Plus Storage Offload moves files from the local disk to external storage — S3 or SFTP — in batches, on a schedule, and brings them back transparently when someone opens them. Uploads stay fast, because nothing leaves the server while they happen.
What you get
Scheduled, batched moves
A scheduled job takes the files out; nobody waits on the network while uploading a document.
Transparent reads
A moved file opens exactly as before — the user never learns it left the disk.
Decision rules
What moves, from what age and from what size — configured once, not decided case by case.
The “what is worth moving” analysis
How much space sits in each model and how much would be freed, before anything is moved.
Storage connectors
S3 and SFTP/FTP, on the same connector base used for imports.
It never deletes anything
Offloading moves files. Deleting is a separate decision, in a different module, under different rules.
What is worth moving
Before anything is moved, the system shows how much space sits in each model and how much would be freed — so the decision is made on figures, not on impressions.
Which questions does it answer for you?
- How much of our space is taken by files nobody opens any more?
- How much disk would we free by moving them to external storage?
- Does anything change for users if we move the files?
- From what age and what size is a file worth moving?
- What has been moved so far, when, and exactly where to?
Value for the organisation
- Postpones spending on storage without taking anything out of the system
- Keeps uploads fast, because the move happens afterwards, not during
- Shortens the backups of the local filestore
- Draws a clear line between two decisions that are often confused: what moves and what gets deleted
The files sit where storage is cheap. People open them exactly as before.