Every ERPNext site accumulates attachments — sales order PDFs, item images, expense receipts, quality inspection photos, employee documents — and by default the File DocType writes all of them straight to the bench's local sites/<site>/private/files and public/files directories on the application server. On a high-attachment-volume site that disk fills relentlessly: your frappe-bench volume balloons, backups take longer and cost more, bench migrate and restore windows grow, and eventually you are resizing the server for storage you should never have been paying compute prices for. ERPNext core has no native concept of routing attachments to object storage, no per-folder storage policy, and no built-in migration path — so teams end up bolting on cron rsync hacks or symlinking files/ to a mount, both of which break on bench update, backups, and multi-bench setups.

We build a proper Frappe app (installable via bench get-app / bench install-app) with its own module that intercepts file writes through hooks.py doc events on the File DocType — after_insert, on_trash, and validate — so that attachments in the folders you designate are streamed to an S3-compatible bucket (AWS S3, MinIO, Wasabi, Backblaze B2, DigitalOcean Spaces, or any endpoint that speaks the S3 API) instead of the local disk. Routing is driven by a configuration DocType where you map Frappe File folders to target buckets and policies, so, for example, Home/Attachments/Item Images can go to a public CDN-backed bucket while Home/Attachments/HR stays in a strictly private bucket. Credentials live in encrypted site config, never in the database or code, and every storage backend is validated on save.

File access stays transparent to end users. When a private attachment is requested, the app issues a short-lived presigned URL through a whitelisted method rather than proxying bytes through the Frappe worker, so downloads don't tie up gunicorn/worker processes and large files stream directly from the object store. Public-bucket files can be served straight from a CDN origin for image-heavy DocTypes. A one-time migration tool — implemented as a Frappe scheduler/background job so it doesn't block the request cycle — walks existing File records folder by folder, uploads each object, verifies integrity, rewrites the file_url / content_hash linkage, and (optionally, after a verification pass) reclaims the local disk. Permissions are unchanged: the app respects Frappe's existing File permission model, role profiles, and the private/public distinction, so a presigned URL is only ever minted for a user who is already entitled to that attachment.

Because this is build-to-order, we don't hand you a generic plugin and wish you luck. We start with a short scoping call to confirm your ERPNext version (v15 or v16), attachment volume, which folders and DocTypes need offloading, your target object store, and whether you need public/CDN delivery, private-only, or a mix. We then build your version of the app, test it on a staging copy of your site including a dry-run of the migration against a snapshot of your real files, run UAT with you, and cut over with a documented rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source and git repository so you are never locked to us.