Cloud Storage DMS Sync Hub

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.