Migrate from Rizer to Odoo CRM

Rizer Contact maps to Odoo CRM Lead. Standard fields (name, email, phone, address) migrate directly. Rizer's lifecycle_stage property migrates as a custom selection field on the Lead since Odoo does not have a native lifecycle stage concept. Contact source (referral, organic, paid) migrates to a custom char field lead_source__c. We infer field data types from raw values before write because the Referrizer API does not enforce type constraints on custom field read.

Rizer Company maps to Odoo res.partner with is_company=True. The company_name maps to the partner name field, industry and domain data map to custom char fields, and website is preserved. Odoo uses a unified partner model for both companies and individuals, unlike CRMs that maintain a separate Account object. Company records are created before Lead import so that the parent_id lookup can be resolved at Lead insert time.

Rize Clients map to Odoo res.partner records, mirroring the Company mapping. If the customer uses both Rizer Social (marketing) and Rize (time-tracking), we run two separate export passes against rizersocial.io and rize.io respectively, then consolidate into the same Odoo partner records using email as the dedupe key. Client billing information that has no Odoo CRM equivalent migrates as custom fields on the partner record.

Rize Projects do not have a direct Odoo CRM equivalent. If Odoo Project app is available in the customer's Odoo instance, Projects map to project.project with the Rize Client as the partner_id. If only CRM is available, Projects map to CRM Lead records with a custom project_name__c field and a tag identifying them as converted projects rather than sales leads. We document the chosen strategy during scoping.

Rize Tasks nested under Projects map to project.task if Odoo Project is installed, or to CRM Lead activities (mail.activity) if only the CRM app is available. Subtask indicators (a boolean or count field in Rizer) expand into discrete activity records with a parent reference. We flatten the hierarchy during migration and tag each record with its source project context.

Rizer Team Members map to Odoo res.users records. We match by email address. Any Rizer Team Member without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before Lead and Opportunity import resumes. Role assignments (admin, manager, member) map to Odoo access rights groups: system access maps to Settings > Users, sales access maps to Sales > User, and manager access maps to Sales > Manager.

Rizer's referral tracking sources, attribution windows, and UTM parameters are stored on Contact records with no native Odoo equivalent. We create custom fields on the CRM Lead — referral_source__c (char), referral_campaign__c (char), attribution_window__c (date range stored as two date fields), and utm_medium__c / utm_campaign__c (char) — to preserve this data. Attribution history spanning multiple sources is stored as a text field with pipe-delimited values. This data is preserved for future reporting once the customer rebuilds attribution logic in Odoo.

Rizer Tags are flat string lists applied to Contacts. Odoo CRM uses crm.tag records attached via a many2many relation. We normalize tag values at migration time — removing duplicates, standardizing casing — and create crm.tag records on demand during import. Tags used for contact classification map directly; tags used for workflow routing do not migrate (Workflow rebuild is out of scope) but are preserved as crm.tag records for the admin to reassign post-migration.

Rizer custom fields on Contact map to custom fields on the CRM Lead created via Odoo Studio or directly in the data model. We inspect the raw field values to infer the correct Odoo field type — date strings become date fields, numeric strings become float or integer fields, delimited multi-select strings become char fields with the delimiter noted for the admin to convert to tags. Date fields stored as ambiguous strings are flagged for manual verification before write. This type-inference step is critical because the Referrizer API returns all values as strings without type metadata.

Rizer Workflows are property-triggered email and SMS sequences with branching logic, delay rules, and tag triggers attached to Contact lifecycle stages. Odoo CRM uses stage-based automated actions and Odoo Studio rules, which are fundamentally different trigger models. We do not migrate Workflows as code. We deliver a written inventory of every active Rizer Workflow with its trigger condition, sequence steps, delays, tag actions, and a recommended Odoo automated action equivalent for the customer's admin to rebuild. The inventory is delivered as a structured document, not as migrated automation objects.

Rizer communication history (emails, calls, meetings, notes) attached to Contact records maps to Odoo mail.message records on the CRM Lead. Call duration and disposition migrate as custom fields on the message. Meeting time and location migrate as mail.activity records of type 'meeting'. The migration complexity depends on what Rizer's API exposes per engagement — we inspect the API response during discovery to determine whether engagements are available as structured records or require parsing from contact activity feeds. Historical engagement data is preserved as notes if structured records are unavailable.

Rizer Task engagements (separate from Rize Project Tasks) attached to Contact records migrate to Odoo mail.activity records on the CRM Lead. Task subject, due date, priority, status, and assignee migrate directly. HubSpot-style task assignment (hubspot_owner_id) resolves via the User email mapping to an Odoo res.users OwnerId equivalent on the activity.

Rizer Social and Rize are separate products with separate login domains (rizersocial.io and rize.io), separate data models, and separate API endpoints. We treat them as two distinct export scopes. The marketing CRM migration covers Contacts, Companies, Workflows, and Engagements. The time-tracking migration covers Clients, Projects, Tasks, and Team Members. Both exports run in parallel passes and consolidate into the same Odoo instance via partner dedupe by email. Customers who only use Rizer Social scope the migration to the CRM data only.