Migrate from Entera to Odoo CRM

Entera contact records (buyers, sellers, agents, and other parties involved in real estate transactions) map directly to Odoo res.partner. Email, phone, address, and company link all have direct equivalents. Odoo's partner is the single contact model for both individuals and organizations, supporting the full spectrum of real estate transaction participants from individual investors to corporate property management firms.

Entera's property entity — the core investment record representing residential or commercial real estate — becomes an Odoo crm.lead with type set to 'opportunity'. Property address components map to Odoo's street, street2, city, state_id, and country_id fields. Investment metrics including After Repair Value (ARV), repair cost, cap rate, and monthly rent become custom fields (x_arv__c, x_repair_cost__c, x_cap_rate__c, x_monthly_rent__c) on the crm.lead record.

Entera deals representing specific investment transactions map directly to Odoo opportunities stored as crm.lead records with type='opportunity'. Deal value maps to the expected_revenue field on the Odoo lead. Entera deal stage maps to Odoo stage_id with value-by-value mapping for each pipeline stage, preserving probability weights assigned to each stage in Entera's workflow configuration.

Entera pipeline stages such as Under Review, Due Diligence, and Closed Won map to corresponding Odoo crm.stage records. Each Odoo stage receives probability and sequence order values aligned to Entera's original stage definitions. The stage mapping preserves the deal progression logic that investment teams built in Entera's pipeline configuration, ensuring that deal lifecycle stages translate accurately.

Entera tenant records representing occupants linked to investment properties transform into Odoo res.partner records tagged with a 'Tenant' contact category. Lease terms including start date, monthly rent amount, and security deposit are stored as custom fields on the partner record. The original property reference is preserved through a custom x_property_id field linking back to the corresponding crm.lead representing the rental property.

Entera activities including calls, emails, and meeting notes linked to properties or deals map to Odoo's mail.activity and mail.message records. Call activities become mail.activity with activity_type_id set to 'Call', emails become mail.message records on the parent crm.lead or res.partner, and meetings become calendar.event records. Original timestamps and activity ownership resolved by email matching to Odoo res.users are preserved throughout the migration.

Entera files including lease documents, inspection reports, and financial statements re-upload to Odoo ir.attachment records linked to the parent crm.lead or res.partner. The file_name maps to ir.attachment.name and file_content maps to the datas binary field. File size limits apply per Odoo's ir_attachment model configuration and server settings for maximum upload size.

Entera's custom property fields including investment metrics, renovation status, HOA fees, and property condition ratings require new custom fields on the Odoo crm.lead model. FlitStack delivers a comprehensive field creation plan specifying each x_ field name, data type (monetary, float, selection, or date), and validation rules so the Odoo-side schema is schema-ready before the data migration begins.

Entera workflow rules that automated deal progression triggered by document uploads or stage changes do not transfer to Odoo natively. These automations must be rebuilt as Odoo automated actions using ir.actions.server or server actions defined in the Technical menu. FlitStack exports the complete workflow definitions including trigger conditions, action sequences, and filter criteria as a structured rebuild reference for Odoo developers.

Entera's AI-powered lease parsing and rent roll ingestion has no equivalent at the Odoo CRM layer. The document-driven field extraction that automatically populated deal metrics from uploaded PDFs does not translate to Odoo's native capabilities. Teams requiring this functionality must pursue custom OCR and AI development on the Odoo platform or integrate with third-party document processing services such as Azure Document Intelligence or Google Document AI.

Entera owner assignments resolve to Odoo res.users by email address matching during the migration process. Unmatched owners are flagged in a pre-migration report for manual resolution before the cutover window. A default fallback owner (typically the migration administrator or a designated system user) is assigned to any records where no matching Odoo user exists in the system.

Entera notes attached to properties, deals, or contacts migrate as Odoo mail.message records with the note=True flag indicating they are free-form notes rather than communication threads. Original author information, note body content, and timestamp data are all preserved from Entera's audit data. The notes remain linked to their parent crm.lead or res.partner record for complete contextual visibility within Odoo's activity stream.