Migrate from Convert Wire to Odoo CRM

Convert Wire contact records map directly to Odoo res.partner. The partner acts as the central record for both customer and company associations. Phone, email, address, and custom fields on the Convert Wire profile populate corresponding fields on the res.partner record. Active/commercial partner flags are set based on Convert Wire's account status field.

Convert Wire company records map to res.partner records with is_company=True. The company partner is created first, then individual contacts are linked via parent_id. Website, industry, and employee count fields map to Odoo's website, industry_id, and employee_count respectively. If Convert Wire stores parent-child hierarchies, the top-level company migrates first and child companies link via parent_id.

Convert Wire deal or opportunity records map to Odoo crm.lead. The lead stores name, expected revenue (wire amount), partner_id link to the customer, and stage_id pointing to the appropriate Odoo pipeline stage. Lost leads are preserved with the lost reason stored in Odoo's lost_reason_id field.

Convert Wire pipeline stages are mapped value-by-value to Odoo crm.stage records within the target sales team. Each stage's sequence, probability, and fold (is_won) flag are set to match Convert Wire's stage behavior. Stages that represent closed-won outcomes map to stages where is_won=True.

Convert Wire financial transactions (wire amounts, fees, status) are normalized into Odoo sale.order records linked to the corresponding crm.lead opportunity. Wire amounts populate amount_total, transaction dates map to date_order, and fee components become separate order lines with a designated fee product. If Convert Wire tracks invoice-level records, these map to account.move entries with partner_id, line items, and payment state.

Convert Wire activity logs (calls, emails, notes, follow-ups) migrate as Odoo mail.activity records linked to the target res.partner or crm.lead. Activity type, date, user assignment (user_id), and summary text are preserved. Completed activities retain their done_date timestamp. The original activity metadata ensures historical context is maintained for audit and relationship tracking purposes.

Convert Wire file attachments (wire confirmations, uploaded documents) re-upload to Odoo's ir.attachment table linked via res_model = the target Odoo model (res.partner, crm.lead) and res_id = the record ID. The original filename, mimetype, and file content are preserved. Files exceeding Odoo's default 25MB per-file limit are flagged for manual retrieval.

Convert Wire custom fields that do not map to a standard Odoo field require custom field creation in Odoo via Settings > Technical > Models before migration. FlitStack generates a custom field manifest listing field name (in snake_case), field type (char, float, selection, many2one), and whether the field belongs on res.partner, crm.lead, or another model.

Convert Wire owner IDs or email assignments are resolved against Odoo res.users by email match. Unmatched owners are flagged before migration; records are assigned to the admin user or held in a queue for manual reassignment. The original owner reference is preserved in a custom field (original_owner_id) for audit purposes.

Convert Wire notes and comments migrate as Odoo mail.message records with message_type = comment, attached to the corresponding res.partner or crm.lead record. The original note text, author email address, and create date timestamp are all preserved during migration to maintain complete conversation history and audit trails within the Odoo CRM interface.