Once an Odoo estate grows past a single company, document storage becomes a quiet liability. Attachments pile into the Odoo filestore, backups balloon, and different teams already live in different clouds — Finance in SharePoint, Sales in Google Drive, Operations on Dropbox, and the platform team archiving to Amazon S3. Odoo core stores every attachment as an ir.attachment row, either as a filestore blob on disk or a base64 field in the database, with no notion of routing a document to the right provider or reflecting that governance decision per company or document type. You can bolt on one cloud with a settings toggle, but the moment you need several providers, per-model rules, and a real audit trail, Odoo native runs out of road.

We build a single connector framework that sits behind ir.attachment and treats each provider as a pluggable backend under one generic interface. On top of it runs a policy engine — new models such as document.sync.policy and document.sync.provider with their own security via ir.model.access.csv and record rules — that decides, for any attachment, which cloud it belongs in based on the Odoo model (res_model), the company_id, or a document-type classifier you define. Routing is evaluated the moment a document is created through an @api.model_create_multi extension and re-evaluated by scheduled ir.cron jobs, so both real-time and batch flows are covered. Each provider gets its own queue with exponential backoff, so a throttled or briefly offline cloud retries cleanly instead of blocking the user or losing the file. An access-token vault stores per-provider OAuth credentials with automatic refresh, isolated per company so a multi-tenant deployment never leaks one tenant's token to another.

The technical heart is storage offload with integrity guarantees. In offload mode the heavy blob leaves the Odoo filestore and is replaced by a lightweight pointer, so your database and on-disk backups shrink while the file stays one click away — two-way link resolution renders the external document directly on the Odoo record via an OWL widget, and checksum verification plus cross-provider deduplication ensure a file is stored once and provably intact. Where a provider exposes version history, we mirror document versions so your Odoo record and the cloud stay in step. A central sync dashboard (list, kanban, and graph views over a document.sync.log model) shows per-document status, storage reclaimed, and one-click error retry, while a compliance audit trail records who synced what, to which cloud, and when — exportable to CSV or reachable programmatically over Odoo's XML-RPC/JSON-RPC API. Bulk migration and provider-to-provider re-routing tools let you move an existing library between clouds without touching the originating records. The module builds only on base, mail, and web, works on Community and Enterprise alike, and ships for Odoo 17.0, 18.0, and 19.0.

Because this is built to order, nothing is downloaded and switched on blind. We start with a short scoping call, confirm your providers, company structure, and routing rules in a written scope, then build, test on a staging clone of your database, and install with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional providers, multi-company or multi-tenant credential isolation, and the volume of historical documents migrated increase the quoted scope. You get the final fixed quote after the scoping call — never a surprise on delivery.