Migrate from The Real Estate Platform (REP) to Odoo CRM

REP contacts map directly to Odoo res.partner records with company_type set to 'individual'. REP contact ownership by agent resolves to the corresponding Odoo res.users record. REP contact create/update timestamps are preserved as custom fields for audit continuity. This direct mapping ensures that all contact details—including name, address, phone, and email—are transferred intact, while the agent-to-user linkage maintains accountability for each record's history.

REP companies map to Odoo res.partner with company_type = 'company'. REP parent-company hierarchy (if present) maps to Odoo's parent_id field on res.partner. REP company domains and annual revenue map to Odoo website and annual_revenue fields respectively. This ensures that each organization's branding information, financial metrics, and hierarchical relationships are preserved in Odoo, supporting accurate reporting and segmentation across the sales pipeline.

REP leads become Odoo crm.lead records with type = 'lead'. REP stage values map to Odoo crm_case_stage records — stage names and probabilities are re-created in Odoo before migration. REP lead source and campaign attribution map to Odoo's source_id and campaign_id lookups.

REP deals become Odoo crm.lead with type = 'opportunity', linked to the REP contact via partner_id. Deal amount, close date, and stage map to Odoo's expected_revenue, date_closed, and stage_id. REP deal owner resolves to the Odoo res.users record by email match.

REP agents map to Odoo res.users records — each agent becomes a user who can own crm.lead records and log activities. REP office and region assignments map to crm.team membership, with agents added as team members in Odoo after team creation.

REP listings have no native Odoo equivalent. Property address, MLS number, listing price, property type, and transaction subtype migrate as custom fields on crm.lead. These custom fields must be created in Odoo before migration — we deliver a custom-field setup plan based on the REP listing schema audit.

REP white-labels custom fields per customer deployment, meaning every REP instance has a different schema. We audit REP's custom field inventory first, then recreate each as an Odoo custom field on the appropriate model (crm.lead or res.partner) with matching field type selection before migration data is loaded.

REP call, email, and meeting logs attach to crm.lead records as mail.activity entries with activity_type_id mapped (call, email, meeting). Activity subject, date, duration, and owner are preserved. REP notes migrate as Odoo mail.message records on the parent crm.lead. This migration maintains the full activity timeline, enabling sales reps to review past interactions without data loss and supporting Odoo's activity dashboards and follow-up reminders.

REP offices and regions map to Odoo crm.team records. REP agents are assigned as members of the corresponding crm.team. For nested REP office hierarchies, Odoo's parent_team_id field (available in Odoo 16+) is used where the version supports it. This structure preserves territorial reporting and helps maintain clear visibility of which agents belong to which office, facilitating manager oversight and territory-based forecasting.

REP file attachments on contacts, companies, and deals re-upload to Odoo's ir.attachment table linked to the migrated record. File name and original create date are preserved. Large files or files exceeding Odoo's attachment size limits are flagged before migration for manual handling.

REP automation rules and drip sequences cannot be imported into Odoo — REP uses trigger-and-action automation logic that has no Odoo counterpart. We export all REP automation definitions as a JSON file before migration. Odoo administrators use this file to rebuild equivalent automations using Odoo Action buttons and server actions post-migration.