Migrate from Realvolve to Odoo CRM

Realvolve People records map directly to Odoo res.partner records. The name, email, phone, address, and social handle fields migrate as-is. Owner assignments (agents) resolve by email match against Odoo res.users. Unmatched owners receive a fallback assignment to a designated placeholder user or partner record to ensure every record lands with a resolved owner in Odoo.

Realvolve Companies migrate to res.partner records with company_type set to 'company'. Parent-company hierarchies map directly to Odoo's parent_id field on res.partner, preserving organizational structures. Multi-company contacts with N:N associations collapse to a primary company partner with remaining associations preserved as Account Contact Relations.

Realvolve Property records become Odoo crm.lead opportunities. Listing status, MLS number, property type, and address fields migrate to custom Char and Selection fields on crm.lead. Listing agent and selling agent roles migrate as custom Many2one fields pointing to res.partner, preserving the agent-to-property relationship from Realvolve.

Realvolve Transaction records hold the deal record and its party role associations. The transaction header maps to crm.lead fields including deal amount, current stage, and expected close date. For transactions that reach closed-won status, we create sale.order records linked back to the corresponding opportunity via the order reference field on crm.lead.

Realvolve transaction parties carry role labels such as Listing Agent, Selling Agent, and Title Officer. These roles map to a combination of sale.order line notes and a custom Many2many field on crm.lead that stores all deal participants. Odoo has no native role-label object for opportunity participants, so custom fields capture each party's function in the transaction.

Active Realvolve workflow states including Current Workflow Step, Next Due Date, and Status migrate as custom fields on crm.lead. Each Realvolve workflow stage maps to a corresponding Odoo pipeline stage in the crm.lead Kanban view, preserving the transactional timeline while adapting to Odoo's stage-based pipeline representation.

Realvolve custom fields on People records, such as License Number, Preferred Neighborhood, or Referral Source, require Odoo custom field creation via Odoo Studio or Python module. We deliver a comprehensive field creation plan before migration specifying each custom field's Odoo type, XML or Python implementation code, and validation rules so the Odoo schema is prepared for data landing.

Realvolve property custom fields like HOA Fee, Lot Size, and Year Built migrate as custom fields on crm.lead. Realvolve's date and currency fields map to Odoo's date and monetary field types with proper decimal precision and currency configuration preserved during migration.

Realvolve file attachments migrate to Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via the res_model and res_id fields. Files are re-uploaded to Odoo's filestore directory structure. Inline images embedded in notes or description fields are extracted and rehosted as standalone attachment records with proper mimetype classification.

Realvolve Premium Workflows (Transaction Coordination, Listing Management, Sphere of Influence, Past Client Follow-up, Lead Conversion) are automation packages that have no direct Odoo CRM equivalent. We export the workflow definitions as structured JSON files containing step definitions, conditional branches, action types, and pause conditions for your Odoo developer to rebuild using Studio or server actions.

Realvolve logged calls, emails, and meetings migrate as mail.message records on the corresponding res.partner or crm.lead. Odoo's crm.phone.call model handles logged calls with duration and outcome fields captured. Original timestamps and owner assignments are preserved from Realvolve's create_date and owner_id fields to maintain full activity history integrity.

Realvolve email templates are marketing content structures that do not migrate directly to Odoo. We export template definitions as HTML files with merge field references preserved for your Odoo marketing team to recreate using Odoo's email marketing module. The export includes variable placeholders and conditional content blocks for accurate template recreation.