Migrate from ServiceTitan to Odoo CRM

ServiceTitan customers map directly to Odoo res.partner records with partner_type='contact' for individual contacts and partner_type='company' for business entities. The primary service location address is stored as a related address record on the res.partner. Email, phone, and mobile are mapped to Odoo's standard contact fields.

Each ServiceTitan service location becomes a separate res.partner record with type='delivery' or type='other', linked to the parent customer res.partner via the parent_id field. Latitude and longitude from ServiceTitan are stored as Odoo custom fields (x_studio_latitude, x_studio_longitude) since Odoo base CRM has no native geocoordinate fields.

ServiceTitan Jobs map to Odoo crm.lead records in the converted (opportunity) state. The job status (Scheduled, In Progress, Completed, Cancelled) maps to Odoo pipeline stages — your team configures stage names to match ServiceTitan's workflow. Job line items migrate as notes or custom fields; full invoice linkage requires the Odoo Accounting module.

ServiceTitan job status values (e.g., Booked, Dispatched, En Route, In Progress, Completed, Invoiced) are mapped one-to-one to Odoo crm.stage records within the designated pipeline. Each stage's sequence order and fold settings are configured to replicate the visual layout of ServiceTitan's pipeline board, so the migrated opportunities appear in a familiar workflow arrangement for your dispatch and operations teams.

ServiceTitan job types (e.g., Repair, Maintenance, Installation) migrate as crm.lead tags in Odoo. Tags provide flexible categorization without requiring a custom field definition. Multiple job types on a single ServiceTitan job create multiple tag entries on the corresponding crm.lead, preserving all categorized work types and allowing filtering by tag in Odoo's CRM views and reports.

ServiceTitan invoices migrate as Odoo account.move records if the Odoo Accounting module is installed. If Odoo CRM only is being migrated, invoices are preserved as custom-field-rich crm.lead records with invoice number, total amount, and payment status, but the full accounting ledger cannot be replicated without the Accounting app. We disclose this upfront during scoping.

ServiceTitan estimates and proposals map to Odoo sale.order records in 'draft' or 'sent' state. The Odoo sale.order holds line items, pricing, and terms. Converting a ServiceTitan estimate to an accepted quote in Odoo requires a manual step or Odoo workflow trigger after migration.

ServiceTitan technicians and staff members resolve to Odoo res.users by email match. Active users in Odoo receive ownership of migrated Jobs (crm.lead records) based on the technician assigned in ServiceTitan. If a ServiceTitan technician has no matching Odoo user, the record is flagged and assigned to a fallback user pending admin action.

ServiceTitan custom properties on Customer records require Odoo custom fields. In Odoo Community, this means a custom module with a Python field definition; in Odoo Enterprise, fields are created via Odoo Studio. We generate the field creation script during the migration plan phase so your Odoo admin can pre-create the schema before data loads.

ServiceTitan Pricebook entries map to Odoo product.product records. Unit price, cost, and uom (unit of measure) are transferred directly. Product categories in ServiceTitan become product.category records in Odoo. If the Odoo Inventory or Sale apps are installed, product variant management and stock qty fields are available post-migration.

Files and photos attached to ServiceTitan Jobs or Customers are downloaded from ServiceTitan storage and re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead or res.partner. File size limits follow Odoo's configured attachment storage settings (default 128 MB per file).

ServiceTitan notes and communication history attached to Jobs or Customers migrate as Odoo mail.message records linked to the target res.partner or crm.lead. Original author and create date are preserved as message metadata. Private notes (visible to author only) are stored as note.note records with access restricted to the original owner.

ServiceTitan service agreements and maintenance memberships have no direct Odoo CRM equivalent. If Odoo Subscriptions is installed, agreements can be modeled as subscription records with recurring product lines. Without that module, agreements migrate as tagged crm.lead records with custom fields capturing contract start/end dates and renewal terms.

ServiceTitan marketing campaign tracking data migrates into Odoo's native UTM (Use This Method) tagging system. Each distinct campaign name from ServiceTitan becomes a utm.campaign record, while tracking sources and mediums are created as utm.source and utm.medium entries respectively. The migrated crm.lead records carry the corresponding utm_* references, preserving the full attribution history so your team can analyze lead sources and campaign performance using Odoo's built-in reporting tools.

Call logs and SMS messages recorded in ServiceTitan migrate as Odoo mail.message records with a note subtype. The message body carries the call duration or SMS content, and the author is set to the ServiceTitan technician who logged the communication. Call disposition and outcome are stored as custom fields on the message record.