Migrate from Wise Agent to Odoo CRM

Wise Agent contacts map directly to Odoo res.partner records. In Odoo, res.partner serves double duty — individual contacts and companies both live here, distinguished by the is_company boolean. Address fields, phone, email, and name map 1:1. Partner IDs resolve before opportunity records load since crm.opportunity references partner_id as a required foreign key.

Wise Agent company records become Odoo res.partner with is_company set to true. The company name maps to name, domain/website maps to website, industry maps to industry_id (Odoo stores this as a many2one to res.partner.industry). Parent-company hierarchies in Wise Agent map to parent_id on the Odoo partner record to preserve corporate structure.

Wise Agent uses label tags (buyer, seller, investor, prospect) to classify contacts. Odoo has no native label taxonomy on res.partner — partner categories exist but are many2many tags, not the flat label system Wise Agent uses. We migrate labels as a custom selection field (x_wise_label) on res.partner, preserving the exact label vocabulary from Wise Agent. Full label-to-category cross-reference exported as a CSV for Odoo admin review.

Wise Agent transactions — representing real estate deals — map to Odoo crm.opportunity records. The transaction name becomes opportunity name, transaction amount becomes expected_revenue, transaction stage (active, pending, closed) maps to Odoo stage_id using a value-mapping table. Each transaction is linked to the res.partner representing the primary contact via the partner_id field.

Wise Agent transaction stages (e.g., Active Lead, Under Contract, Pending, Closed) map value-by-value to Odoo CRM stage records within the relevant team pipeline. Probability percentages from Wise Agent stage settings are applied to the mapped Odoo stage. Stage-entered dates are preserved as custom datetime fields (x_stage_entered_date) on the crm.opportunity record.

Wise Agent stores MLS listing IDs linked to transactions. Odoo CRM has no native MLS field. We create a custom char field (x_mls_listing_id) on crm.opportunity and store the MLS listing reference there. This field does not drive any Odoo logic — it is a reference field for the brokerage team to reconcile with their MLS export.

Wise Agent transaction checklists track milestones (inspection, appraisal, loan approval, closing). Odoo has no equivalent checklist construct. Checklist items migrate as internal notes on the crm.opportunity using Odoo's mail.message system with a note flag — preserving the item description, completion status, and due date. Odoo project tasks are a more robust alternative if the brokerage wants to activate Odoo Project alongside CRM.

Wise Agent logged emails map to Odoo mail.activity records with activity_type_id = 'email'. Original send date becomes the activity's date_deadline, subject line maps to summary, and body content maps to note. Activities are linked to the res.partner record of the associated contact. This preserves the full email thread history on the partner timeline.

Wise Agent logged calls and meetings become Odoo mail.activity records. Call activities use activity_type_id = 'call'; meetings use calendar.event with the meeting subject, start datetime, and duration preserved. Owner of the activity is set to the Odoo internal user matched by email from the Wise Agent agent who logged the call or meeting.

Wise Agent custom properties — text, date, number, and pick-list types — migrate as Odoo custom fields. Text properties become ir.model.fields of type char or text on the relevant model (res.partner or cdoo.opportunity). Date properties become date fields. Pick-list properties require the Odoo admin to create the selection field first with the exact Wise Agent option values; we then map values by name during import.

Wise Agent owner assignments on contacts and transactions resolve by email match against Odoo res.users.login. Unmatched owners are flagged before migration — the team either creates Odoo users for them before the run or assigns their records to a fallback internal user. This prevents crm.opportunity records landing without a valid user_id owner.

Wise Agent drip email sequences, text automation rules, and lead routing logic have no functional equivalent in Odoo CRM's automation framework. FlitStack exports campaign definitions as a structured CSV showing step order, trigger conditions, delay intervals, and message content. The Odoo admin rebuilds these using Odoo Studio automation rules or the Odoo Marketing app based on this export.