Migrate from Bigin by Zoho CRM to Odoo CRM

Bigin Contacts map to Odoo CRM Contact records linked to a Partner record. In Bigin, Contacts and Companies are separate modules with a linking relationship; in Odoo, the Partner model serves both individual and organizational records, with Contact records nested under a Partner. We split Bigin's Contact-Company relationship by creating an Organization Partner for each Bigin Company and a Contact-type Partner for each Bigin Contact, then linking the Contact Partner to the Organization Partner via the parent_id relationship. Email, phone, address, and owner fields transfer directly; the Bigin Contact Salutation and Lifecycle Stage properties migrate as custom fields on the Partner record.

Bigin Companies map to Odoo Partner records with Type set to Company. The Company Name becomes the Partner name, website URL maps to website, and any address fields map to partner address fields. In Odoo, company records can also carry accounting and fiscal data through the Accounting module integration. We preserve any Bigin Company-to-Contact linkage by resolving the parent Partner after the Company Partner insert.

Bigin Deals map directly to Odoo CRM Opportunity records. The Deal Name becomes the Opportunity name, Deal Amount maps to Expected Revenue, Close Date maps to Deadline, and the Bigin Pipeline plus Stage combination maps to a corresponding Odoo CRM Stage within a Team. We pre-create Odoo CRM Teams and Stages matching the source pipeline names before migration so that Deal stage history is preserved by setting Stage history if available or mapping directly on insert.

Each Bigin Pipeline becomes an Odoo CRM Team (crm.team), and each Stage within the pipeline becomes a Stage within that team's sequence. Bigin's sub-pipelines map to additional Stage groups within the same Team. We configure Stage probability percentages in Odoo to match the percentages stored in Bigin. Teams on the Express plan (3 pipelines) or Premier plan (unlimited pipelines) require Stage and Team pre-creation in Odoo before Deal import begins.

Bigin Products map directly to Odoo Product records. Product Name, Unit Price, Tax, and Description fields transfer to Odoo Product Template. Product images stored as attachments in Bigin migrate as Odoo product images linked to the Product Template. Any custom product fields created via the Developer Console use the <namespace>__<label> naming convention and require pre-creation of matching custom fields in Odoo before the product import.

Bigin Tasks map to Odoo Project Task records (or CRM Activity records depending on Odoo configuration). Task Subject maps to name, Description maps to Description, Due Date maps to Deadline, and the owner assignment maps to user_id via email resolution. Task status (Open, Overdue, Completed) maps directly to Odoo Stage values. Tasks linked to a specific Deal in Bigin resolve to the migrated Opportunity record in Odoo via the What_id reference.

Bigin Events map to Odoo Calendar Event records. Start and End datetime, location, and description transfer directly. Recurring events in Bigin are exported individually and squashed in Bigin's Bulk Read output; we handle the recurrence expansion in the transformation layer and create separate Odoo Event records for each occurrence. Event attendees linked to Bigin Contacts or Companies resolve to the migrated Odoo Partner records.

Bigin Call records map to Odoo CRM Call activity records. Call Subject, Duration, Outcome, and Start Time transfer to Odoo's CRM phone call fields. Call recordings stored as Bigin attachments migrate as ir.attachment records linked to the parent Call activity. Calls linked to Contacts, Companies, or Deals resolve to the migrated Odoo Partner or Opportunity record.

Bigin Notes map to Odoo Notes (mail.message) attached to the relevant Partner or Opportunity record. Notes are excluded from Bigin's Bulk Read API and require individual record API calls, which consume credits at a higher rate. We flag note volume during scoping and budget credit consumption accordingly. Note body content migrates as plain text to Odoo's mail.message model.

Bigin Attachments stored against Contacts, Companies, Deals, or other modules map to Odoo ir.attachment records. Like Notes, Attachments are excluded from Bigin's Bulk Read API and require individual API requests per file. We migrate attachments via individual API calls and flag any file size or credit budget issues during scoping. File links resolve to the migrated parent record by cross-referencing the record ID from the Bigin export.

Bigin custom fields created via the Developer Console use the <topping_namespace>__<field_label> naming convention and are scoped per module. We map each custom field explicitly during scoping, validating the field type against Odoo's available field types (Char, Integer, Float, Boolean, Date, Datetime, Selection, Many2one, etc.). Odoo custom fields must be pre-created in the destination database before data import begins because Odoo does not support dynamic field creation during import. We pre-create all destination custom fields in a staging environment before production migration.

Bigin Pipeline Owners and record-level owners map to Odoo User records. We resolve Bigin owner records by email match against the Odoo destination User list. Any Bigin owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo users receive record assignments only if the customer's Odoo configuration allows assigning records to inactive users.