Migrate from Kickserv to Odoo CRM

Kickserv Customers map directly to Odoo res.partner records with type='contact'. Customer name, address, phone, email, and website fields map to the equivalent res.partner fields. Kickserv customer properties migrate as custom fields on res.partner. Each Customer's original created_at timestamp is preserved in a custom field (x_kickserv_created_date) on the res.partner record after migration.

Kickserv contacts within a Customer become child res.partner records linked to the parent Customer partner via parent_id. First name, last name, email, phone, and job title map directly to their Odoo equivalents. Each contact's parent_id points to the Customer partner record. Contacts without a parent company become standalone res.partner records.

Kickserv Jobs translate to Odoo project.task if the team uses Odoo Project for work orders, or to crm.lead (Opportunity) if the job represents a sales opportunity. We determine the target based on Job type and your Odoo configuration during the planning phase. Job status (scheduled, in progress, completed) maps to task stage or opportunity stage.

Kickserv custom fields on Jobs migrate to Odoo custom fields on project.task (prefixed x_kickserv_). Field type is preserved — text fields become char, pick-lists become selection, numeric fields become float or integer. Your Odoo admin configures field visibility on task forms before migration.

Kickserv Estimates map to Odoo sale.order as quotations. Line items (Items in Kickserv) become sale.order.line records. Estimate status (draft, sent, accepted) maps to sale.order state. Tax calculations carry over if Odoo tax codes are pre-configured to match Kickserv tax setup.

Kickserv Invoices migrate to Odoo account.move records with type='out_invoice'. Invoice line items become account.move.line records. Payment status (paid, unpaid, overdue) maps to Odoo's payment_state field. Historical invoices retain original invoice dates, due dates, and amounts in the Odoo account.move record. Payment terms and invoice references are preserved where available.

Kickserv Employees migrate to Odoo hr.employee records linked to res.users. Employee name, email, phone, and role/position map to the equivalent fields. Owner or technician assignment on Jobs becomes the task's user_id in Odoo via email-matched hr.employee. Employees without Odoo user accounts are flagged on a pre-migration report for manual user creation before migration runs.

Kickserv Time Entries map to Odoo account.analytic.line records linked to the project/task. Entry date, duration, description, and employee link carry over. Unit amount and cost mapping depends on whether Odoo payroll is active — we preserve raw hours by default.

Kickserv Notes attached to Jobs or Customers migrate as Odoo mail.message records linked to the target record (res.partner, project.task). Rich-text formatting is preserved where Odoo's mail system supports it. Standalone notes without a parent record become note.note objects. Each migrated note retains its original creation timestamp from Kickserv.

Kickserv file attachments on Jobs, Customers, or Estimates re-upload to Odoo's ir.attachment table linked to the equivalent record. Files are stored in Odoo's filestore. Large files or inline images in notes are downloaded and rehosted. File size limits from Odoo apply.

Kickserv Items used in Estimates and Invoices may be standalone or linked to a product catalog. We map them to Odoo product.product records with a sale.order.line for each usage. If Kickserv Items have no product link, they become description-only lines in Odoo.

Kickserv scheduling events map to Odoo calendar.event records linked to the Job or task. Event start and end times, assigned employee, and description carry over to the calendar.event record. Recurring events are expanded into individual Odoo events. All-day events and timezone handling follows Odoo's calendar configuration for consistency.