Odoo – Close CRM Connector | Close - Odoo Connector | Odoo Close Integration
by Waqas Mustafa https://www.linkedin.com/in/waqas-mustafa-ba5701209/$ 150.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Contacts (contacts) • Discuss (mail) • Project (project) • Calendar (calendar) |
| Lines of code | 1250 |
| Technical Name |
odoo_close_connector |
| License | LGPL-3 |
| Website | https://www.linkedin.com/in/waqas-mustafa-ba5701209/ |
| Versions | 16.0 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Contacts (contacts) • Discuss (mail) • Project (project) • Calendar (calendar) |
| Lines of code | 1250 |
| Technical Name |
odoo_close_connector |
| License | LGPL-3 |
| Website | https://www.linkedin.com/in/waqas-mustafa-ba5701209/ |
| Versions | 16.0 17.0 18.0 |
-
Community
-
Enterprise
Odoo ⇌ Close CRM Connector: Bi-directional CRM Sync
Click Here for Complete Manual Guide
https://docs.google.com/document/d/1j9Io1XDyIErzUFh5k9z7RG7FgResHVNTGoOxHjyQe6g/edit?usp=sharing
Seamlessly integrate Odoo with Close CRM for complete CRM synchronization. Keep your contacts, leads, tasks, and notes in perfect sync across both platforms with powerful bi-directional synchronization.
Perfect for businesses using both Odoo and Close CRM who want to maintain a single source of truth across platforms. Features smart pagination, duplicate prevention, and incremental sync for maximum efficiency.
Full bi-directional sync with field mapping and user assignments
Pipeline and stage mapping with monetary values and related contacts
Sync tasks with contact linking, deadlines.
Multiple safety layers prevent duplicate records across systems
Handles unlimited contacts and opportunities with efficient API usage
Configurable cron jobs (5-60 minutes) plus manual "Sync Now" button
- Name, Email, Phone, Mobile
- Address (Street, City, State, Zip, Country)
- Assigned User
- Website
- Opportunity Name
- Expected Revenue (Monetary Value)
- Internal Notes (Syncs bi-directionally with Close Opportunity Note)
- Related Contact
- Assigned User
- Pipeline Stage
- Task Title
- Priority Level (Normal / High Star mapping)
- Due Date
- Close CRM Dedicated Time & Date
- Assigned User
- Related Contact/Lead
- Note body/content
- Author (if user is mapped)
- Related record (contact or opportunity)
Possible Causes:
- Incorrect API Key
- API Key does not have sufficient permissions
Solutions:
- Double-check API Key
- Try creating a new API Key in Close CRM
Check:
- Is "Sync Contacts" enabled in settings?
- Is the Sync Direction set to Bi-directional or Close CRM → Odoo?
- Check if the record has a valid email address.
Check:
- Is "Sync Opportunities" enabled?
- Is the opportunity's stage mapped in Pipeline Mapping?
- Is the opportunity type set to "Opportunity" (not "Lead")?
Fix: Map the stage in Close CRM → Configuration → Pipeline Mapping
The current code has triple protection against duplicates and cannot create them. Existing duplicates were likely created before the module was installed or manually.
Solution: Manually merge duplicates. The connector will maintain the link going forward.
- Test connection before enabling sync
- Map all users and pipeline stages before syncing
- Start with a small test dataset
- Use reasonable polling intervals (5-15 minutes)
- Regularly check Last Sync Timestamps
- Maintain clean contact data (valid emails, phones)
- Link tasks to contacts
- Enable sync on production data without testing
- Skip user and pipeline mapping
- Manually edit Close CRM ID fields
- Delete synced records without understanding impact
- Set polling interval to 1 minute unless necessary
- Enable sync during bulk imports (disable temporarily)
-
17.0.1.0.0 2026-04-16
- Initial release with full bi-directional sync
- Contact, Opportunity, Task, and Note synchronization
- Smart pagination with Close CRM API cursor support
- Triple-layer duplicate prevention
- User and pipeline mapping functionality
- Configurable cron jobs and manual sync
- Comprehensive error handling and logging
Please log in to comment on this module