Migrate from VaultRE to Odoo CRM

VaultRE contacts map to Odoo res.partner records. Since VaultRE allows a single contact to carry multiple roles (buyer, seller, tenant, landlord), we split each role into a separate partner_category tag on the res.partner record. Original VaultRE contact ID preserved as external_id for delta-run de-duplication.

Each VaultRE role flag on a contact generates a corresponding tag in res.partner.category. Role-specific metadata (e.g., tenant lease expiry date) migrates as custom Char fields on the partner record. Your Odoo admin selects which roles map to tags versus custom fields during the mapping review.

VaultRE property listings translate to Odoo product.template records if the agency uses Inventory to manage rental stock, or to a custom crm.property model if only CRM visibility is needed. Property status (For Sale, For Rent, Sold, Leased) maps to product.active or a custom status_char field depending on Odoo edition.

VaultRE's agent-to-property assignment maps to product.template's seller_ids, pointing to the agent's res.partner record. If the agent is also a contact in the system, FlitStack resolves by email match to prevent duplicate partner creation during migration. The seller_ids relationship ensures that property listings retain their assigned agent information in Odoo. During the migration process, any potential duplicate contacts are flagged for review, and email-based matching prevents redundant records from being created in the Odoo database.

VaultRE trust-accounting records (receipts, disbursements, reconciliations) route to Odoo Accounting as account.move entries rather than CRM records. This requires the Accounting app to be installed in the Odoo database. We map VaultRE ledger account codes to Odoo chart of accounts codes using your account mapping spreadsheet.

VaultRE open-home check-ins with attendee names and feedback combine into Odoo crm.lead notes and calendar.event records. Each check-in generates a lead note entry and a calendar event if a follow-up task was recorded. Original timestamps preserved as write_date on the target record.

VaultRE leads and enquiries map directly to Odoo crm.lead records. Lead source (website, referral, direct) migrates to crm.lead.source. Pipeline stage names from VaultRE map to crm.stage stage_id values via value mapping. Unqualified leads remain as crm.lead until converted to opportunity.

VaultRE logged calls, emails, meetings, and notes migrate to Odoo mail.activity records linked to the parent res.partner or crm.lead via res_id and model fields. Original activity timestamps and user assignments preserved. VaultRE note body migrates as mail.message with message_type='notification'. The mail.activity model captures all interaction history, maintaining the original communication context and chronology. Each migrated activity retains its source record reference, ensuring complete traceability in the new Odoo system.

VaultRE field groups and their contained custom fields (Date, Checkbox, Text, Drop-down Selection) translate to Odoo Studio custom fields on res.partner or product.template. Drop-down selections become selection fields with values mapped one-by-one. FlitStack delivers a field-group-to-Studio-field mapping spreadsheet before migration runs.

VaultRE staff records map to Odoo res.users by email match. Unmatched staff are flagged before migration — your team either creates Odoo users first or assigns VaultRE staff records to a fallback Odoo user. User active/inactive status from VaultRE controls res.users.active in Odoo.

VaultRE multi-office structure maps to Odoo res.company records if the Odoo multi-company feature is enabled, or to res.partner.category tags for simpler single-company setups. Each office's default contact and agent pool assign to the corresponding company_id on migrated records. When multi-company mode is activated, each office becomes a distinct Odoo company entity, preserving hierarchical relationships and enabling granular access controls across different organizational branches.

VaultRE's native integrations with Pricefinder and CoreLogic for property data enrichment have no direct Odoo CRM equivalent. These integrations must be replaced with Odoo-compatible third-party apps or custom API connectors — FlitStack documents which VaultRE integrations are active so your Odoo admin can evaluate replacement options.