Migrate from APRO CRM to Odoo CRM

APRO contacts map to Odoo res.partner records. Individual contacts use partner with is_company=False; contacts tied to real-estate companies map with is_company=True. APRO contact properties become ir.model.data custom fields on res.partner. Primary company association in APRO maps to partner's parent_id field in Odoo.

APRO company records map 1:1 to Odoo res.partner with is_company=True. Company name, domain, industry, employee count, and annual revenue fields map to their Odoo equivalents. Address data maps to res.partner's street, city, state, country, and zip fields. Parent-company hierarchies in APRO map to parent_id in Odoo.

APRO deals map to Odoo crm.lead records. The deal name becomes crm.lead name field. Deal amount, close date, owner, and stage all map directly. APRO pipeline stages map to Odoo crm.stage records scoped to the target crm.team. Note that APRO deals with multiple associated properties require a custom field to store the primary property reference.

APRO pipeline becomes an Odoo crm.team record with its own crm.stage set. Each APRO pipeline stage maps to a crm.stage within that team. Stage sequence order is preserved. If APRO has multiple pipelines, each becomes a separate crm.team in Odoo. Teams must be created before stage assignment in the migration sequence.

APRO's property object (listing data, property type, status, automatch rules) has no direct Odoo CRM equivalent. Properties can map to product.product with custom fields (x_property_type, x_listing_status, x_owner_id) or a dedicated real_estate module. The primary approach is a custom field on crm.lead to reference the property. Owner/agent associations use partner_id lookups.

APRO call logs and email threads map to Odoo mail.message records linked to crm.lead or res.partner via res_model and res_id. Original timestamps, body content, and author IDs are preserved. SMS threads map to mail.message with subtype 'mail.mt_comment'. Meeting records from APRO map to calendar.event with attendee links to res.partner.

APRO owner assignments resolve by matching owner email to Odoo res.users.login. Unmatched owners are flagged before migration. Default fallback assigns records to the admin user. Odoo's user-record structure (res.users) differs from APRO's owner model — APRO owner properties become custom fields on crm.lead linked to the assigned res.users record.

APRO custom properties on contacts, companies, and deals require custom fields in Odoo. For Community edition, fields use x_ prefix (x_custom_field). For Enterprise, Studio-generated fields use x_studio_ prefix. Custom field type mapping: APRO text/number types map to Odoo char/float fields. Pick-list values require manual setup in Odoo's selection fields before migration.

APRO file attachments on records migrate to Odoo ir.attachment records linked via res_model and res_id. Files are re-uploaded to Odoo's filestore. Original filenames and create dates are preserved as display_name and create_date. Binary content for property documents, contracts, and listing images migrates with full fidelity.

APRO's custom automation algorithms do not have a direct Odoo equivalent. They must be rebuilt in Odoo using ir.actions.server (Python actions), base.automation rules, or Odoo Studio visual workflows. We export the rule definitions from APRO as a reference document for Odoo administrators to reconstruct the logic post-migration.

APRO's bundled IP telephony call history (call duration, direction, status, recording links) maps to Odoo's crm.phonecall model (if OCA module is installed) or to mail.message records with phone-related metadata. Call recording URLs are preserved as external links in custom fields. Teams without the phonecall module receive call data as activity logs on the linked partner/lead.