Migrate from Olqan to Odoo CRM

Olqan Contacts map to Odoo res.partner records with is_company set to False. The Olqan email field maps to email on res.partner; phone maps to phone; company association from Olqan maps to parent_id pointing to the company partner. We create all company partners first so that the parent_id lookup resolves at Contact import time. Lifecycle stage values from Olqan are stored in a custom char field x_olqan_lifecycle_stage for audit.

Olqan Companies map to Odoo res.partner with is_company set to True. Company name maps to name; address fields map to street, city, state_id, country_id, zip; industry maps to industry_id if the Odoo database has industry classification installed; size maps to employee_size as a char field. The domain field from Olqan is stored as website. Deduplication is by name and domain. Companies must import before Contacts because Contact records reference the parent company via parent_id.

Olqan Deals map to Odoo crm.lead records with type set to opportunity. Deal name maps to name; value maps to planned_revenue; stage maps to stage_id via a pre-configured stage lookup that we create in Odoo before migration. The Olqan pipeline assignment maps to a crm.team on crm.lead, which requires that the Odoo sales team exists in the destination database. Owner from Olqan maps to user_id on crm.lead via email resolution against Odoo res.users.

Olqan Tickets map to Odoo helpdesk.ticket if the Helpdesk module is active in the destination Odoo instance. Ticket subject maps to name; description maps to description; priority maps to priority; agent assignment maps to user_id; customer association maps to partner_id via email dedupe against res.partner. If Helpdesk is not present in the Odoo destination, we map tickets to crm.lead records with a tag indicating ticket origin, and the customer can install Helpdesk post-migration and reassign.

Olqan Projects map to Odoo project.project records if the Project module is active. Project name maps to name; description maps to description; start and end dates map to date_start and date_deadline. We link project team members from Olqan to Odoo project.task.assignee records via email matching against res.users. Milestones migrate as project.milestone records if the Odoo version supports them.

Olqan Tasks map to Odoo project.task. Independent tasks link to project_id as null; project-nested tasks link to the corresponding project.project record. Task title maps to name; description maps to description; assignee maps to user_ids (multi-user supported); due date maps to date_deadline; status maps to stage_id via a stage sequence we configure in Odoo before import. Subtask nesting is preserved where Odoo's project task hierarchy supports it.

Olqan Employee records map to Odoo hr.employee. Job title maps to job_title; department maps to department_id via a department name lookup; contact details map to work_email, work_phone, and private_email; manager hierarchy maps to parent_id referencing another hr.employee. Start date maps to hire_date. Employees are imported before projects and tasks so that assignee references resolve correctly. This object requires the Odoo HR module to be active.

Olqan Time Logs map to Odoo account.analytic.line for timesheet tracking. Hours map to unit_amount; date maps to date; billable flag maps to unit_amount with a separate non-billable flag mapping. The linked task or project reference maps to project_id and task_id on the analytic line. This object requires the Odoo Timesheets module. Historical time logs preserve the original amounts and dates without recalculation.

Olqan Invoices map to Odoo account.move records with type set to out_invoice for customer invoices. Invoice header fields (number, date, due date, status) map to name, invoice_date, invoice_date_due, and state. Line items map to invoice_line_ids with product, description, quantity, and price_unit. This object requires the Odoo Accounting module and assumes the chart of accounts is already configured. Paid invoices are migrated with state set to posted; draft invoices keep state as draft. Payment history migrates as account.move.line records with reconciled flags.

Olqan custom fields on any object migrate to Odoo custom fields created via Odoo Studio (Enterprise) or programmatically via the XML-RPC ir.model.fields API. Field labels and data types are preserved; picklist values become selection fields; multi-value fields become char or many2many depending on Odoo version. If the destination uses Odoo Community, custom field scope is limited to fields created during installation via Studio; programmatically created fields may require a custom module. We flag this constraint during scoping.

Olqan Owners and Users map to Odoo res.users. Resolution is by email address. Olqan user records referenced on Deals, Tickets, Projects, and Tasks must have a matching Odoo user before those records import. Any Olqan owner without a matching Odoo user enters a reconciliation queue for the customer's admin to provision the res.users record with the correct email and access rights before the migration resumes.

File attachments on Olqan Deals, Projects, Tickets, and Tasks migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding parent record. We preserve the original file name, file content, and create_date. Files above 25 MB are split into chunks for XML-RPC upload. Attachments import after their parent records so that the res_id reference is satisfied at insert time.