OneDrive & Google Drive Document Sync

Key Features

Two-way sync between Odoo and Google Drive (Drive API v3) and Microsoft OneDrive/SharePoint (Graph API) over OAuth2 with encrypted, auto-refreshed tokens

`drive.sync.rule` model mapping any Odoo model (`sale.order`, `project.project`, `account.move`, `hr.employee`) to a destination folder convention

Auto-folder provisioning per record driven by `compute` fields (`@api.depends`), e.g. `Sales/2026/SO0042/` on first sync

Attachment offloading at the `ir.attachment` layer to move blobs out of the Postgres filestore while keeping a record link

Bidirectional reconciler comparing local checksum against remote `modifiedTime`/`eTag` with configurable conflict resolution (newest-wins, Odoo-wins, or manual)

Selective sync rules scoped by model, record domain, MIME type, size threshold, or Odoo tag

Shared-link generation via provider API (view/edit scope) written back to an Odoo field for one-click access

`ir.cron` scheduled sync plus queued jobs so large batches never block the request/response thread

On-demand sync smart button and status widget in the form view (XML/OWL) for manual pushes

`drive.sync.log` audit model recording direction, remote file id, checksum, and error detail per operation

Access controlled by `ir.model.access.csv` and record rules — sync config is admin-only, users see only entitled links

Idempotent, retry-safe sync with exponential backoff on API rate limits (Drive/Graph 429s) and resumable uploads for large files

XML-RPC / JSON-RPC endpoints so external systems can trigger sync or read link fields

Built and tested for Odoo 17.0, 18.0 and 19.0, Community or Enterprise, with the right `__manifest__.py` dependencies per edition

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Teams that already live in Google Drive or Microsoft OneDrive end up maintaining two parallel filing systems: quotations, contracts, delivery notes and project files pile up as ir.attachment blobs inside Odoo while the "real" copy sits in a shared drive that finance, legal and external partners actually open. Odoo's native Documents app (Enterprise) can store and tag files, and Community can attach them to records, but neither reaches out to an external cloud drive, mirrors changes back, or offloads the Postgres/filestore bloat that thousands of PDFs create. The result is duplicated uploads, stale versions, and "which folder is the latest contract in?" every week.

ECOSIRE builds a dedicated integration module that connects Odoo to Google Drive (Drive API v3) and Microsoft OneDrive / SharePoint (Graph API) over OAuth2, with tokens stored encrypted and refreshed automatically. At its core is a drive.sync.rule model (models.Model) that maps any Odoo model — sale.order, project.project, hr.employee, account.move — to a destination folder convention, plus a drive.sync.log model that records every push/pull with status, remote file id, and checksum. Attachments are intercepted at the ir.attachment layer so files saved in the chatter or Documents propagate to the cloud, and a bidirectional reconciler compares Odoo's copy against the remote modifiedTime/eTag to decide direction and resolve conflicts. Folder creation is driven by compute fields (@api.depends) so, for example, each confirmed sale order auto-provisions Sales/2026/SO0042/ on first sync.

