Migrate from ServeCircle to Odoo CRM

ServeCircle job sheets map directly to Odoo crm.lead records. The job sheet number becomes the opportunity name, service type maps to Odoo lead source or a custom field, and job status maps to the Odoo CRM stage picklist value. Original technician assignment resolves to Odoo res.users via email match.

ServeCircle service accounts (client profiles attached to job sheets) map to Odoo res.partner contacts. The account name becomes partner name, contact email and phone map directly, and branch association stores as a partner tag or custom field since Odoo does not have a native branch model.

Each ServeCircle branch maps to a separate res.company record in Odoo if the multi-company configuration is enabled. If only single-company mode is used, branch names store as tags on crm.lead and res.partner records. Branch inventory pools require Odoo Inventory app activation and warehouse creation per branch.

ServeCircle technician records (engineers assigned to job sheets) map to Odoo res.users by email match. Technician role (service engineer vs. front-desk) maps to Odoo internal user category or a custom field. Unmatched technicians are flagged before migration for team assignment or user creation.

ServeCircle quotations generated in the Advanced tier map to Odoo sale.order records in draft state. Line items map to order lines with product reference. Approval status in ServeCircle maps to Odoo internal order state — pending approvals become draft quotations awaiting confirmation.

ServeCircle service invoices map to Odoo account.move records with type 'out_invoice' for customer invoices. Payment status (pending, confirmed) maps to Odoo invoice state (draft, posted). The invoice number, date, customer reference, and line item totals all transfer directly. This mapping requires the Odoo Accounting app to be installed on the destination database, and journal configuration must be completed before invoice records can be created.

ServeCircle service type picklist values (mobile repair, computer repair, warranty service, etc.) map to Odoo crm.tag records. Value-by-value mapping is required because the picklist values are free-form in ServeCircle and must be explicitly linked to Odoo tags during migration planning.

ServeCircle job status values (registered, in-progress, on-hold, completed, delivered) map to Odoo CRM stage definitions. Stage sequence order must be configured in Odoo CRM pipeline settings before migration runs so the stage_id foreign key resolves correctly. Each stage maps to a specific pipeline stage record that must already exist in Odoo when the migration loads crm.lead records.

ServeCircle file attachments on job sheets (marked Coming soon but may contain historical files) migrate to Odoo ir.attachment records linked to the crm.lead via res_model and res_id. File content is base64-encoded and re-uploaded to Odoo's filestore during migration. If historical attachments exist in ServeCircle exports, they are included in the migration run and preserved as Odoo attachment records accessible from the opportunity form view.

ServeCircle custom fields added in Advanced or Enterprise tiers require Odoo custom field creation via Settings > Technical > Custom Fields before migration. Field type mapping follows: text fields to char/text, numeric fields to float, date fields to date. Custom fields on job sheets map to custom fields on crm.lead.

ServeCircle Enterprise escalation level management maps to Odoo crm.lead.priority field using a numeric scale (0-Low, 1-Normal, 2-High, 3-Very High). This preserves the urgency ranking of job sheets as they move through the service pipeline. The escalation chain logic that defines automatic escalation triggers requires manual rebuild using Odoo Studio workflow rules or server actions — this is preserved as a migration plan note for the Odoo administrator to implement post-migration.

ServeCircle warranty service claims options and claim accounts for franchisees map to custom fields on res.partner in Odoo. A warranty_claim_account field stores the franchisee claim account reference for each customer contact. Odoo 售后服务 (after-sales service) module can be activated for full warranty workflow management including claim creation, resolution tracking, and replacement parts ordering from linked inventory. This extends beyond pure data migration into workflow configuration territory.