Migrate from Wyvern Magic to Odoo CRM

Wyvern Magic Contacts map directly to Odoo CRM Contacts (res.partner with customer_rank set to 1). Standard fields (name, email, phone, street, city, country) migrate as typed fields on res.partner. Custom contact properties from Wyvern Magic (such as industry classifications or custom rating fields) are mapped to custom Char, Selection, or Float fields on the res.partner model that we pre-create via Odoo's Settings > Technical > Models interface before migration. Owner email from Wyvern Magic maps to the user_id field on the Odoo partner record.

Wyvern Magic Company records map to Odoo CRM Company records (res.partner with customer_rank set to 0 and is_company = True). The Wyvern Magic domain field maps to the website field on res.partner. We create the Company records before Contact import so that the child Contacts can reference the parent Company via the parent_id field on res.partner. Employee count, industry, and any custom company fields migrate as typed custom fields on the res.partner model.

Wyvern Magic Deals map to Odoo CRM Opportunities (crm.lead with type = 'opportunity'). The Wyvern Magic dealstage property maps to the stage_id field on crm.lead, which references a crm.stage record. The pipeline assignment from Wyvern Magic maps to a crm.team record that we create and configure before migration. Deal amount, close date, and probability migrate to expected_revenue, date_closed, and the probability field on the Opportunity.

Wyvern Magic Lead records map to Odoo CRM Lead records (crm.lead with type = 'lead'). Lead status, lead source, and any custom lead scoring fields migrate to the crm.lead fields priority, source_id (via crm.lead.source), and a custom float field for imported lead score values. Owner assignments migrate via user_id on crm.lead by email lookup against Odoo User records.

Wyvern Magic pipeline definitions (stage names, probabilities, stage order) are extracted during discovery and recreated in Odoo CRM as crm.team records (one per pipeline) with corresponding crm.stage records (stage_ids on the team). We set sequence values to match Wyvern Magic's stage ordering and probability percentages on each stage. This configuration step is required before any Deal or Opportunity records can be imported.

Wyvern Magic Engagement records (email, call, meeting, note, task) migrate to Odoo CRM as crm.lead log notes (mail.message with model = 'crm.lead' and sub_type = 'crm.lead_msg_act') for activities attached to Leads or Opportunities, and as mail.message records linked to res.partner for activities attached to Contacts. Call subtype, duration, and disposition map to custom fields on the log note record. Meeting activities create crm.calendar.event records with start_datetime, stop_datetime, and attendee_ids preserved. All activity timestamps and owner assignments migrate directly.

Wyvern Magic Owner records map to Odoo User records (res.users) by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Lead records and resolve them against the destination Odoo instance's User table. Any Wyvern Magic Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status on the Odoo User controls read/write access post-migration.

Wyvern Magic custom objects with tenant-specific schemas migrate to Odoo custom models (ir.model records with a custom model definition). We inspect the Wyvern Magic custom object schema during discovery, create the matching Odoo model with the same field types (Char, Integer, Float, Date, Many2one, One2many, Text, Selection), and set up any lookup relationships to standard objects (res.partner, crm.lead) before importing data. Custom object records with required field constraints must have those constraints satisfied during import or the batch fails.

Wyvern Magic custom fields on standard objects (Contacts, Companies, Deals, Leads) migrate to Odoo custom fields on the corresponding Odoo model (res.partner for Contacts and Companies; crm.lead for Leads and Opportunities). We use Odoo's Settings > Technical > Fields interface to pre-create each custom field with the correct type (Char, Integer, Float, Selection, Date, Datetime, Text, Many2one) inferred from the Wyvern Magic property type during the discovery type-inference step.

Wyvern Magic tags applied to Contacts, Deals, and Companies migrate to Odoo CRM tags (crm.tag records) and are associated to the res.partner and crm.lead records via the crm.tag.rel many-to-many table. Multi-value tag arrays from Wyvern Magic are flattened into multiple crm.tag entries per record. Tag names and tag colors (if stored in Wyvern Magic) are preserved as tag_name and color fields on the crm.tag record.

Wyvern Magic attachments stored with URL references or file export are migrated as ir.attachment records linked to the parent res.partner or crm.lead record. The attachment name, URL, and associated record reference migrate directly. Large file attachments may require a separate file-migration pass after the record migration, depending on Odoo's attachment storage configuration (file store vs database storage) and the customer's file size limits.

Historical analytics, dashboards, and report configurations from Wyvern Magic do not migrate. Odoo provides a native CRM dashboard and reporting tool (crm.forecast.report and custom Pivot/Graph views) that the customer configures post-migration. We deliver a written summary of the reporting structure in Wyvern Magic (report types, fields used, filter logic) as a reference guide for rebuilding in Odoo.