Migrate from Trade Service Pro to Odoo CRM

TSP customers map 1:1 to Odoo res.partner records. The partner_type field ('customer', 'invoice_address', 'delivery_address') determines the Odoo address role, allowing multiple address types per customer in the same table. The residential versus commercial distinction from TSP becomes a custom selection field (tsp_customer_type) on the partner record to preserve the original customer classification. Each TSP customer is validated against Odoo's partner constraints before insertion.

TSP jobs contain both lead context (customer info, trade type, service address) and scheduling context (assigned tech, job date, status). We split this: the lead/opportunity portion maps to crm.lead (type='opportunity'), and the work-order portion maps to project.task linked via crm.lead.task_ids. Original TSP job number is preserved as a custom field on both records for traceability.

TSP proposals map to Odoo sale.order records in state='draft'. Each TSP proposal line item becomes a sale.order.line linked to a product.product. TSP proposal status (sent, accepted, rejected) maps to Odoo sale.order state transitions. The original proposal number is stored as name on the Odoo record.

TSP invoices become Odoo account.move records of type='out_invoice'. Line items map to account.move.line with product references where available. TSP invoice payment status (paid, pending, overdue) maps to Odoo's payment_state field using the account_payment module's reconciliation logic. TSP invoice numbers are preserved as account.move.name, and TSP tax rates mapped by service address state and zip become corresponding account.tax records linked to the invoice lines.

TSP pricebook entries (service descriptions, unit prices, labor rates) translate to Odoo product.product records with type='service'. TSP pricing tiers become Odoo product.pricelist rules attached to those products. Each TSP service item receives a corresponding Odoo product so sale.order.line can reference it directly.

TSP users and technicians map to Odoo res.users. Email is the matching key. TSP role assignments (admin, back office, field tech) map to Odoo groups: field technician becomes Odoo's 'Project / Task User' group with access to project.task and crm.lead but not accounting journal entries.

TSP intake records capture the ad source or referral channel for each new lead. The TSP intake_source values map to Odoo crm.lead.source_id (crm.lost_reason for non-lead types). Value mapping is done per unique source string found in the TSP dataset; unmapped sources become a generic 'TSP Intake' entry.

TSP custom forms generate user-defined fields on customers and jobs. Each TSP custom field is created as an Odoo ir.model.fields entry on the appropriate model (res.partner for customer-level forms, crm.lead for job-level forms). Field types are inferred from TSP data types: text fields become char/-text, numeric fields become float, date fields become date. Custom field definitions are delivered as a setup plan before migration.

TSP permission sets (back-office vs field-tech access) have no direct Odoo equivalent. We preserve the TSP permission metadata in a custom field on res.users (tsp_original_permissions__c) and deliver a group-mapping plan so your Odoo admin can recreate access rules in Odoo's Security configuration before the migration goes live.

TSP file attachments (images, signed documents, inspection reports) attached to jobs and customers are downloaded and re-uploaded to Odoo's ir.attachment table, linked to the corresponding res.partner or crm.lead via res_model and res_id. Odoo's 100MB per-file limit covers most TSP attachment sizes; files exceeding this are flagged before migration.