Migrate from Rubi CRM to Odoo CRM

Rubi CRM Contacts map directly to Odoo res.partner records with partner_type set to contact. Standard fields (name, email, phone, street, city, country) migrate 1:1. Custom contact properties discovered during scoping are created as ir.model.fields on res.partner before import. The Contact-Company relationship in Rubi CRM maps to the parent_id reference on res.partner, which Odoo uses to build the company-contact hierarchy.

Rubi CRM Company records map to Odoo res.partner with is_company=True. Company name becomes the partner name, and associated Contacts are linked via parent_id to the newly created company partner. We run company deduplication by name and domain before import to prevent duplicate Odoo partners. Company-level custom fields migrate as custom fields on the is_company partner record.

Rubi CRM Member records are distinct from Contacts and store membership-specific identifiers and status. We map Member ID to a custom field rubi_member_id__c on res.partner, and membership status (Active, Expired, Cancelled) to a selection field rubi_membership_status__c. The original Member record is matched to an existing Contact by email where a correspondence exists, or created as a new res.partner if no Contact link is found.

Membership records in Rubi CRM track individual subscriptions against Member profiles, including start dates, end dates, and tier names. We map start_date to rubi_membership_start__c, end_date to rubi_membership_end__c, and tier_name to both a selection field rubi_membership_tier__c and a partner_tag in Odoo's tag system (res.partner.category). The tag system allows Odoo to filter members by tier in list views and kanban without requiring a custom object. Rubi CRM does not export full subscription history in a single pass; multi-period subscription records require a separate export run from the membership module.

Rubi CRM Events are objects with bookings tied to Contacts or Members. We map event name, start_date, end_date, and location to Odoo event.event. Each Rubi CRM booking (Attendee) becomes an event.registration record linked to the Odoo event.event via event_id and to the corresponding res.partner via partner_id. Booking status (Confirmed, Waitlist, Cancelled) maps to Odoo's registration state field. Multi-session training courses are mapped to Odoo event.event with is recurring=True and session lines.

Rubi CRM's Kanban pipeline is a view with stage names stored as user-defined custom field values against deal records rather than a native pipeline object. We extract the distinct stage values from Rubi CRM deal records during the scoping call and deliver a stage-configuration worksheet mapping each Rubi CRM stage name to an Odoo CRM stage in the default sales team pipeline. Stage probability percentages are documented for entry into Odoo's stage configuration. This is a configuration handoff, not a data migration; the customer's Odoo admin applies the stage names post-migration.

Rubi CRM Deals map to Odoo crm.lead records with type=opportunity. The deal name becomes the lead name, amount maps to planned_revenue, and expected_close_date maps to date_deadline. Stage name from the custom field maps to stage_id via the stage-configuration worksheet. Partner_id is resolved via Contact-Company matching. We create crm.lead records before linking them to event registrations if any Deals are tied to event bookings.

Email interactions logged via Rubi CRM's Outlook plugin are stored as Activities linked to Contacts. We export activity timestamps, subject, and body text to Odoo mail.message records linked to the corresponding res.partner via model=res.partner and res_id. Thread-level threading from the original email is not preserved; messages land as individual entries rather than a threaded conversation view. This is a known limitation of the Rubi CRM export format.

Rubi CRM Tasks map to Odoo project.task if the customer uses the Odoo Project module, or to mail.activity if tasks are scoped to CRM-only. Task owner resolves via email match to Odoo res.users. Due date and status map directly. We confirm the target model during scoping based on whether the customer intends to use Odoo Project alongside CRM or keep task management within the CRM module.

Rubi CRM allows custom fields per record type but does not expose a schema endpoint. We discover custom field names and types during the export scoping phase by inspecting a sample export. We create matching fields in Odoo via ir.model.fields before any data import begins. Field types are mapped: text to char, number to float or integer, date to date, checkbox to boolean, dropdown to selection. Custom fields on Rubi CRM custom objects are handled as additional custom fields on the mapped Odoo object.

Rubi CRM's Report Builder exports data snapshots and its Audit log tracks user actions. Neither contains transactional CRM records. We do not migrate these objects as they are point-in-time exports not suitable as migration sources. We recommend exporting any reports the customer relies on as CSV from Rubi CRM before decommissioning and rebuilding them as Odoo custom reports or Excel imports post-migration.

Rubi CRM Saved Reports are flat snapshot exports and do not contain relational data suitable for Odoo import. We audit the customer's saved reports during scoping and flag those that contain operational data (pipeline summaries, membership renewal lists) for recreation as Odoo custom searches, saved filters, or Excel exports from the migrated data. Odoo Reporting (Flectra) or a BI tool like Metabase can rebuild historical analytics if the customer requires it.