Migrate from Referrizer to Odoo CRM

Referrizer Contacts map directly to Odoo res.partner records. The contact name, phone, email, and address fields translate to Odoo's name, phone, email, and street/city/country fields. Custom field properties on the Referrizer contact enumerate during GET /contacts and get created as custom fields on res.partner before migration. Labels from Referrizer become Odoo Tags attached via partner_category. We scope extraction by location_id to prevent cross-location contamination and validate contact counts per location against the Referrizer dashboard before transformation.

Referrizer Pipeline stages map to Odoo crm.lead stages within a single Sales Team. Each Referrizer stage name becomes an Odoo stage with a sequence number and probability percentage matching the Referrizer stage order. Odoo stages are managed via Settings > CRM > Stages and can include lost/won flags. If Referrizer has multiple pipelines (multi-stage configurations), we create separate CRM Teams in Odoo and assign stages per team.

Referrizer leads in the pipeline map to Odoo crm.lead records with type='lead'. The lead status, source, and assigned owner transfer to Odoo's crm_lead fields. Odoo's crm.lead model supports a stage_id pointing to a stage in the pipeline. We resolve Referrizer's hubspot_owner_id or owner email to an Odoo res.users record by email match before inserting the lead.

Referrizer Campaigns (Regular and Automated modes) map to Odoo crm.lead records tagged with the campaign name, or to a custom campaign model if the customer has installed the Odoo CRM Campaigns module. Campaign type and status migrate as custom fields. Contact associations within the campaign transfer as tag assignments on the Partner record. Automated campaign reentry rules and trigger intervals do not migrate; we document the campaign configuration in the automation inventory for the admin to rebuild in Odoo.

Referrizer offer codes and referral link associations map to Odoo as custom Char fields on res.partner (referral_code, offer_code) or as a Product record with a promotional price if the offer drives a product discount. Referral reward structures (point value per referral) migrate as custom fields documenting the reward logic. We do not migrate referral relationship graphs as relational data unless the destination supports a custom referral object, which most Odoo CRM configurations do not.

Referrizer loyalty point balances are stored as numeric contact properties, not a distinct object. We extract these during contact enumeration, separate them from standard contact fields, and create a custom float or integer field loyalty_points on res.partner before migration. The field name is configurable during scoping. Point balance history (transactions) does not migrate as a separate table unless the customer has a custom loyalty module installed in Odoo.

Referrizer review request history (which contacts received requests, when, and to which platform) is stored as activity on the contact record. We export this as a formatted note on the Odoo res.partner with review_request_date and review_platform fields. Automated review request triggers (the automation behind the campaign) do not migrate; we document the review request campaign in the automation inventory for the admin to rebuild using Odoo Email Marketing or a third-party review integration app.

Referrizer contact labels map to Odoo partner_category records attached to res.partner via the category_id many2many field. Label names become category names. Multi-label contacts receive multiple Odoo tags. If the label count is large (over 200 distinct labels), we discuss with the customer whether to consolidate into a smaller tag set or maintain the full label taxonomy as Odoo tags.

Referrizer contact activity feed events (UTM tracking, campaign opens, link clicks) export as Odoo mail.message records linked to the res.partner via model=res.partner and res_id pointing to the partner ID. Call, meeting, and task engagements map to Odoo crm.activity records. Email engagements map to mail.message with email=True. The activity timeline ordering is preserved using the original Referrizer timestamp as the message date. We do not migrate Smart Inbox conversational threads because Referrizer exposes no API endpoint for them.

Referrizer team members export by email and name. We match by email against Odoo res.users. Owners assigned to Contacts, Leads, and Deals resolve to the matched Odoo user ID during import. Any Referrizer owner without a matching Odoo user goes to a reconciliation queue for the admin to provision before record import resumes. Role-based permission structures in Referrizer do not map directly to Odoo's access rights model and are documented separately.

Referrizer multi-location accounts map to Odoo res.company records (if the customer uses Odoo multi-company) or to a custom division field on res.partner if they prefer a single-company structure. We scope extraction by Referrizer location_id during the extract phase and validate that contact counts per location match the Referrizer dashboard totals before loading. Cross-location contact assignment during migration is prevented by enforcing the location filter during all extraction queries.

Referrizer custom fields are contact-level key-value properties enumerated via GET /contacts before migration. We inspect all custom field names and types (string, number, date, checkbox) and pre-create matching Odoo custom fields on res.partner using Odoo Studio or direct XML definition. Odoo requires developer mode to create fields via the UI; we handle the XML-based field creation in the migration schema phase. Fields that have no Odoo equivalent (e.g., complex JSON properties) are stored as Char fields with the JSON stringified.