The heavy lifting runs as an ir.cron automated action and via queued jobs so large batches never block the request thread; you can also trigger an on-demand sync from a smart button in the form view (XML/OWL). Selective sync rules let you scope by model, record domain, file type, size threshold, or Odoo tag, so you sync signed contracts but not 200 draft revisions. Shared-link generation calls the provider API to mint view/edit links (respecting each drive's permission model) and writes them back to an Odoo field for one-click access from the record. Access is governed by ir.model.access.csv and record rules so sync configuration stays admin-only while end users only see links they are entitled to, and everything is exposed over Odoo's XML-RPC / JSON-RPC API for external automation.

Because this is a build-to-order engagement, we start from your actual filing conventions rather than a generic template. After a short scoping call we confirm which models sync, the folder-naming scheme, conflict-resolution policy, and whether you need Drive, OneDrive, or both. We build against your target version — Odoo 17.0, 18.0, or 19.0, Community or Enterprise — deliver on a staging instance for UAT, then install on production with a documented rollback. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the full source in a git repository so nothing is locked behind a black box.

What you get

Installable module source code built for your exact Odoo version (17.0/18.0/19.0) and edition

Installation and configuration on your environment, including OAuth app registration guidance for Google Cloud and Microsoft Entra

Technical documentation: model/field reference, sync-rule schema, cron schedule, and API endpoints

End-user guide plus a live training session for admins and daily users

UAT on a staging instance with sign-off, and a documented production rollback plan

Post-go-live support window for defect fixes and configuration tuning

Full git repository handover with commit history and branch structure

Seed configuration of your initial sync rules and folder conventions

Who this is for

Google Workspace / Microsoft 365 teams

Organizations already standardized on Drive or OneDrive who want Odoo records to file themselves into the shared drive automatically instead of staff re-uploading documents by hand.

Operations and document controllers

People responsible for keeping contracts, delivery notes, and compliance files in one authoritative place, who need per-record folders and version reconciliation rather than scattered attachments.

Odoo administrators and IT leads

Admins who need attachment offloading to control filestore/Postgres growth, granular access control via record rules, and a clean OAuth setup they can audit.

Finance and project managers

Users who live in spreadsheets and shared drives and want one-click shared links from the Odoo record — quotations, invoices, and project files reachable without logging into Odoo.

How OneDrive & Google Drive Document Sync Compares

Criterion	ECOSIRE	Custom Build	Competitor
Two-way sync with Drive & OneDrive	Built in, both providers, conflict rules included	Possible but you design and maintain it	Often one provider or one-way only
Auto-folder per record	Compute-driven naming to your convention	Hand-coded per model	Fixed or shallow folder mapping
Attachment offloading	Selective offload of filestore blobs to cloud	Requires careful `ir.attachment` work	Rarely offered
Selective sync rules	Model, domain, MIME, size, tag scoped	Whatever you build	Usually all-or-nothing
Version fit (17/18/19)	Built for your exact version and edition	You own version upgrades	May lag new Odoo releases
Support & source ownership	Support window + full git repo handover	In-house team owns everything	Vendor-locked, ticket queue
Delivery model	Build-to-order, 2-4 weeks, UAT + rollback	Weeks to months, you staff it	Instant download, generic fit
Shared-link generation	API-minted links written back to record	Extra work per provider	Sometimes, view-only

Frequently Asked Questions about OneDrive & Google Drive Document Sync

How long does delivery take?

Because this is a build-to-order module, we build it for your exact setup rather than shipping a stock download. Typical delivery is 2 to 4 weeks from confirmed scope — the range depends on how many Odoo models you sync, whether you need both Drive and OneDrive, and your conflict-resolution and folder-naming rules. We confirm the timeline in writing after the scoping call.

Does it work with both Google Drive and OneDrive, or only one?

Both are supported. Google Drive uses Drive API v3 and OneDrive/SharePoint uses the Microsoft Graph API, each over OAuth2. You can enable one or both; if you only need one provider we scope out the other to keep the build lean.

Is the sync truly two-way, and how are conflicts handled?

Yes. A file changed in Odoo is pushed to the drive, and a file changed in the drive is pulled back, using each side's checksum and modified timestamp/eTag to decide direction. Conflict policy is configurable — newest-wins, Odoo-wins, or flag-for-manual-review — and every decision is written to the `drive.sync.log` audit trail.

Will it reduce our Odoo filestore and database size?

It can. Attachment offloading moves file blobs from the Odoo filestore to the cloud drive while keeping a lightweight record link and shared link. You choose which models and file types offload via selective sync rules, so critical attachments can stay local while bulk documents move out.

Which Odoo versions and editions are supported?

We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. The `__manifest__.py` dependencies differ by edition — for example integrating with the Enterprise Documents app versus Community's base attachment layer — and we target whichever you run.

What support and updates come after go-live?

Every engagement includes a post-go-live support window for defect fixes and configuration tuning. Because you receive the full source in a git repository, you are never locked in. We also offer ongoing support and version-migration retainers if you want us to maintain compatibility as you upgrade Odoo or as the Drive/Graph APIs change.

Is our data secure during sync?

OAuth2 tokens are stored encrypted and refreshed automatically — no passwords are held. Access to sync configuration is restricted via `ir.model.access.csv` and record rules, shared links respect each provider's permission model, and all traffic uses the providers' HTTPS APIs. We can also scope sync so sensitive record domains never leave Odoo.