Organize Odoo attachments into folder trees and two-way sync them to Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box. One-time license from $349.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Organize Odoo attachments into folder trees and two-way sync them to Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
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
Configurable path templates using record fields and @api.depends compute logic — build folder names from company, document type, date, partner or any field, matching your existing naming convention
Internal vs public shareable link control per file: generate time-limited public links for external parties or keep documents internal-only, governed by a dedicated field and record rules
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.
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.
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.
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.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Cloud Storage DMS Sync Hub 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Cloud Storage DMS Sync Hub,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| Automatic directory creation per record | Via base.automation on create, template-driven | You wire the automated actions | Limited / manual filing | |
| Internal vs public share-link control | Per-file, time-limited, rule-governed | Build it yourself | Sometimes, coarse-grained | |
| 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 | |
| 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 |
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 2–4 weeks 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.
Yes. Every build includes a post-launch support and bug-fix window (typically 30–90 days, specified in your quote) 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.
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.
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.
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.
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.
Organize Odoo attachments into folder trees and two-way sync them to Google Drive, OneDrive/SharePoint, Nextcloud, Dropbox, S3 and Box.