Migrate from Sercom to Odoo CRM

Sercom's customer record maps to Odoo's res.partner. The partner can be marked as a company (is_company=True) or an individual contact. Odoo's commercial_partner_id handles parent-company hierarchy when a customer has multiple service locations. Email, phone, and address fields map directly; country_id is set from Odoo's res.country model.

Each Sercom job becomes an Odoo crm.lead record. The job name maps to crm.lead.name (opportunity title), job status maps to a custom selection field mirroring Sercom's status values (Scheduled, In Progress, Completed, Cancelled). The job's scheduled date maps to crm.lead.date_deadline for scheduling reference. Priority from Sercom maps to crm.lead.priority. The original Sercom job ID is stored in a custom Char field for traceability.

Sercom locations are multi-address records attached to a customer. Odoo stores addresses on res.partner itself — the customer record holds the primary address, and additional service locations require separate res.partner contact records (type='other') linked to the parent company via parent_id. FlitStack flags cases where one Sercom customer has more than three locations for manual review.

Sercom technicians map to Odoo res.users if they have Odoo login credentials. Job assignment (which technician handled a job) is stored as a custom Many2one field (x_technician_id) pointing to res.users on the crm.lead. Unmatched technicians are flagged and can be created as Odoo users before migration or left as free-text in a custom Char field.

Sercom job parts can be split across multiple records. If Odoo Inventory is installed, parts migrate as stock.move.line records linked to a picking linked to the opportunity. Without Odoo Inventory, parts data is consolidated as a JSON-formatted Char field on the crm.lead for reference. FlitStack surfaces which approach your Odoo instance supports before migration runs.

Sercom tracks job status changes with timestamps. Odoo has no native status-history table for crm.lead. FlitStack stores status transitions as a serialized JSON custom field (x_status_history__c) and logs them as mail.message entries in Odoo's chatter for visibility without a custom audit module.

Files attached to Sercom jobs (photos, signed forms, job reports) migrate to Odoo ir.attachment records linked to the corresponding crm.lead via res_model='crm.lead' and res_id=lead_id. Odoo Community self-hosting can accept large files; Odoo Online has a 115MB per-file limit enforced at upload time.

Sercom internal notes map directly to Odoo mail.message records with message_type='comment' and subtype='note'. The note body migrates as the mail.message body field, preserving the original content, timestamps, and the user who created each comment in Sercom. This ensures that internal discussions and context from past jobs carry forward into Odoo for continuity of team knowledge and handoff documentation.

Sercom custom fields that have no Odoo standard equivalent are created as custom fields on crm.lead before migration. Selection-type Sercom fields become ir.model.fields with ttype='selection'; Char/Text become ttype='char' or 'text'; date fields become ttype='datetime'. The migration plan lists each custom field with its target Odoo field name and required field type.

Sercom automation rules (email on job completion, status-change notifications) have no direct Odoo equivalent. FlitStack exports rule definitions as a structured JSON reference document and provides an Odoo Studio rebuild guide. The automation layer must be recreated by your Odoo admin post-migration using server actions or Odoo's CRM team assignment rules.