Migrate from Oncord to Odoo CRM

Oncord's single Contact object maps to Odoo Lead for records without an active sale and to Odoo Contact attached to an Account for records with a deal history or commerce association. We apply a split rule based on Oncord's contact tags, group membership, and any deal association. The original Oncord contact ID is preserved in a custom field x_oncord_id on both Lead and Contact for audit reconciliation.

Oncord Groups function as static segmentation lists. We map each Group to an Odoo Tag record on the res.partner model, or to a Channel if the group represents a sales team or routing list. Tags are linked via the res.partner.tag.rel many-to-many table. On Lite plans, filters restricted to Groups only are noted as a constraint in the mapping inventory.

Oncord CustomFields are extracted via its internal API component and mapped to Odoo custom fields created via ir.model.fields before migration. We handle type mapping: Oncord text and number fields map to Odoo char and float fields; date fields map to Odoo date; dropdown fields map to Odoo selection fields with the same options list. All custom fields must be deployed to Odoo before any partner records are imported.

Oncord Products (available only when the Commerce add-on was active) map to Odoo Product Template records. We extract product name, description, price, SKU, inventory count, images, and any custom product fields. Products with variants (size, color) map to Odoo Product Template with Product Variant lines. If the customer had the Commerce add-on, product data migration is included; if Commerce was never active, no product records exist to migrate.

Oncord discount rules and coupon codes map to Odoo's Loyalty Program or Coupon Program depending on whether the discount applies to a specific order or a general promotion. Eligibility conditions and usage limits are documented as a written mapping for the customer's Odoo admin to configure in the CRM or eCommerce module post-migration.

Oncord Events with RSVP and attendee lists map to Odoo Calendar Event records. Event name, date, location, capacity, and attendee list (linked back to Contact records) migrate. If the customer uses the Odoo Events module instead of the calendar, Events map to event.event records. Attendee status (attending, not attending, maybe) maps to calendar.event.type or a custom selection field.

Oncord admin users map to Odoo User records. We resolve by email match. Any Oncord Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision. Role semantics differ: Oncord's admin and editor roles have no direct Odoo equivalent, so we assign the Odoo Standard User or Portal User access level based on the customer's indicated function.

Oncord Web Forms and their field-to-contact-property mappings are documented in the written handoff inventory. Odoo's Form Builder or a third-party module (like website_form_builder) replaces Oncord forms. We do not migrate form code or embed scripts; we deliver a field-level map of every Oncord form so the customer's admin can recreate the form structure in Odoo.

Oncord automation workflows trigger on contact activity, group membership, or time-based schedules. We document the workflow structure (triggers, conditions, actions) in the written inventory. Migration of automation as code is not in scope. The customer receives a detailed list of every Oncord Automation with its trigger logic and a recommended Odoo Automated Action or Studio workflow equivalent, plus the specific Odoo version and module required to implement each one.

Oncord engagement records (calls, emails, meetings, tasks, notes) map to Odoo Mail Activity records or Project Task records depending on whether the destination Odoo instance includes the Project module. Email content maps to Odoo mail.message linked to the partner. Call disposition and duration map to custom fields on the activity record. Activity timestamps are preserved to maintain the timeline for sales reps.

Oncord Contacts with associated billing or shipping addresses map to Odoo res.partner records with the address fields populated. If the customer used Oncord's Xero or MYOB sync (available with Commerce add-on), address and company data is already structured for Odoo partner mapping. We preserve the Oncord contact source field as x_oncord_source on the partner for marketing attribution.

Oncord contacts that represent organizations rather than individuals map to Odoo res.company records or to contacts with company_type set to company and linked as child contacts. Oncord's business type or industry field maps to Odoo's industry_id (res.partner.industry) selection field.