Skip to content
CRM ⇄ ERP

Close to Odoo integration — real-time, two-way sync

Keep Close and Odoo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Close and Odoo

Close the gap between front office and back office: Close and Odoo share customers and status in real time, in both directions.

Close holds the customer relationship; Odoo runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.

Stacksync syncs Leads, Contacts, Opportunities, Activities in Close with Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead) in Odoo field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
  • Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.

Where Odoo is the finance system of record: money status on the account

Invoice and payment state from Odoo shows on the account in Close, so reps see balances before promising the next order.

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

Where Odoo manages people and org data: keep Close aligned

Owners, territories, and org structure informed by Odoo stay current in Close.

What you can sync between Close and Odoo

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Close objects Odoo objects
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools.
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems.
Users Sales reps referenced as owners on leads, opportunities, and activities. Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Employees (hr.employee) HR records read for directory and provisioning syncs.
What ships with Close ⇄ Odoo

Connect Close and Odoo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Odoo connection.

Real-time

Two-way sync

Changes in Close or Odoo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Close or Odoo record.

Observability

Monitoring

Track your Close ⇄ Odoo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Odoo.

How the Close and Odoo connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

Odoo

Integration surface
XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
Authentication
Database user credentials or per-user API keys
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

How to connect Close to Odoo — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Close and Odoo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Odoo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close and Odoo objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Odoo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Odoo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Close and Odoo integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Close and Odoo.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.