Migrate from eZnet CRM to Odoo CRM

eZnet CRM Accounts map directly to Odoo CRM Company records. Account Name becomes the Company name field, website maps to website, and phone/address fields map to Odoo's contact fields on the Company record. Account is imported before Contacts so that the parent-company lookup relationship is satisfied at the moment of Contact insert. We preserve any custom fields on the eZnet Account as Odoo custom fields on res.partner using Odoo Studio or direct Python model inheritance. Territory assignments from eZnet Enterprise map to Odoo CRM Sales Team or tags on the Company record.

eZnet CRM Contacts map to Odoo CRM Contact records (res.partner with is_company=False). First name, last name, email, phone, mobile, and address fields migrate directly. The Account-Contact link from eZnet is preserved by resolving the parent Company ID during import so that the Contact is linked to the correct Odoo Company at insert time. Duplicate detection is performed on email address before import.

eZnet CRM Leads map to Odoo CRM Lead records (crm.lead with type='lead'). Lead status, source, rating, and any custom lead fields migrate as Odoo custom fields on the Lead record. We preserve the eZnet lead stage and conversion date if the lead was previously converted. Unconverted Leads land in the Odoo Lead pipeline and can be converted to Opportunities through Odoo's standard Convert to Opportunity action.

eZnet CRM Opportunities map to Odoo CRM Opportunity records (crm.lead with type='opportunity'). Deal amount, expected close date, probability, and stage migrate directly. We pre-create Odoo pipeline Stages to match the eZnet pipeline structure, preserving stage names, order, and probability percentages. The Account lookup and Owner assignment resolve at migration time through email matching to Odoo User records.

eZnet CRM pipeline and stage configuration migrates as Odoo CRM Stage records within the appropriate Sales Team. Stage names, display order, and probability percentages are re-created in Odoo before Opportunity import begins. Odoo allows unlimited stages per pipeline, unlike eZnet's tier-constrained pipeline configuration on lower plans.

eZnet CRM Activities (calls, emails, tasks, events) split into Odoo Mail Message records for email content and Task records (project.task or mail.activity.type) for calls, tasks, and events. Each migrated activity links to the parent Contact or Company record via Odoo's res_id/res_model referencing mechanism. Activity date and owner are preserved; note content migrates as Mail Message body text. Some activity types may flatten into Odoo's Chatter log on the parent record rather than as separate records, which we document during scoping.

eZnet CRM Document Library records map to Odoo CRM attachments (ir.attachment records linked via res_model and res_id to the parent Company or Contact). Document metadata (name, description, file type, upload date) migrates; actual file blobs require separate file transfer handling and are flagged during discovery for explicit scope confirmation. We reparent attachments to the correct Odoo parent record after the Company and Contact imports complete.

eZnet CRM Users with role-based security map to Odoo User records. We resolve by email match and map eZnet role and profile assignments to Odoo Security Groups (Sales: User, Manager) and Sales Team assignments. Inactive users from eZnet are preserved in Odoo as inactive records so that historical Opportunity and Activity ownership is preserved for audit.

eZnet CRM custom fields on any object migrate to Odoo custom fields on the equivalent model (res.partner for Contact/Account custom fields, crm.lead for Opportunity/Lead custom fields). We capture the full field schema including data type, picklist values, and visibility settings during discovery. Odoo custom fields are pre-created via data migration script before record import begins. Picklist values migrate as selection fields or tags depending on the source field cardinality.

eZnet CRM Marketing Campaign records migrate to Odoo CRM Campaign (utm.campaign). Campaign name, start date, status, and budget migrate directly. Campaign member associations to Contacts migrate as Odoo CRM Salesteam tags or as Campaign members if the Odoo Marketing module is installed. Note that campaign automation rules, email sequences, and workflow triggers from eZnet do not migrate as code.

eZnet CRM Inventory Items (Professional tier and above) map to Odoo Product records (product.template). Item name, SKU, stock levels, and pricing migrate to Odoo product fields. Unit of measure and vendor information map to Odoo product variants if applicable. This object only migrates if the Odoo Inventory or Sales app is installed in the destination database.

eZnet CRM Customer Support module tickets migrate to Odoo Helpdesk tickets (helpdesk.ticket) if the Odoo Helpdesk app is installed. Ticket subject, description, priority, status, and assigned technician migrate directly. Linked Contact and Account resolve via the Odoo partner lookup at migration time. Resolution notes and internal comments migrate as Ticket messages.