Reduce web-server storage
Transfer suitable files to object storage and release local copies after verification.
Offload files and attachments to S3-compatible storage, free up the CRM and control access in SuiteCRM 8.
Schematic illustration · Part of the CRM process
Separate application hosting and file storage without introducing another workspace for employees.
Transfer suitable files to object storage and release local copies after verification.
A smaller local file collection can reduce backup and restore times. External files still need their own backup strategy.
Upload, open and view files on the record. Storage providers and technical paths remain in administration.
SuiteOffload connects the CRM file register to protected storage access.
Private buckets and server-side CRM permission checks control access. Setup also checks that anonymous requests are rejected.
File sizes and SHA-256 checksums support integrity verification. A successful transfer alone does not authorise deletion of the local copy.
Business modules can protect files. Local cleanup requires verified conditions and a successful restore test.
Adapters connect S3-compatible destinations. Endpoints, permissions and supported operations are checked before activation.
| Storage destination | Typical use |
|---|---|
| Hetzner Object Storage | Object storage with an appropriate region |
| Amazon S3 | Existing AWS infrastructure |
| DigitalOcean Spaces | Managed S3-compatible storage |
| MinIO / private S3 environment | Self-managed infrastructure |
| Other S3 providers | After a successful compatibility review |
Administration → Files & storage brings setup together.
Configure the profile, endpoint, region and private bucket.
Protect the access key and secret; grant only the permissions needed.
Select file classes and modules. Local copies are initially retained.
Write a test object, read it back, verify the contents, check anonymous access and remove test data.
Start after a successful test. Inventory existing files separately and transfer them in batches.
Each step remains verifiable and is tracked as a background job.
Record file counts, sizes and types. Transfer a small pilot set before processing the full collection.
Clean up only after verifying the remote copy, accounting for holds, observing the waiting period and passing a restore test.
Before switching providers or deactivating the module, copy external files back and verify them. Sufficient local storage and access to the destination are prerequisites.
A sound calculation considers more than the price per gigabyte.
Account for file storage, backup volume and recovery effort.
Include capacity, minimum charges, requests, data transfer and additional backups.
Signature evidence and invoices use the file register. The Health Center monitors storage connections and the local buffer.
Good to know about SuiteOffload.
New files can wait in the local buffer for transfer while sufficient space is available. Files stored only externally may be temporarily unavailable during an outage.
File access stays on the CRM record. Supported file classes and previews are checked during setup.
Files that exist only externally must be restored and verified before deactivation. A safeguard is intended to prevent premature removal.
No. Retention, backup and recovery must be planned separately for external files.
Explore the complementary areas of AgenticUltimate.
Help & documentation
S3 connectivity and file offloading — in the QOON Knowledge Base.
In about 20 minutes we clarify storage volume and access and show offloading and control in SuiteCRM 8.