Migrate from Rainbow CRM to Odoo CRM

Rainbow CRM Contacts with no associated Company export as individual records. These map to Odoo res.partner records with partner_type set to contact. Rainbow CRM Contacts with an associated Company require partner_id lookup resolution: we match the Rainbow company_name in the export against Odoo res.partner records by name, creating the company partner first if it does not exist. Email serves as the dedupe key across all partner imports.

Rainbow CRM Companies export as flat records and map to Odoo res.partner records with is_company = True. We create these first, before any Contact import, to satisfy the partner_id self-referential lookup that Odoo's Contact model requires. Company name becomes res.partner name, domain becomes website, and address fields map to the partner's address fields. Company records without an email domain generate no website lookup key.

Rainbow CRM Deals map to Odoo crm.lead records. The mapping is direct for deal name, amount, expected closing date, and responsible owner email. The Rainbow dealstage property does not map directly to an Odoo stage ID and requires a manual stage mapping table (see gotchas). Rainbow CRM's Deal-to-Contact association is denormalized in the export; we reconstruct the contact_id by matching the deal's associated contact email against imported res.partner records.

Each unique Rainbow CRM deal stage value extracted from the export maps to an Odoo crm.lead.stage record. Rainbow stage names do not match Odoo's default stages (New, Qualified, Proposal, Won, Lost), so we create custom stage names in Odoo that match the customer's pipeline language, or remap to nearest Odoo equivalents based on scoping confirmation. Stage probability values transfer where present in the export.

Rainbow CRM Leads export as a separate object and map to Odoo crm.lead records with type = lead (distinguished from type = opportunity for Deals). We flag any Leads sharing an email address with an existing imported Contact at migration time and present a deduplication decision table to the customer before writing those records. The customer chooses whether to merge, keep separate, or prioritize the Lead.

Rainbow CRM Tasks export as flat records with title, description, due date, and status. We map these to Odoo project.task records linked to a default project created during migration. Assignee resolution requires matching the Rainbow task owner's email against Odoo res.users records by email; any unresolved assignees are placed in a reconciliation queue for the customer's admin to provision. task_name maps to name, date_deadline maps to date_deadline, and stage maps to stage_id in the Odoo project.

Rainbow CRM activity history (calls, emails, meetings, notes) exports in a denormalized flat format with a single activity_type field. We parse each row, classify by activity_type, and create Odoo mail.message records for emails and notes linked to the correct res.partner via model and res_id. Meeting records create calendar.event entries with start datetime, duration, and location preserved. Call duration and disposition map to custom message fields in Odoo. We thread activities to the correct contact or deal by matching the associated email against imported res.partner records.

Rainbow CRM exposes a subset of custom fields in its export formats, but not all custom field types are guaranteed to appear (see gotchas). We inspect the export schema during discovery, identify all present custom properties, and pre-create matching custom fields on the appropriate Odoo model (res.partner, crm.lead, project.task) before migration. Fields that do not appear in the export are documented in the scope as non-migratable with a manual export recommendation for each.

Rainbow CRM does not expose file attachments or document records through its documented export format. Any linked files must be handled through direct database access or manual re-upload. We document every ir.attachment record that would be required in Odoo based on references in the activity export, but we cannot extract the actual binary files from Rainbow CRM's export mechanism. This gap is surfaced in the discovery report and requires a separate engagement or customer-led extraction if file preservation is required.

Rainbow CRM Owners referenced on Contact, Company, Deal, and Task records map to Odoo res.users by email match. We resolve owner_id on each migrated record by querying the Odoo destination database for a res.users record with a matching email. Any Owner in Rainbow CRM without a matching Odoo res.users record is placed in a reconciliation queue. The customer provisions missing Odoo users before record import resumes to avoid null owner_id references.

Rainbow CRM Lead status values (Active, Qualified, Converted, Closed) do not have direct Odoo equivalents. We map them to crm.lead.medium_id as a custom selection matching the customer's lead lifecycle. If the customer uses a custom lead scoring model in Rainbow CRM, we carry the score value into a custom float field on crm.lead in Odoo.

Rainbow CRM exports contact names as a single full_name field or as separate first_name and last_name fields depending on the export configuration. We parse both formats and populate res.partner.name in Odoo (which stores a single display name field) and optionally create res.partner.firstname and res.partner.lastname via the Odoo base_name_modules partner_firstname extension if installed, setting both fields for full name reconstruction.