Migrate from Brivity to Odoo CRM

Brivity contacts map directly to Odoo res.partner records. When is_company=false the record represents an individual; when is_company=true it represents a brokerage or property company. Email, phone, and address fields translate 1:1. Primary company assignment uses parent_id on res.partner. During migration, we validate email uniqueness and flag duplicates for review. The is_company flag determines whether the contact appears in Odoo's company or contact views, ensuring proper segmentation for marketing and sales workflows.

Brivity company records map to res.partner with is_company=True. Odoo requires parent_id to be empty on company records. Multi-location companies need separate res.partner records linked by parent_id after the initial company record is created. Each location gets its own partner record with parent_id pointing to the main company, allowing you to track interactions and assignments at both the headquarters and branch level. This structure supports accurate reporting by location and maintains clear hierarchies in your partner database.

Brivity deal names, amounts, close dates, and stage names map to crm.lead name, expected_revenue, date_deadline, and stage_id respectively. The crm.lead type field is set to 'opportunity' for all migrated deals. Owner assignment via user_id resolved by email match against Odoo res.users.

Each Brivity pipeline becomes an Odoo crm.team. Brivity stage names within each pipeline create crm.stage records assigned to that team. Stages are ordered using sequence values pulled from Brivity. Teams without pipeline assignment default to the base CRM team in Odoo.

Stage names are mapped value-by-value from Brivity to Odoo crm.stage records. Probability and legend_color values are preserved as stage properties. Stage IDs in Brivity are not reused; new stage IDs are assigned in Odoo and mapped in the migration lookup table.

Brivity custom properties that have no Odoo CRM native equivalent (e.g., transaction_type, showing_notes, mls_number) are created as x_ prefixed fields on crm.lead using Odoo's ir.model.fields API. Field type (char, float, selection, date) is inferred from the Brivity property value type. Selection fields require explicit value_mapping with Brivia pick-list options.

Brivity tasks and showing notes become Odoo mail.activity records linked to crm.lead via res_model='crm.lead' and res_id matching the migrated deal ID. Task state (open/done) maps to activity state and calendar_event_id where applicable. Original timestamps preserved in create_date. This ensures all historical activities appear in the Odoo chatter, giving your team full visibility into the deal's history. Activities sync with Odoo's calendar module, allowing users to see scheduled tasks alongside their pipeline view.

Brivity leads that have not been converted to deals migrate as Odoo crm.lead records with type='lead' rather than 'opportunity'. These land in the Leads pipeline view in Odoo and can be converted to opportunities manually after migration using Odoo's native Convert to Opportunity action.

Brivity agent and team member records do not create new Odoo users. Owner resolution runs by email address match against existing Odoo res.users. Agents without a matching Odoo email are assigned to a fallback user (configurable) and flagged in the migration report for manual reassignment.

Files attached to Brivity contacts or deals are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. File size limits apply per Odoo configuration. Inline images in Brivity notes are extracted and stored separately.

Brivity notes on contacts and deals migrate to Odoo mail.message records with message_type='comment'. Rich-text formatting is converted to HTML-compatible body content. Notes are displayed in the Odoo chatter thread on the corresponding crm.lead or res.partner record. This preserves all contextual information and makes it searchable within Odoo. The chatter integration allows team members to add follow-up comments directly on migrated notes, maintaining collaboration continuity.

Brivity's automated follow-up sequences, action plans, and marketing tools do not have an Odoo CRM equivalent at the data level. These are configuration artifacts, not records. We export workflow definitions as JSON for your Odoo admin to rebuild using Odoo Studio actions and server actions after migration.

Brivity tracks agent-level metrics like showing_count, conversion_rate, and days_on_market as deal properties. These migrate to custom x_ fields on crm.lead so reporting in Odoo Spreadsheet or custom views preserves the performance context from Brivity. Custom fields allow you to build agent performance dashboards, track individual productivity, and maintain historical data for comparison. You can create pivot tables and charts in Odoo Spreadsheet to analyze these metrics across your pipeline.