Migrate from Ready_ to Odoo CRM

Ready_ Contact records map to Odoo res.partner with company_type = 'person'. Standard fields (name, email, phone, street, city, state, country, zip) migrate directly to the corresponding Odoo partner fields. If the Ready_ Contact is associated with a Company record, we set parent_id on the res.partner to point to the corresponding company-type partner. Custom fields on the Contact migrate to res.partner custom fields created in Odoo via Studio or module definition before import. Email uniqueness is enforced as a partner dedupe key during insert.

Ready_ Company records map to Odoo res.partner with company_type = 'company'. The company name maps to name, domain to website, and firmographic fields (industry, employee_count, annual_revenue) migrate to custom fields on the company partner record. Related Contacts import after the parent Company partner so that parent_id references resolve at insert time. We create the company partner first in every batch to satisfy the foreign key constraint.

Ready_ Deals map to Odoo crm.lead records. The deal value maps to planned_revenue, expected_close_date maps to date_deadline, and owner_team_member_id resolves to the res.users id via the email lookup table we build during owner reconciliation. Pipeline and Stage assignment requires a pre-migration mapping table because Ready_ allows fully custom pipeline and stage names. We create an Odoo Sales Team per unique Ready_ pipeline and map the stage names to Odoo stage sequence values.

Ready_ Activities (calls, emails, tasks) map to Odoo mail.activity records. The activity type (call, email, task) maps to activity_type_id, which we configure as custom activity types in Odoo CRM before migration. The timestamp, notes, and linked Contact or Deal reference migrate to the corresponding Odoo fields. We resolve the activity's linked record reference to the Odoo res.partner or crm.lead id before insert. Activity chaining and sequence order are preserved in the Odoo activity's note or in a custom sequence field if the customer's workflow depends on ordering.

Each unique pipeline name in Ready_ becomes a Sales Team in Odoo, and each stage name within that pipeline becomes a crm.stage record attached to that team. Stage sequence order migrates from Ready_ to Odoo's sequence integer. If the customer uses multiple pipelines with overlapping stage names, we scope the stage to the team to prevent collisions. Odoo's stage wizard_states (draft, open, won, lost) are assigned based on the stage name semantics collected during scoping.

Ready_ custom fields on Contacts (text, number, date, picklist) migrate to Odoo res.partner custom fields. We create the field definitions in Odoo before importing any Contact data, matching field type (char for text, integer for number, date for date, selection for picklist). Picklist values in Ready_ map to Odoo selection option tuples. Custom field values migrate as part of the Contact partner insert.

Ready_ custom fields on Companies migrate to res.partner custom fields using the same type-mapping logic as Contact custom fields. Because company-type partners and person-type partners share the same res.partner model, both Contact and Company custom fields live on the same Odoo model. We distinguish them during scoping by recording which fields apply to which company_type so that the Odoo admin knows which fields appear on which partner view.

Ready_ custom fields on Deals migrate to Odoo crm.lead custom fields. We create the field definitions in Odoo via Studio or module XML before importing any lead data. The type mapping follows the same rules as Contact custom fields. Custom field values migrate as part of the crm.lead insert.

Ready_ Team Members represent users and store name and email. We extract every distinct Team Member ID referenced on Deals, Activities, and Contacts, resolve the ID to the email address, then match against the destination Odoo res.users table. If a matching User does not exist, we flag it in the owner reconciliation queue and the customer's Odoo admin provisions the User before migration continues. Owner assignments on crm.lead and mail.activity reference res.users id.

Ready_ Notes attached to Contacts or Deals migrate to Odoo mail.message records as internal notes (message_type = 'comment', subtype = 'note'). The note body migrates as the message body, the linked record resolves to the corresponding res.partner or crm.lead id, and the original timestamp preserves the activity date. Attachments on Notes migrate as ir.attachment records linked via the res_model and res_id to the mail.message.

The Ready_ Deal Stage is extracted from the Deal record and maps to the sequence integer on the corresponding Odoo crm.stage within the appropriate Sales Team. Stage probability percentages from Ready_ map to Odoo's optional stage_hardness or a custom probability field if the customer uses stage-based forecasting. We build the complete stage sequence map during scoping before any Deal records are imported.

Ready_ maintains an association between Contact and Company records. During migration, we read the association table, extract the Company ID and Contact ID for each pair, then set parent_id on the Contact's res.partner record to reference the Company partner's res.partner id. This establishes the Odoo partner hierarchy used for displaying child contacts under the parent company in Odoo's partner views and reporting.