Migrate from Variable Soft CRM to Odoo CRM

VSCRM Lead records map to Odoo crm.lead. The lead's name, email, phone, source, status, and owner assignment migrate directly. VSCRM lifecycle stage maps to Odoo's lead_stage_id (New, Qualified, Proposal, Negotiation, Won, Lost). VSCRM's custom lead fields are discovered from the export file and created as Odoo Studio custom fields on crm.lead before import. Owner resolution uses email matching against Odoo's res.users table.

VSCRM Contact records map to Odoo res.partner with partner_type = 'contact'. The primary company association from VSCRM maps to the partner's parent_id (also res.partner as the Company record). VSCRM lifecycle stage on the contact becomes a custom field partner_lifecycle_stage__c in Odoo. VSCRM contact-phone and contact-email map to phone and email on res.partner. Contacts without a company association are imported as standalone res.partner records and linked to Deals separately.

VSCRM Company records map to Odoo res.partner with is_company = True. Company name becomes partner name, domain becomes website, industry maps to industry_id (Odoo's industry reference model), and employee_count maps to a custom field. Res.partner records with is_company = True are imported first so that child Contact records (is_company = False) can reference parent_id at insert time. This parent-child resolution is the critical ordering dependency for the Contact phase.

VSCRM Deal records map to Odoo crm.lead with type = 'opportunity'. Deal value maps to planned_revenue, expected_close_date maps to date_deadline, owner maps to user_id, and stage maps to stage_id. The VSCRM pipeline name maps to crm.team (sales team) in Odoo. Open deals with no associated Contact or Company in VSCRM are imported as standalone leads first and reconciled against res.partner records after Contact import. Closed-won deals set active = False in Odoo after migration.

VSCRM named pipelines map to Odoo crm.team records. Each team gets its own Kanban view with stage columns. VSCRM stage labels within each pipeline are recreated as crm.stage records under the corresponding team. Stages with no associated deals are created as empty container stages to preserve the full pipeline structure. The pipeline-stage mapping matrix is documented during discovery and deployed in Odoo before Deal import begins.

VSCRM deal stages (New, Qualified, Proposal Sent, Negotiation, Closed Won, Closed Lost) map to crm.stage records with sequence ordering preserved. Probability percentages migrate from VSCRM to crm.stage.on_change_state values. VSCRM custom stage properties (stage-specific notification rules, owner-assignment triggers) do not carry over and are documented separately for Odoo Automations rebuild.

VSCRM activities map to a combination of Odoo record types. Calls and meetings migrate as mail.message records with subtype 'mt_comment' and subtype设置 for call/discussion. Tasks migrate as project.task records linked to the parent crm.lead via project_id. Email content migrates to mail.message on the lead's chatter thread. All activity timestamps are preserved as write_date on the migrated record. Activity notes migrate as mail.message body text.

VSCRM custom fields on Contacts, Companies, and Deals are discovered from the export file header row. We create Odoo Studio custom fields of the closest matching type (Char, Text, Integer, Float, Date, Selection, Many2One) on the respective Odoo model before import. Multi-select or checkbox fields in VSCRM map to Odoo Char with comma-separated values or to selection fields if the set of values is enumerable and bounded.

VSCRM owner assignments on Leads, Contacts, Companies, and Deals map to Odoo res.users records by email address lookup. Any VSCRM owner without a matching Odoo user is placed in a reconciliation queue for the customer's Odoo admin to provision before Deal import. Owner display names are preserved in a custom field on the migrated record to prevent information loss if user provisioning is delayed.

VSCRM workflow automations are not exportable and have no portable format. We enumerate every active automation rule during the discovery call, recording the trigger event (record creation, field change, stage change), the condition logic, and the action taken. This inventory is delivered as a written handoff document for the customer's Odoo admin to rebuild using Odoo Automations. No automation logic migrates as code.

VSCRM tags on Leads, Contacts, and Deals migrate to Odoo crm.tag records. Tags are normalized (lowercase, stripped whitespace) and deduplicated before import. A tag's association with a specific record type (Lead vs Contact vs Deal) is preserved in a custom field on crm.tag so that tag filtering behaves consistently post-migration. Tags without any associated records are excluded from migration but noted in the handoff document.

VSCRM notes attached to Leads, Contacts, Companies, or Deals migrate as mail.message records on the Odoo record's chatter thread. The note body migrates as message_body in plain text; attachments migrate as ir.attachment records linked via res_model = 'crm.lead' or 'res.partner' and res_id = the migrated record ID. Note timestamps are preserved as message_date.