Migrate from The Service Program to Odoo CRM

The Service Program stores customer records with business name, contact name, phone, email, and billing address. These map directly to Odoo's res.partner object. In Odoo, a partner can be flagged as 'is_company' for business accounts and as a simple contact for individuals. The Service Program's customer ID is stored in a custom field (tsp_customer_id__c) for traceability.

The Service Program links multiple service addresses to a single customer account — a property or job site separate from billing. Odoo models these as res.partner records with parent_id pointing to the billing partner. Each service location retains its own street, city, state, zip, and contact name. FlitStack preserves the location-to-customer linkage using Odoo's Contact Addresses model (res.partner address type).

Each work order in The Service Program — with its job description, scheduled date, assigned technician, status, and customer link — becomes an Odoo project.project record. The project name defaults to the work order number or customer name + date. Odoo's project.stage replaces The Service Program's status field (Open, Scheduled, Completed, Invoiced).

Work order line items (each service task, material used, or labor entry) map to project.task under the parent project. Odoo's task stages mirror the work order's line-item status. Original technician assignment maps to project.task's user_ids field. Task descriptions preserve the original service description text from the source line item.

Technician records in The Service Program (name, phone, email, certifications) map to Odoo's hr.employee object. Employee email enables Odoo's internal messaging and activity assignment. If Odoo's HR app is not installed, FlitStack creates a res.users record instead so the technician can log into Odoo and receive task assignments.

The Service Program exports invoice data to QuickBooks; the invoice metadata (invoice number, date, amount, customer, line totals) is migrated as Odoo account.move records under the accounting app. FlitStack does not migrate the full accounting ledger — only the document-level invoice history so Odoo's accounts-receivable reporting has a starting point. Original QuickBooks invoice numbers are stored in a custom reference field.

The Service Program stores a QuickBooks customer ID on each customer record to maintain the QB sync relationship. Since Odoo has its own native accounting module rather than a QB bridge, this QB ID is preserved as a custom char field (qb_customer_ref__c) for reference and any future QB-to-Odoo reconciliation your accountant may need.

Service businesses in The Service Program track equipment at a service location (e.g., a pool pump, HVAC unit, or lawn-irrigation system). These map to Odoo's product.product (for inventory-tracking items) or stock.production.lot (for serialized assets). Your Odoo administrator chooses the right model based on whether you need serial-number tracking and warranty management.

If The Service Program stores recurring service contracts or maintenance schedules (e.g., 'bi-weekly pool service'), these map either to Odoo's project recurring task feature or, if subscription billing is involved, to the sale.subscription object. FlitStack preserves the recurrence frequency and next scheduled date as custom fields so your Odoo admin can configure the automation after migration.

The Service Program supports custom fields per work order type. FlitStack creates corresponding custom fields on Odoo's project.project and project.task models before the migration runs. Field types are matched (char, selection, float, date) using the source field definition. Custom field metadata is documented in the migration plan for Odoo Studio setup.

Internal notes attached to work orders in The Service Program migrate as Odoo mail.message records on the corresponding project.task. This preserves the full service history and technician comments. Odoo's messaging thread model (mail.thread) renders these inline on the task form view.

The Service Program may hold unqualified prospects or 'estimates sent' records that are not yet active work orders. These map to Odoo's crm.lead object. The Odoo CRM pipeline kanban view gives your sales team a stage-based pipeline distinct from the project-based service workflow used for active jobs.