Migrate from Right On Interactive to Odoo CRM

Right On Interactive Contacts with lifecycle stages below sales-qualified threshold (Prospect, MQL, Subscriber) map to Odoo crm.lead. Lifecycle stages above sales-qualified (SQL, Customer, Advocate) map to res.partner contact records attached to a parent Company (res.partner in company mode). We capture the customer's full lifecycle stage label set during discovery, build the mapping table, and preserve the original stage label in a custom char field roi_lifecycle_stage__c on both crm.lead and res.partner for historical audit. The split rule is parameterized before migration so the same script can be re-run for delta imports.

Right On Interactive Company records map to Odoo res.partner records with is_company=True. The company domain from Right On Interactive becomes the Website field and serves as the deduplication key during import. Parent-child relationships between companies (if configured in Right On Interactive) map to the parent_id field on res.partner. All contacts imported later reference their parent company via partner_id to satisfy Odoo's partner-company linking model.

Right On Interactive's behavioral, demographic, and firmographic sub-scores each become a separate custom float field on res.partner and crm.lead: roi_score_behavioral__c, roi_score_demographic__c, and roi_score_firmographic__c. The aggregate 3D score maps to a fourth custom field roi_score_total__c. We create these fields via Odoo Studio or direct field creation in developer mode before migration begins. Odoo has no native multi-dimensional scoring model, so the three-field structure preserves analytical value and enables the customer's team to use these values in Odoo computed fields, domain filters, and group-by views.

Right On Interactive lifecycle stage labels are account-configured custom properties, not a fixed schema. We extract the complete label set during discovery (for example: Prospect, Marketing Qualified, Sales Accepted, Customer, Evangelist), create a custom selection field roi_lifecycle_stage__c with those exact values on both crm.lead and res.partner, and map each contact's stage value at import time. If the customer uses different stage names per sub-account or brand, we create a mapping table per label group and apply it during the transform phase.

Right On Interactive engagement events (email opens, link clicks, form submissions, social interactions) attach as Odoo crm.activity records linked to the parent res.partner via res_id and model='res.partner'. Each activity record carries activity_type_id, description, create_date from the original timestamp, and a custom body field holding the engagement detail (clicked URL, form name, social platform). Email response events map to crm.lead model. Activity type categorization preserves the source event type for Odoo group-by filtering. This mapping handles historical records; new engagement tracking after cutover requires Odoo's native email tracking or a third-party integration.

Right On Interactive Lead records (synced from CRM integrations) map directly to Odoo crm.lead. The lead_source attribution from Right On Interactive maps to Odoo's source_id (utm.source). Initial scoring from Right On Interactive at time of sync is preserved in a custom field roi_import_score__c on crm.lead. Lead status transitions that contributed to lifecycle stage movement are documented as activity notes for the customer's admin to review during Odoo workflow configuration.

Right On Interactive Opportunity data synced from CRM integrations maps to Odoo crm.lead records where the type='opportunity'. The pipeline stage from Right On Interactive maps to Odoo's stage_id within the relevant team pipeline. Deal value maps to Odoo's expected_revenue field. The linked contact and company resolve to res.partner records via the partner_id and partner_name fields at migration time. Odoo's kanban pipeline view renders the opportunity stages automatically from the stage_id assignment.

Right On Interactive Campaign records (program assets, budgets, multi-channel assignments) map to Odoo utm.campaign for marketing attribution tracking. Campaign metadata (budget, channel assignment) migrates to custom fields on utm.campaign: roi_campaign_budget__c and roi_campaign_channel__c. Active campaign execution state (sending, paused, completed) is not transferred; the customer reactivates campaigns in Odoo using the campaign record as the UTM attribution source. The utm.campaign model enables Odoo to attribute new Leads and Opportunities to the migrated campaign source.

Right On Interactive event and webinar registrations map to Odoo event.registration records linked to the corresponding event.event. Invitation status (Registered, Attended, No-Show) and follow-up sequence assignments migrate as registration state and a custom field roi_followup_sequence__c. If the customer's Odoo instance does not include the Event module, registrations migrate as crm.activity records attached to the res.partner with a custom selection field roi_registration_type__c set to 'webinar' or 'event'.

Right On Interactive social listening data including mention counts and sentiment scores migrate as custom integer fields on res.partner: roi_social_mentions__c and roi_sentiment_score__c. Raw social stream data requires separate export handling and does not transfer as structured Odoo records; we document the export format and recommend a social listening integration (native Odoo social apps or a third-party connector) for ongoing stream data post-migration.

Right On Interactive Owners map to Odoo res.users by email match. We extract every distinct owner referenced on Contact, Company, and Engagement records and match against the destination Odoo instance's res.users table. Owners without a matching res.users account are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive users are migrated as inactive res.users with the appropriate flag to preserve historical assignment without granting login access.

Right On Interactive landing pages and their associated form fields export as HTML assets or template records. We flag any embedded dynamic content fields for manual rebuild in Odoo Website Builder or as web.form models. The landing page URL mapping to UTM sources is documented in the migration playbook so the customer can configure corresponding Odoo website landing pages with the same attribution logic. Active live pages are not transferred as functional pages; they are documented for rebuild.