Migrate from Rechat to Odoo CRM

Rechat contacts map to Odoo res.partner records with partner_type set to 'contact'. The email, phone, name, address, and jobtitle fields translate directly. Rechat owner_id resolves by email match to Odoo user records before import — unmatched owners flag for manual assignment.

Rechat companies map to Odoo res.partner with company_type set to 'company'. The domain, industry, employee count, and revenue fields translate as direct fields. Parent-company relationships in Rechat map to res.partner.parent_id in Odoo — circular references are flagged and resolved during validation before any records commit to the target database.

Rechat deals map to Odoo crm.lead as opportunities. The deal name becomes the crm.lead name field, amount maps to crm.lead.expected_revenue, and close date maps to crm.lead.date_deadline. Pipeline assignment and stage mapping are handled through value mapping tables keyed on pipeline ID.

Rechat's listing object (property address, MLS number, listing agent ID, property type) has no native Odoo equivalent. We create custom_char fields on crm.lead to store the property address, MLS number, and listing agent reference. The raw listing payload is preserved as a JSON custom field for reference.

Rechat pipelines are named collections of stages. Each pipeline maps to a distinct set of Odoo crm_stage records grouped by sales team. The stage names, sequence order, and probability percentages are recreated in Odoo's pipeline configuration before migration runs. We deliver a stage-setup checklist and coordinate with your Odoo admin to pre-create all required stage records.

Stage names are mapped value-by-value from Rechat stage labels (New Lead, Showing Scheduled, Offer Made, Under Contract, Closed Won) to Odoo stage names (New, Qualified, Proposition, Negotiation, Won). Each stage's probability and fold-to-cancelled flag are reapplied from the Odoo stage configuration.

Rechat call logs, emails, and meeting records map to Odoo mail.activity entries with activity_type_id set to 'call', 'email', or 'meeting'. Original timestamps, owner assignments, and subject lines are preserved. Odoo requires activity_type records to exist before migration — we create them from the standard type library.

Rechat notes with HTML content are sanitized to strip unsafe tags while preserving links and basic formatting. The cleaned content is stored as a mail.message record with subtype 'note' on the crm.lead. Inline images are downloaded and re-hosted as Odoo attachments.

Rechat tags applied to contacts and deals map to Odoo crm.tag records via ir.model.data cross-references. Tag names and color values are recreated as crm.tag entries in Odoo. The many-to-many relationship between records and tags is established through crm.lead.tag_ids during the import phase, ensuring all tagged contacts and deals retain their categorization after migration completes.

Rechat flows, touch reminders, and Lucy AI assistant automations do not transfer. We export the full flow definitions (trigger events, conditions, and actions) as JSON reference documents so your Odoo admin can rebuild them using Odoo Studio server actions and scheduled actions on the CRM module.

Rechat email templates and newsletter content are exported as HTML files and contact-segment exports. Odoo's email marketing uses the Email Marketing app — templates must be recreated there. We provide the HTML source and merge-field mappings as a rebuild guide.

Rechat reports and pipeline analytics do not transfer. The underlying data (deals, amounts, stages, activity timestamps) migrates completely, so reports can be rebuilt in Odoo's native reporting tool or BI integrations. We export Rechat report definitions as reference screenshots and field lists.

Rechat custom properties per contact, company, and deal map to Odoo custom fields. For res.partner we use custom_char, custom_text, or custom_selection depending on the source data type. For crm.lead we create equivalent fields. All custom field names and pick-list values are preserved in the migration plan.

Rechat's internal record ID is stored as a custom_char field on each migrated Odoo record (Source_Rechat_ID__c on res.partner and crm.lead). This field enables delta-run de-duplication to prevent duplicate records during incremental syncs, precise rollback targeting to revert specific records if needed, and maintains a cross-reference audit trail between the two systems for reconciliation and troubleshooting.