Migrate from Bushel CRM to Odoo CRM

Bushel contact records map to Odoo res.partner (contact type). We preserve the Bushel contact ID as x_bushel_id for traceability and delta-run de-duplication. If a Bushel contact has no associated company, we create a res.partner without a parent_id in Odoo. Original Bushel create_date is stored as x_original_create_date since Odoo sets CreatedDate at import time.

Bushel customer accounts map to Odoo res.partner with partner_type = 'company'. Bushel's N:N contact-to-account model means multiple Bushel contacts can reference the same account; in Odoo this collapses to one res.partner record with multiple contact children via child_ids relation. We flag any account with more than three linked contacts for manual review before committing.

Bushel assigns an account_manager_name to each customer account. Odoo CRM assigns leads to crm.team and opportunities to res.users via user_id. We map each unique Bushel account manager to a corresponding Odoo user by email match, creating the crm.team record if it does not already exist. Unmatched managers are flagged before migration and assigned to a fallback salesperson.

Bushel activities logged against accounts map to Odoo's crm.activity model (for structured calls and meetings) and mail.message (for notes and general chatter). Activity type, subject, date, and owner are preserved. If Bushel stores activities with HTML or rich-text formatting, we strip to plain text for mail.message body compatibility.

Bushel stores farm_demographics as a structured set of fields (farm size, acreage, storage capacity). Odoo has no native equivalent. We create x_farm_size (float), x_acreage (float), and x_storage_capacity (char) custom fields on res.partner before import. Values transfer directly; unit notation (acres vs. hectares) is preserved as stored in Bushel.

Bushel records the primary_commodity grown or traded per account (e.g., corn, soybeans, wheat). Odoo CRM has no commodity field. We create x_primary_commodity as a selection field on res.partner with the exact pick-list values from Bushel. If Bushel uses a free-text commodity field, we create x_primary_commodity as char and deduplicate values post-import.

Bushel delivery_destinations store the grain elevator or delivery point associated with each account. Odoo has no native delivery destination field. We create x_delivery_destination (char) on res.partner and transfer the destination name. If Bushel stores multiple destinations per account, the primary destination maps to x_delivery_destination and secondary destinations are appended to x_delivery_destination_notes.

Bushel quotes map to Odoo sale.order. Bushel line items (product, quantity, price) map to sale.order.line. Odoo sale.order must be linked to a res.partner (customer) and a crm.team (salesperson). If Bushel quotes are in draft state, they import as sale.order with state = 'draft'. If they are confirmed, state = 'sale'.

Bushel file attachments (contracts, scale tickets, delivery confirmations) are re-uploaded to Odoo's ir.attachment table and linked to the corresponding res.partner or crm.lead record via res_model and res_id. Odoo Community has a 115 MB filestore limit per database; Odoo Enterprise and Custom have higher limits. We flag any attachment exceeding 25 MB before import.

Bushel supports additional custom properties beyond standard fields. Each unique Bushel custom property that does not have a direct Odoo equivalent is created as a custom field (x_ prefix) on the appropriate Odoo model before migration. Custom properties are analyzed for type: text maps to char, numbers to float, dates to date, and pick-lists to selection fields.

Bushel tracks delivery_season (e.g., Fall 2024, Spring 2025) per account. Odoo has no native delivery season field. We create x_delivery_season (char) on res.partner. If Bushel stores season as a date range (start_date, end_date), we map to x_delivery_season_start and x_delivery_season_end as date fields.

Bushel prospects without an established customer account map to Odoo crm.lead. All Bushel contact fields, account manager assignment, and custom properties transfer to crm.lead fields with the same x_ prefix convention. A crm.lead in Odoo can later be converted to a res.partner via the Convert to Opportunity action, which creates the partner record and links the opportunity.