Apps › Sell online and connect platforms

EspoCRM Connector

Accounts, contacts, leads and opportunities come from EspoCRM into Odoo's contacts and CRM, nothing goes back, and a new instance runs in dry-run until you switch it off.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsCRM, Contactsno Enterprise module
Price89 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.0.14bambooforge_espocrm_connector

110 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

How you use it

Three flows, in the order you will meet them

Flow 01

Connect: one instance per EspoCRM server, dry-run first

Test Connection proves the address and the key, and the first import writes nothing.

  1. In Odoo: EspoCRM Connector > Configuration > Instances > New. Enter the server's address and the API user's key.
  2. Press Test Connection. The state turns Connected and Status Mappings gets twelve rows.
  3. On the Import tab, set each import limit above the number of records of that type, then press Queue Account Import and Queue Contact Import.
  4. Read Operations > Logs and Validation Results, untick Dry Run Mode and import again.
The EspoCRM instance form: the server's address, the API key field, state Connected and the Safety tab with Dry Run Mode
Flow 02

Accounts, contacts, leads and opportunities come in

Each record type lands where Odoo keeps it.

  1. Accounts become company contacts with their type and industry.
  2. Contacts become people, under their company when the account came first.
  3. Leads and opportunities become CRM leads with EspoCRM's status or stage kept as text; tick CRM's Leads setting to see the leads.
Flow 03

A failed job lands in a list, not in silence

Every job is retried, set aside after its last try, and shown with its error.

  1. Open the Control Tower: one card per instance with its backlog, dead letters and conflicts.
  2. Open Dead-letter, fix the cause the error names, and requeue the jobs.

Price and where to buy

89 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.