Migrate from Realpage to Odoo CRM

RealPage prospects map directly to Odoo crm.lead. The prospect status field (New, Touring, Application, Lease Signed) determines the initial stage_id in the target pipeline, linking each status to a corresponding crm.stage record. Prospect type (rental, commercial) can be stored as a custom selection field on crm.lead, created via Odoo Studio or the ORM before migration. This mapping preserves core data while allowing property‑specific attributes to be added as custom fields.

RealPage tenant and contact records map to Odoo res.partner. The partner's type (tenant vs. company) maps to Odoo's is_company flag, and RealPage contact category can be stored as a tag in res.partner.category. Email, phone, and address fields transfer directly, while the contact name splits into firstname and lastname on the res.partner record. If a contact appears multiple times, the migration deduplicates by email and keeps the most recent entry.

RealPage property records have no native equivalent in Odoo CRM. Property name, address, and type are preserved as custom char fields on crm.lead. If the migration includes multiple properties per lead, a separate property reference table is created in Odoo and linked by a custom many-to-one field.

RealPage unit numbers and unit types (studio, one-bedroom, etc.) become custom char fields on crm.lead. Unit status (available, leased, under maintenance) maps to a custom selection field. Multiple units per prospect are stored as a comma-separated string or a related sub-record depending on volume.

Lease-specific fields — lease start date, lease end date, monthly rent, security deposit, and lease status (Active, Expired, Pending Renewal) — map to custom date, monetary, and selection fields on crm.lead. The lease status drives Odoo lead stage when mapped alongside the prospect lifecycle.

RealPage business entities associated with prospects map to Odoo res.partner with is_company=True. Company name, domain, industry, and employee count translate directly, while RealPage company category can be stored as a tag in res.partner.category. Multi‑business portfolios in RealPage generate multiple res.partner records, each representing a separate parent entity; subsidiary contacts are linked via parent_id to the top‑level company. The migration deduplicates companies by name and domain to avoid duplicate records.

RealPage logged calls, emails, and meetings map to Odoo crm.activity records linked to the corresponding crm.lead or res.partner. The activity type (call, email, meeting) maps to activity_type_id, and any notes or descriptions are transferred as the activity's note field. Owner resolution follows the same email‑matching logic used for leads, preserving the original timestamp for reporting continuity.

RealPage documents (lease applications, signed leases, correspondence) are exported as a file package and re‑uploaded to Odoo as ir.attachment records linked to the appropriate res.partner or crm.lead. The original filename and document type are stored in the attachment's name and description fields. File size limits from RealPage's export format are respected, and any file that exceeds Odoo's upload limit is flagged in the reconciliation report for manual handling.

RealPage owner IDs are resolved by email match against Odoo res.users. Unmatched owners are flagged in the pre‑migration audit report — teams either invite the user to Odoo first or assign their records to a designated fallback owner before the migration runs.

RealPage prospect source fields (Website, Referral, Walk‑in, etc.) map to Odoo CRM's source_id on crm.lead, which references crm.tracking.source. If RealPage captures UTM parameters or campaign codes, those values are stored in custom fields on the crm.lead for later marketing analysis. Custom RealPage sources that have no Odoo equivalent are added to crm.tracking.source as new records before the migration, ensuring every lead retains its original referral information.

RealPage priority levels (High, Medium, Low) map to Odoo CRM's priority field using a value mapping table, where each RealPage level corresponds to a specific Odoo priority value (e.g., 1 = Low, 3 = Medium, 5 = High). Any custom priority values present in RealPage that do not exist in Odoo's default set are added to the crm.lead priority selection during the schema setup phase. This ensures every migrated lead retains its original urgency classification.

RealPage marketing campaign associations on prospects map to Odoo CRM's crm.tracking.mediium and crm.tracking.campaign records. The campaign name, medium, and any UTM parameters (source, medium, term, content) captured in RealPage are stored in the corresponding tracking fields on each crm.lead, enabling detailed ROI analysis within Odoo. If a campaign does not already exist in Odoo, it is created automatically during the migration using the data from RealPage.