Teams that self-host their file storage do it on purpose: they want documents on infrastructure they control, not scattered across a vendor's object store. Odoo, though, keeps attachments in ir.attachment — either as base64 blobs in the database or under the filestore directory — with no native concept of syncing those files to an external WebDAV server, no per-record folder structure a user can browse in a Files app, and no way to hand someone a shareable link that respects your access rules. The moment you want a sales order's contracts sitting in a Nextcloud folder your legal team can open directly, or a public link to a datasheet that expires, Odoo core runs out of road and people fall back to manually re-uploading files in two places.

We build a dedicated Odoo module that bridges ir.attachment and the Nextcloud/ownCloud WebDAV + OCS Share API. A configuration model (with credentials stored in ir.config_parameter / a secured settings model, never hard-coded) holds the server URL, service account, and root path. New models.Model records extend the attachment and target document models with fields tracking the remote path, share token, sync state, and last-synced hash, using compute methods with @api.depends to surface a clean status in the UI. Per-record folder mapping is driven by a configurable template (for example /Odoo/{model}/{record_name}-{id}) so every partner, project, sale order, or DMS document gets a deterministic folder created on first sync. Two-way sync reconciles both directions: files added or replaced in Odoo push up over WebDAV, and changes detected on the Nextcloud side are pulled back and re-attached, with conflict handling based on modified-time and content hash so you never silently lose an edit.

Link generation uses the OCS Share API to mint either an internal link (visible only to the mapped Nextcloud group/users) or a public share, with optional password and expiry, exposed on the Odoo record through a QWeb-rendered button and stored so it can be embedded in QWeb reports or emails. Visibility is access-rights-aware: the module ships ir.model.access.csv entries plus record rules so a user only sees links and folders for records they can already read in Odoo, and public-link creation can be gated to specific groups. A scheduled automated action (ir.cron) runs the background sync on an interval you choose, batched and rate-limited to stay friendly to your Nextcloud instance, with a full sync log and a manual "sync now" action for on-demand pushes. Everything is reachable over Odoo's XML-RPC/JSON-RPC API too, so external systems can trigger syncs or read share URLs programmatically.

Because this is a build-to-order module, nothing ships until we agree on scope. We start with a short scoping call to confirm which models you want synced (attachments only, DMS documents, or specific business records), your Nextcloud/ownCloud version and auth method, and your Community-vs-Enterprise edition on Odoo 17.0, 18.0, or 19.0. We then build against a staging copy of your database, validate the two-way sync and link behavior in UAT, and deliver the installable module with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source, documentation, a training session, and a post-go-live support window — and the git repository is yours to keep.