Migrate from VAIL-CRM to Odoo CRM

VAIL-CRM Contact records map to Odoo res.partner with contact=True. Standard fields (name, email, phone, mobile, website, street, city, state, country) map directly to Odoo partner fields. Social media identifiers from VAIL-CRM (LinkedIn, Twitter handles) migrate to res.partner custom fields or the contact's user-defined fields. The partner_type flag (company vs individual) is set based on whether VAIL-CRM records are linked to a Company or are standalone individual contacts.

VAIL-CRM Company records map to Odoo res.partner with company_type='company'. Address fields (street, city, state, country, zip) migrate to the partner address fields. Website from VAIL-CRM becomes the partner website field and is used as the dedupe key during import. We create the company partner record before any child contact import so that the child contact's parent_id reference is satisfied at insert time.

VAIL-CRM's contact-company linking is preserved by setting the child contact's parent_id to the matching company partner record. We match on company name or VAIL-CRM company ID. If the same person appears as a contact under multiple companies in VAIL-CRM, we create multiple partner records in Odoo with separate parent_id relationships rather than collapsing them, since Odoo supports multi-company contact affiliations through the contact_is_company flag.

VAIL-CRM Deals map to Odoo crm.lead with type='opportunity'. Deal name becomes crm.lead name, deal amount becomes expected_revenue, close date becomes date_deadline, and the VAIL-CRM pipeline stage name maps to an Odoo CRM Stage ID. We extract the full stage probability percentage from VAIL-CRM and configure a corresponding stage in Odoo's CRM Stage management with the probability value set.

VAIL-CRM pipeline stages (names, sequence order, probability weights) are extracted during discovery and pre-configured in Odoo as crm.stage records within the relevant crm.team. Each stage probability migrates as the stage's probability percentage. The Odoo Stages must exist in the destination before Deal migration begins, or all Deals will land in the default stage.

VAIL-CRM custom pipeline configurations map to Odoo crm.team records. Where multiple VAIL-CRM pipelines exist (one per line of business or product), we create one crm.team in Odoo per pipeline, assign the team members, and map the pipeline's stages to that team's stage configuration. crm.team members map to Odoo res.users via email match.

VAIL-CRM call activity records (from the service automation or activity history) map to Odoo crm.phonecall with name, duration (in minutes), date, user_id (owner), and notes. Call disposition values from VAIL-CRM map to crm.phonecall tag or a custom selection field. The phonecall is linked to the related partner or lead via the crm.phonecall model references.

VAIL-CRM email engagement records migrate to Odoo mail.message records linked to the corresponding crm.lead or res.partner. Email body content, sender, recipient, and timestamp migrate to mail.message fields. Attachments migrate as ir.attachment records linked via mail.message.attachments. Email threading is preserved by matching on the message-id header if available.

VAIL-CRM meeting records map to Odoo calendar.event with name, start_datetime, stop_datetime, location, and description. Attendees migrate as calendar.event attendee records (res.partner records linked via calendar.attendee). Meeting organizer maps to res.users via email match. All-day meetings set allday=True with date instead of datetime.

VAIL-CRM notes attached to Contacts, Companies, or Deals migrate to Odoo note records on the respective model. Note body, author, and creation date migrate. Notes linked to a Deal that maps to a crm.lead attach to the lead; notes linked to a Contact attach to the res.partner record. The note's create_date is preserved for timeline ordering.

VAIL-CRM marketing automation campaign records map to Odoo utm.campaign records, which serve as the tracking source for all marketing activities in Odoo. Campaign name, start date, and end date migrate. Note that VAIL-CRM marketing automation workflows (triggers, conditions, actions) do not migrate as code; we deliver a written inventory of each campaign's workflow logic for the customer's admin to rebuild using Odoo's Marketing app Action Rules or external automation tools.

VAIL-CRM service automation tickets map to Odoo helpdesk.ticket records when the Helpdesk app is installed in the destination Odoo instance. Ticket subject, description, status, priority, and assignment migrate. VAIL-CRM custom ticket field configurations (priority tiers, category fields, resolution notes) map to Odoo helpdesk.ticket custom fields pre-created during schema setup. If the destination Odoo does not include the Helpdesk app, tickets are mapped to crm.lead notes as a fallback.

VAIL-CRM custom fields on any standard object (Contact, Company, Deal, Activity) are extracted during discovery with their field type, required status, and picklist values. We pre-create each custom field as an Odoo ir.model.data field before data migration begins, using the matching Odoo field type (char, selection, many2one, etc.). Picklist values migrate as selection options or many2many tags depending on whether the field is single-select or multi-select in VAIL-CRM.

VAIL-CRM owner assignments on Contacts, Companies, Deals, and Activities map to Odoo res.users by email match. We extract all distinct owner email addresses from VAIL-CRM records and match them against the destination Odoo user list. Any owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision the user before record migration continues. Owner assignments on Deals map to crm.lead user_id; owner assignments on Contacts map to res.partner user_id.