Migrate from Swivl Tech to Odoo CRM

Swivl Tech Contact maps directly to Odoo res.partner. The email, phone, address, and company association fields align structurally. Swivl contacts without a company map to res.partner records with no parent_id. Multi-address contacts collapse to the primary address; secondary addresses are stored as custom fields for reference.

Swivl Tech Company maps to Odoo res.partner with partner_type='company'. The company name maps to the name field, domain to website, industry to industry_id (from res.partner.industry), and employee_count to employee_count. Parent-child company hierarchies in Swivl map to parent_id on res.partner. Additional company metadata such as fiscal year information, tax identification numbers, and credit limits are preserved as custom fields to ensure complete data transfer across your organizational structure.

Swivl Tech work orders have no direct Odoo equivalent. We map them to crm.lead records where type='opportunity'. Job description maps to description, scheduled_date to date_deadline, and the assigned technician's email resolves to an Odoo res.user linked via a custom x_tech_id field. Job status becomes a crm.stage within the active pipeline.

Swivl Tech's job_status values (New Job, Scheduled, In Progress, Completed, Invoiced, Cancelled) map one-to-one to Odoo crm.stage entries in the target pipeline. Each stage gets a sequence number matching Swivl's workflow order. Probability values are applied per stage from Odoo's standard defaults.

Swivl Tech line items (service description + amount) on a work order map to sale.order.line records when the Odoo Sale app is installed. If the Sale app is not active, line item data is preserved as a custom Char field (x_line_items) on crm.lead in a structured text format. We surface this decision before migration runs.

Swivl Tech stores job notes, GPS check-ins, and customer interactions as Activity Log entries with a timestamp and internal-user attribution. We migrate these as Odoo mail.message records linked to the crm.lead or res.partner via res_model and res_id. The Swivl create_date field maps to mail.message's date for timestamp continuity.

Swivl Tech scheduled visits with technician assignment, date/time, and customer map to Odoo calendar.event records linked to the technician's res.user (user_id) and the customer's res.partner (partner_ids). Swivl's scheduled_date maps to start_datetime and stop_datetime in Odoo. Additional visit metadata such as visit purpose, location details, and any associated notes are preserved to maintain full contextual information about each scheduled customer interaction.

Swivl Tech photo attachments migrate as binary records in Odoo's ir.attachment table with res_model pointing to crm.lead or res.partner. The original filename and content type are preserved. Inline images embedded in job notes are downloaded and re-uploaded as ir.attachment records.

Swivl Tech custom properties (e.g., x_vehicle_id, x_contract_type) are stored as arbitrary key-value pairs with no schema. We read every unique property key across all records, then create matching custom fields on crm.lead or res.partner via Settings → Technical → Fields in Odoo. Field type is inferred from the data: text values become char, numeric values become float or integer, dates become date.

Swivl Tech stores the assigned technician by email in work_order.assigned_tech. We match this email against Odoo res.user records (filtered by login). Unmatched technicians are flagged before migration; the team either creates the Odoo user first or assigns the crm.lead to a fallback user chosen at migration setup.

Swivl Tech maintains a timestamped history of job status changes. We represent each status transition as a mail.message with a structured body noting the old and new status values and the transition timestamp. This gives Odoo users an audit trail of the job's full lifecycle on the crm.lead record.

Swivl Tech invoices created against a work order map to Odoo account.move records when the Odoo Accounting app is installed. If Accounting is not active, the invoice number and amount are stored as custom fields on the crm.lead for reference. We surface this dependency at scoping.

Swivl Tech captures customer signatures as base64-encoded images stored against the work order. Odoo CRM has no native signature field on crm.lead. We preserve the signature as a binary custom field (x_customer_signature) on crm.lead and attach the original image as an ir.attachment for audit visibility.

Swivl Tech records post-job star ratings as integer values. Odoo CRM has no native star-rating construct. We preserve the rating as an integer custom field (x_swivl_rating, range 1–5) on crm.lead for reporting and historical reference. This enables you to analyze customer satisfaction trends over time, evaluate technician performance based on ratings received, and identify patterns in service delivery that can inform training and process improvements.