Illustrative previewOrganize Odoo attachments into folder trees and two-way sync them to Google Drive,
OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box.
What is Cloud Storage DMS Sync Hub?
Organize Odoo attachments into folder trees and two-way sync them to Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Odoo already stores every quotation PDF, contract, ID scan and photo as an ir.attachment record — but out of the box those files live in a flat blob store or filesystem your team never sees, and there's no clean way to mirror them onto the cloud drives your company already pays for. Cloud Storage DMS Sync Hub is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports for you. It gives your attachments a real structure — a browsable folder tree per company, per model and per record — and keeps that structure two-way synchronized with Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, Amazon S3 and Box.
Because this is a bespoke build (not an off-the-shelf apps.odoo.com download), we tailor the module to your exact naming conventions, your provider mix, and your security model. When a sales order, invoice, project task, employee record or helpdesk ticket is created, the module can automatically create a matching directory (for example /Odoo/Sales/2026/SO-01042/) and route new attachments there, then push them to your chosen cloud drive over its native API. Files dropped into the mirrored folder on the cloud side flow back into Odoo as attachments on the correct record, so your finance team on SharePoint and your field team on Drive are looking at the same documents your ERP is.
Under the hood the module is built on Odoo's own primitives. New models (models.Model) extend ir.attachment and add a dms.folder / dms.sync.provider layer; @api.depends compute fields derive folder paths and sync status; ir.cron jobs and base.automation (automated actions) drive scheduled and event-triggered syncs; access is locked down with ir.model.access.csv plus record rules so users only see the folders their department owns; and OWL/QWeb views give you a document-explorer UI inside the backend. Public-versus-internal share links are controlled per file, so you decide exactly what leaves your walls. It runs on Odoo 17, 18 and 19, on both Community and Enterprise, and we hand over the full source so you're never locked in.
What you get
- Complete, commented Odoo module source (models, security, views, data, __manifest__.py) delivered as a versioned Git repository you own outright — no runtime license lock-in
- Installation and deployment on your Odoo 17, 18 or 19 environment (Community or Enterprise), including on-premise, Odoo.sh or ECOSIRE-managed hosting
- Provider connection setup and testing for each cloud drive you use — OAuth2 app registration guidance and credential configuration for Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and/or Box
- Custom folder-path templates and sync rules configured to your naming conventions, models and department structure
- Administrator and end-user documentation plus a live training session (recorded) covering folder management, share-link control and troubleshooting sync
- A post-launch support and bug-fix window (two weeks) with response SLAs
- Bulk backfill of your existing historical attachments into the new folder structure and cloud drives, run and verified with you
Who this is for
Operations / IT Manager standardizing document storage
Wants every Odoo document to live in the company's existing cloud drives (SharePoint, Drive, Nextcloud) instead of a hidden ERP blob store, with a folder structure staff already understand — and needs it enforced automatically, not by hoping people file correctly.
Finance & Compliance lead needing an audit-ready paper trail
Must keep invoices, contracts and signed documents mirrored to a governed, backed-up cloud location with clear internal-vs-public access, plus a per-file audit trail showing what synced where and when.
Growing SME already paying for cloud storage
Already runs Google Workspace, Microsoft 365 or Nextcloud and doesn't want a second document silo. Wants Odoo attachments and their cloud drive to be one and the same, so field, office and finance teams see identical files.
How Cloud Storage DMS Sync Hub Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Structured folder tree per model & record (not a flat blob store) | Full hierarchy, path templates from any field | Possible but you design & maintain it | Basic folders, fixed structure | Flat ir.attachment store, no real folders |
| Connectors for all six drives (Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3, Box) | All six, enable any subset | Only what you have time to build | Usually one or two providers | S3/Azure filestore offload only, no folder sync |
| Two-way sync with conflict handling | Event + ir.cron, last-write conflict resolution | Only if you build the reconcile logic | Often one-way (Odoo→cloud) push | None |
| Automatic directory creation per record | Via base.automation on create, template-driven | You wire the automated actions | Limited / manual filing | Not available |
| Internal vs public share-link control | Per-file, time-limited, rule-governed | Build it yourself | Sometimes, coarse-grained | Basic attachment share URL, no governance |
| Tailored to your naming rules, providers & security model | Yes — built to your spec | Yes, but on your engineering budget | No — fixed to vendor's design | No |
| Full source ownership + support/upgrade path (17/18/19) | Git repo you own + ECOSIRE support retainer | You own it and you maintain it | Vendor-licensed, renewal-dependent | Core Odoo, no DMS sync feature |
Frequently Asked Questions about Cloud Storage DMS Sync Hub
This is a build-to-order module — how long until it's live and what's the delivery process?
Correct: this is not an instant apps.odoo.com download. ECOSIRE designs, builds, installs and supports the module for you, with a typical lead time of one working week depending on how many providers you connect and how custom your folder/path rules are. The flow is: a short scoping call to confirm your Odoo version, provider mix and naming conventions, then development, then installation on your environment with connection testing, a backfill of existing attachments, and a training handover. You'll get progress checkpoints along the way, not a black box.
What happens after launch — do I get support and updates?
Yes. Every build includes a post-launch support and bug-fix window (two weeks) with response SLAs. Because we hand over the full source in a Git repo you own, you're free to maintain it yourself afterward, or keep ECOSIRE on a support/maintenance retainer for provider-API changes, Odoo version upgrades (17→18→19) and new features. If a cloud provider changes its API, we'll patch the connector under an active support agreement.
Which cloud providers and Odoo versions are supported?
Out of scope by default are none of the six — the module ships connectors for Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, Amazon S3 and Box, and you can enable any subset. It runs on Odoo 17, 18 and 19, on both Community and Enterprise editions. Additional providers (e.g. Backblaze B2, WebDAV endpoints) can be added as a scoped extension since each connector is built to a common interface.
Is the synchronization really two-way, and how are conflicts handled?
Yes. Files attached in Odoo are pushed to the mapped cloud folder, and files placed into that folder on the cloud side are pulled back into Odoo as ir.attachment records on the correct record. Sync runs both on attachment create/write events and on a scheduled ir.cron pass so it self-heals. Conflicts (the same file changed on both sides) are detected via last-write timestamps and surfaced in the sync-status dashboard with a retry/resolve action, so nothing is silently overwritten.
How is access controlled, and can I keep some documents internal-only?
Access is enforced with Odoo's native security — ir.model.access.csv plus record rules — so users only see the folders and files their department/group owns. Each file has internal-vs-public control: you can generate a time-limited public shareable link for external parties, or keep a document strictly internal. You decide per model, per folder or per file which documents may ever leave your walls.
Will this bloat my Odoo database, and can it handle our existing attachment history?
No — the goal is the opposite. Files are mirrored to your cloud drives, and we can configure Odoo to offload storage to the provider (S3 in particular) rather than keeping large blobs in the filestore/database. For your history, the build includes a resumable bulk backfill that sweeps existing attachments into the new folder structure and pushes them to the cloud in controlled batches, verified with you before it's considered done.
Related Modules
Checkout Trust Badges & Express Conversion Kit for Odoo
A build-to-order Odoo eCommerce module that adds trust seals, an accepted-payment badge row, express wallet placement, an inline coupon and shipping estimator, and low-stock urgency cues to your checkout. ECOSIRE scopes, builds, installs, and supports it for Odoo 17, 18, or 19.
Claude AI Connector
A build-to-order Odoo module that exposes your ERP to Claude AI through the Model Context Protocol, letting an assistant read and act on live Odoo data under your own security rules. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0, 18.0, and 19.0.
Complete HR Suite
A build-to-order 35-module HR platform for Odoo covering attendance, leave management, payroll, and recruitment as one integrated suite. ECOSIRE scopes, builds, installs, and supports it for your organization — it is made to order, not an instant download.
Conekta Payment Gateway for Odoo (Mexico)
A build-to-order Odoo payment provider that accepts Mexican cards, OXXO cash vouchers, and SPEI bank transfers through Conekta, with webhook reconciliation and MXN localization. ECOSIRE builds, installs, and supports it after a scoping call — it is not an instant apps.odoo.com download.
Cloud Storage DMS Sync Hub
Organize Odoo attachments into folder trees and two-way sync them to Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box.
- Structured folder trees for every ir.attachment — browsable directory hierarchy per company, per Odoo model (sale.order, account.move, hr.employee, project.task, helpdesk.ticket) and per record, replacing Odoo's flat attachment blob store
- Native connectors for six providers — Google Drive, OneDrive/SharePoint, Nextcloud (WebDAV), Dropbox, Amazon S3 and Box — each using the provider's official API/SDK with OAuth2 or key-based auth stored securely in ir.config_parameter
- Two-way file synchronization: attachments uploaded in Odoo push to the cloud, and files dropped into the mirrored cloud folder flow back as ir.attachment records on the matching record, with conflict handling and last-write timestamps
- Automatic directory creation per record via base.automation (automated actions) and model create hooks — e.g. a new SO generates /Sales/2026/SO-01042/ on both sides with no manual filing