Migrate from Brokerkit to Odoo CRM

Brokerkit Agent records become res.partner records with type='contact'. Agent-level fields (licensing info, recruiting source, recruiting status) migrate as custom fields on res.partner. The agent's email becomes the res.partner email; a name field is constructed from firstname and lastname if available. Owner assignment resolves by matching the Brokerkit owner email to a res.users record in Odoo.

Each Brokerkit recruiting pipeline maps to a crm.lead record with type='opportunity' in Odoo. The pipeline name becomes the crm.lead name field. The current pipeline stage in Brokerkit maps to stage_id on the Odoo crm.lead, resolving the stage by name within the target crm.team. Pipeline stage probabilities in Brokerkit are not directly importable — we store them as a custom field on crm.lead for reporting reference.

Brokerkit Contact records map 1:1 to res.partner records with type='contact'. Standard fields (name, email, phone, address) pass through directly. A parent company relationship in Brokerkit translates to parent_id on the Odoo res.partner. If the Contact has no company association in Brokerkit, we attach it to a default 'Unassigned' res.partner record flagged as a company stub.

Brokerkit Company records map to res.partner records with type='company'. The company name populates the name field, domain maps to website, industry to industry (as a selection field with value mapping), and employee count to employee_count. Parent-company hierarchies in Brokerkit map to parent_id on the Odoo res.partner — the parent company must be migrated first or circular reference is flagged.

Brokerkit Deal records map to Odoo crm.lead with type='opportunity'. The deal name becomes crm.lead name, amount maps to planned_revenue, close date maps to date_deadline, and stage maps to stage_id via value mapping against the Odoo pipeline's stage definitions. Brokerkit deal owner resolves by email match to Odoo res.users.

Brokerkit follow-up activities and call logs map to Odoo's crm.phonecall model for calls and mail.message for note-type activities. Original timestamps and owners are preserved. Odoo's crm.phonecall requires a name field (constructed from the activity type and related partner) and a duration if available from Brokerkit's log data.

Brokerkit custom properties on Agent records that have no Odoo equivalent become custom fields on res.partner (x_agent_license, x_recruiting_source, etc.). Custom fields must be pre-created in Odoo Settings > Technical > Fields before migration. Field type is inferred from Brokerkit's property type (text, number, date, pick-list).

Brokerkit deal-level custom properties migrate as custom fields on crm.lead (x_deal_commission_type, x_referral_source, etc.). Each custom field requires creation in Odoo before import. For pick-list type properties, we create a selection field and perform value-by-value mapping from Brokerkit values to Odoo selection options.

Brokerkit pipeline stage names map to Odoo stage records. Stage names that have no exact Odoo match get created as new stages within the target crm.team. We preserve Brokerkit stage order as sequence values in Odoo. Stage probability values are stored in a custom float field (x_stage_probability) for reporting continuity since Odoo's stage probability is defined per stage and not directly importable.

File attachments associated with Agent, Contact, or Deal records in Brokerkit are re-uploaded to Odoo's ir.attachment model, linked to the corresponding res.partner or crm.lead record via res_model and res_id. Odoo's attachment storage backend (file system or database) depends on Odoo configuration — we preserve the original file name and content type.