Migrate from ServiceTracker to Odoo CRM

ServiceTracker customer records map directly to Odoo res.partner. Company-level fields (name, phone, address) transfer as-is; individual contact records are created as child partners linked to the company partner record.

ServiceTracker sites are multi-address customer locations. Each site becomes a child res.partner record with type='other', preserving the site name as the partner display name so dispatchers can distinguish locations in Odoo's map view.

Open ServiceTracker work orders become Odoo crm.lead opportunities with the pipeline stage set to match the ServiceTracker status. Completed or cancelled work orders migrate as historical records with a 'Closed' stage; the original status is preserved in a custom field.

Active work orders with scheduled technician assignments also generate project.task records in Odoo's project module. This preserves the job-level task breakdown, time estimates, and actual hours that ServiceTracker tracks separately from the CRM pipeline.

ServiceTracker assets have serial numbers, model data, and install locations. These map to Odoo's maintenance.equipment model if the Odoo Maintenance module is installed, otherwise to product.product with custom fields for serial number, install date, and warranty expiry.

ServiceTracker contracts with recurring billing periods and coverage tiers map to Odoo sale.subscription. The contract number, start and end dates, and coverage scope transfer as custom fields on the subscription record.

ServiceTracker technicians are matched to Odoo res.users by email address. If a technician has no Odoo user account, FlitStack creates a portal-user record so the technician can access the customer portal without a full internal licence.

Each service visit logged in ServiceTracker becomes a mail.message on the related crm.lead or project.task, preserving the date, technician, and notes text. This gives Odoo users a full service timeline on every opportunity.

ServiceTracker custom fields created by the user (pick-lists, numeric fields, date fields) are created as Odoo custom fields on the target model (crm.lead or res.partner) before data loads, using Odoo Studio or Python model definition.

ServiceTracker files attached to work orders or assets are downloaded and re-uploaded to Odoo's ir.attachment table, linked to the corresponding crm.lead or maintenance.equipment record. The original filename and MIME type are preserved.

ServiceTracker invoicing records do not map to Odoo CRM — they belong in the accounting module and require a separate accounting migration pass. We preserve the invoice reference and amount as custom fields on the linked opportunity for reconciliation reference.

ServiceTracker dispatch rules, SLA triggers, and auto-assignment rules have no Odoo equivalent in the base CRM. We export the rule definitions as a JSON document so your Odoo admin can rebuild equivalent automation using Odoo Studio or server actions.

ServiceTracker report definitions and saved filters do not transfer. The underlying data (work orders, labour hours, parts used) migrates completely, so Odoo reporting can reconstruct equivalent analytics from the imported records.