Migrate from UPNIFY CRM to Odoo CRM

UPNIFY Client records map to Odoo res.partner with is_company=False. Standard fields (name, email, phone, mobile) migrate 1:1. Custom client fields map as ir.model.fields with the corresponding field type (char, integer, float, selection). We sequence the Client import after Company import so that the parent_id foreign key resolves to the correct res.partner record if the client is attached to a company. Spanish-first field names in UPNIFY API responses are normalized to English equivalents during the transform step.

UPNIFY Company records map to Odoo res.partner with is_company=True. This is the first object we import in the dependency chain because both Clients and Opportunities reference Company records via parent_id. Company name, website, industry, and address fields migrate 1:1. The parent-child linkage between Company and Client is preserved by resolving Company IDs during the Client import phase.

UPNIFY Opportunities map to Odoo crm.lead with type='opportunity'. Stage names from UPNIFY map to Odoo stage_id via a customer-supplied stage mapping document. The probability field migrates from UPNIFY's stage percentage to Odoo's probability on the stage record. Company linkage migrates as partner_id with parent_id pointing to the res.partner record created from the Company object. Owner assignment maps by email to the Odoo res.users record.

UPNIFY Prospects map to Odoo crm.lead with type='lead'. Lifecycle stage values that indicate pre-qualified status (such as nuevo, contactado) are preserved in a custom field for audit. Prospect records that represent the same entity as a migrated Opportunity are flagged for manual merge during UAT so that the customer decides which record to retain.

UPNIFY Quotations map to Odoo sale.order. The multi-currency metadata (embedded exchange rate, currency code) is flattened into a standard price field during the transform step by applying the recorded exchange rate to the quoted amount. We preserve the original currency and exchange rate in custom fields quotation_currency_id and quotation_exchange_rate for audit. sale.order is created before sale.order.line so that the order_id foreign key resolves correctly.

Each line item on a UPNIFY Quotation (product, quantity, unit price, discount) maps to a separate sale.order.line record linked to the parent sale.order. Product resolution uses SKU matching against the product.product table; if no match is found, the line is created with product_id=False and a description-only fallback for the customer's admin to resolve post-migration.

UPNIFY Products from Catalogs map to Odoo product.product. Fields migrate include name, default_code (SKU), list_price, and description. Stock quantity data is not consistently populated in UPNIFY and is flagged as not migrated; the customer's inventory team populates stock levels post-migration through the Odoo Inventory module.

UPNIFY Goals (team or user-level sales targets with period and target value) map to a custom crm.target model that we create during schema setup if it does not already exist in the destination Odoo database. Goal owner maps by email to res.users. The period field is preserved as a date range. Odoo does not have a native Goals object; this is a configuration-based mapping requiring custom model creation before import.

UPNIFY Calendar entries (tasks, reminders, appointments) map to Odoo calendar.event for time-bound activities and project.task for action items. The decision between event and task is based on whether the UPNIFY entry has a start and end time (event) or a due date only (task). Task status (completed vs open) migrates as state on project.task. Owner assignment resolves by email to res.users.

Tags applied across UPNIFY Clients, Companies, and Opportunities migrate to Odoo crm.tag records. The tag assignment per object is reconstructed using crm.lead.tag.rel for Opportunities and a custom ir.model.data reference for partner tags. We preserve the tag name and color if populated in UPNIFY.

UPNIFY custom fields on Clients, Companies, and Opportunities are pre-created in Odoo as ir.model.fields before any data import begins. Field types (char, integer, float, date, selection) map to equivalent Odoo field classes. Dropdown fields in UPNIFY become selection fields in Odoo with the same option values. Type mismatches are flagged during scoping for customer decision on normalization.

UPNIFY Users are mapped by email address to Odoo res.users. Active vs inactive status is preserved. Role and permission sets do not migrate because Odoo's access control groups (Sales / User: All Records, Sales / User: Own Records) differ from UPNIFY's role model. The customer's Odoo administrator reassigns group memberships post-migration. We hold any HubSpot Owner without a matching Odoo User in a reconciliation queue.

UPNIFY engagement history (email, call, meeting, note) maps to Odoo's mail.message and calendar.event objects. Emails and calls become mail.message records linked to the parent crm.lead or res.partner via model and res_id. Meetings become calendar.event with start_datetime and stop_datetime preserved. Notes become mail.message with subtype='comment'. Activity date ordering is preserved by setting create_date to the original UPNIFY timestamp. Task engagements map to project.task with Status and ActivityDate preserved.

UPNIFY Connect (WhatsApp conversation bundles, priced separately at approximately $449 for Connect 5K as a one-time credit pack) stores conversation history in a separate data store from the CRM contact record. Most destination CRMs, including Odoo, cannot ingest the WhatsApp message thread format natively. We assess whether to export the conversation history as a structured archive for the customer's records or treat it as export-only with no import into Odoo. This is disclosed during scoping and the customer makes the call before migration begins.