Migrate from Rezora to Odoo CRM

Rezora agents map to Odoo res.users. Owner assignment on contacts and leads uses email matching against res.users. Teams of agents map to crm.team records. If Rezora uses team-level templates, those migrate as group-assigned content in Odoo. Each agent's login credentials are preserved in res.users, and their timezone and locale settings are transferred to ensure consistent activity scheduling.

Rezora contacts migrate as res.partner records with partner_type='contact'. Primary company link uses parent_id to the corresponding res.partner (company). Rezora's contact-specific drip enrollment status is preserved as a custom field for reference in Odoo's email marketing module. All standard address fields are mapped to Odoo's street, city, state_id, zip, and country_id, preserving the original formatting and geocoding data.

Rezora companies map to res.partner records with partner_type='company'. Company properties (office address, website, agent count) become custom fields on the company partner. Rezora's N:1 contact-to-company relationships use parent_id on the contact partner record. Additional metadata such as industry classification and primary contact email are stored as custom fields to maintain full context during sales activities.

Rezora leads convert directly to crm.lead records. Lead source, medium, and campaign attribution from Rezora map to Odoo's source_id, medium_id, and campaign_id fields. Lead priority and pipeline stage from Rezora require value-mapping to Odoo crm.stage names. All custom lead attributes, such as referral code and rating, are migrated as custom fields on crm.lead for reporting continuity.

Rezora deals migrate as crm.lead records with type='opportunity'. Property listing links from Rezora deals become custom fields on the Odoo crm.lead. Deal value and commission fields map to Odoo's planned_revenue and custom decimal fields. Associated attachments such as listing flyers and contracts are exported as ir.attachment records linked to each crm.lead for convenient reference.

Odoo has no native drip-automation model. Rezora drip campaigns are exported as a reference CSV (campaign name, sequence steps, enrollment rules, delay intervals) for manual rebuild in Odoo's email marketing module. The CSV is delivered alongside the migration as a rebuild guide.

Rezora email campaigns and their sent/opens/clicks history migrate to Odoo mail.mass_mailing records. Campaign membership (which contact received which campaign) is preserved as mail.activity entries on the res.partner. Actual email body content is exported as HTML files for re-upload. All associated metadata such as subject line, send timestamp, and delivery status are also transferred to Odoo's mail.mass_mailing record for full auditability.

Rezora branded email templates are exported as HTML files with placeholder variable mapping. Odoo mail.template records are created manually using the exported HTML. Contact property placeholders are translated to Odoo's ${object.field} syntax during the template rebuild step. Image assets embedded in templates are downloaded separately and re-uploaded as ir.attachment records, maintaining visual consistency across the rebuilt templates.

Rezora social media posts (scheduled posts, engagement metrics) have no Odoo CRM equivalent. Post text and media are exported as a content archive for reference. If Odoo Social app is installed, posts can be recreated manually using the exported content.

Rezora logged calls, emails, and meetings migrate as mail.message records attached to the res.partner. Call duration and outcome from Rezora are stored in custom fields on the mail.message. Activity timestamps and agent owners are preserved for reporting continuity. All attachments linked to activities are exported as ir.attachment records, preserving the full communication context within Odoo.

Rezora custom contact properties (beyond standard firstname, email, phone) are created as custom fields on res.partner via Odoo Studio or Settings > Technical > Models. Field type is mapped from Rezora's type (text, number, picklist) to the closest Odoo field type.

Rezora deal-level property data (listing address, MLS number, property type, price) is captured as custom fields on crm.lead since Odoo CRM has no native real estate listing model. This is the most common Rezora-to-Odoo custom field requirement. These fields enable your team to track listing status, showings, and offers directly within the opportunity pipeline, providing full visibility into the real estate transaction lifecycle.

Rezora offices and teams map to crm.team records in Odoo. If Rezora tracks branding per office, the brand_id becomes a custom field on crm.team. Multiple Rezora companies under one brokerage map to res.company records in Odoo's multi-company setup. This mapping ensures that team-specific sales targets and reporting dashboards align with your organizational structure in Odoo.

Rezora file attachments on contacts, companies, and deals are re-uploaded as ir.attachment records linked to the corresponding Odoo model (res.partner, crm.lead). File size limits apply; large attachments are zipped before upload to stay within Odoo's attachment size constraints. Metadata such as file name, creation date, and uploader ID are preserved to maintain audit trails for compliance.