Migrate from Saleshiker to Odoo CRM

Saleshiker's Lead records map to Odoo crm.lead (the lead model). The lead's name, email, phone, source, and owner assignment migrate directly. Lifecycle stage from Saleshiker maps to a custom picklist field lead_original_stage__c on the Odoo lead for audit. We preserve the Saleshiker created_date as write_date in Odoo via the XMLRPC write call.

Saleshiker Contact records map to Odoo res.partner with partner_type set to contact. We map email, phone, mobile, function (job title), and owner (user_id) to their Odoo equivalents. The Saleshiker lifecycle stage property becomes a custom Char or selection field contact_original_lifecycle__c on the partner record. The contact-to-Organization link is resolved before migration so that the partner's parent_id (company) points to the correct Organization-Partner record.

Saleshiker's Organization records map to Odoo res.partner with is_company=True and partner_type=company. We map the organization name to partner name, domain to website, and address fields to the partner's street, city, state, country, and zip fields. Organization is created before any Contact import so that parent_id lookups are satisfied on Contact insert.

Saleshiker Deals map to Odoo crm.lead records where type=pipeline. The deal value (amount) migrates to expected_revenue on the Odoo lead. Expected close date maps to date_deadline. Pipeline stage maps to a stage_id reference that we resolve via the Odoo stage lookup (crm_case_stage) using the stage name as the dedupe key. Owner assignment migrates to user_id on the lead.

Each Saleshiker pipeline becomes an Odoo crm.team (sales team) with its own kanban stages. We create crm_case_stage records matching the Saleshiker's stage names and ordering, then assign the stage sequence to the team. The customer confirms the stage mapping table during scoping before migration begins.

Saleshiker Quotes migrate to Odoo sale.order records with state=draft. Quote headers (customer, validity date, payment terms) map to sale.order fields. Quote line items map to sale.order.line with product_id resolved via SKU lookup against the migrated product catalog and price_unit mapped from the quote unit price.

Saleshiker Invoice records migrate to Odoo account.move with move_type=out_invoice for customer invoices. Invoice headers and line items preserve; payment reconciliation history that depends on Saleshiker's internal AR/AP state does not carry over if Odoo's accounting module is not active, in which case we map invoice status to a custom Char field invoice_payment_status__c for the customer's admin to reconcile post-migration.

Saleshiker Products map to Odoo product.product (variant model) or product.template. We map name, default_code (SKU), list_price, and description to their Odoo equivalents. If the destination Odoo instance uses product template variants, we create the template and attach the product variant under it.

Saleshiker's Task records migrate to Odoo project.task. Title, description, due date (date_deadline), stage, priority, and user_id (assignee) map directly. Related-to linkage migrates to custom res_id and res_model fields pointing at the target Odoo record (res.partner or crm.lead) after parent-record resolution.

Saleshiker Events migrate to Odoo calendar.event with name, start (start_datetime), stop (stop_datetime), duration, and location preserved. Recurrence patterns (if stored as RRULE strings) migrate as calendar.recurrence records linked to the parent event. Assignee migrates to user_id on the event.

The Saleshiker Contact-to-Organization association is a critical lookup. We build a cross-reference table during data extraction: for each Contact, we capture the linked Organization ID and look up the corresponding Odoo res.partner record (is_company=True) by organization name or domain before inserting the Contact. parent_id on the contact partner record is set at import time to satisfy Odoo's partner hierarchy.

Saleshiker file attachments stored per record (Lead, Contact, Organization, Deal) are downloaded from Saleshiker's storage during extraction, then uploaded to Odoo via XMLRPC as ir.attachment records with res_model set to the target model (crm.lead or res.partner) and res_id set to the migrated record ID.