Migrate from REDA to Odoo CRM

REDA custom property objects have no Odoo equivalent — re-modeling is required

REDA stores property, unit, and lease data as Salesforce custom objects (__c) with their own relationship fields. Odoo CRM has no property object — these records must be re-modeled as custom fields on crm.lead or res.partner. The mapping is not 1:1: a single REDA lease record may need to split across a many2one field (property reference), a date field (lease start), and a float field (rent amount). We deliver a custom-field design document before migration so the Odoo schema is ready before any data loads. Failing to pre-create these fields results in data loss on import.

Odoo res.partner merges contacts and companies — SFDC Account-Contact split collapses

Salesforce separates Account (company) and Contact (person) into two objects with a parent-child relationship. Odoo res.partner handles both in one model, using the type field (company vs. contact) and parent_id to establish hierarchy. When we migrate SFDC Contacts, we create a res.partner record with type='contact' and a parent_id pointing to the corresponding company partner. For REDA contacts without an Account in SFDC, we create standalone res.partner records. Odoo Studio or manual configuration is needed to display the split name (first + last) as separate fields in list views.

Odoo XML-RPC API has no native bulk upsert — large imports require batched loops

REDA's Salesforce foundation allows Bulk API 2.0 for large-volume extraction (50,000+ records per batch). Odoo's XML-RPC API processes CREATE and WRITE calls per record sequentially. For migrations exceeding 20,000 records, we implement batched loops with configurable delays to respect Odoo's request limits. The Odoo API is free on Custom plans but rate-limited per instance — we tune batch sizes and retry logic based on the target Odoo instance's response patterns during the sample migration phase. SQL direct-import is available but bypasses Odoo's ORM validation and is not used for CRM records to preserve data integrity.

Odoo crm.lead stage_id uses Odoo-specific stage records — SFDC stage probabilities do not auto-transfer

Salesforce Opportunity stages carry probability and forecast category attributes that drive pipeline forecasting. Odoo crm.stage records hold stage names, sequence order, and onchange logic — but probability must be set manually per stage or via automation. We map SFDC stage names to Odoo stage names via the value-mapping table, but probability percentages and forecast categories are not transferred automatically. Your Odoo administrator should configure expected probabilities on each crm.stage record after migration using the SFDC probability report as a reference.

SFDC Files and ContentDocument attachments require re-upload — original download URLs expire

REDA stores files in Salesforce Files (ContentDocument / ContentVersion). These files may have Salesforce-generated CDN URLs or internal storage references that are not publicly accessible after extraction. We download all ContentDocument records linked to REDA contacts, accounts, and opportunities during the extraction phase, then re-upload them to Odoo's ir.attachment table via the XML-RPC binary upload method. Files exceeding Odoo's attachment size limits (default 100 MB) are flagged for client decision — either split into smaller files or stored externally with a URL custom field reference.