Migrate from Service Toolz to Odoo CRM

Service Toolz contacts map directly to Odoo res.partner records. The partner's company_type field is set to 'contact'. Email, phone, and address fields transfer as-is. Service Toolz does not separate leads from customers, so all contacts land as customer-type partners in Odoo — leads requiring nurture are flagged via a custom stage field.

Service Toolz company records map to Odoo res.partner with company_type='company'. Parent-child company hierarchies in Service Toolz map to the parent_id field on res.partner. Multi-address companies: primary address becomes the partner's record; additional locations map to res.partner address records linked by parent_id.

Service Toolz work orders are the core object in the source model and map to Odoo project.task when the Project module is installed. Each work order becomes a task with the original create date preserved as create_date. Technician assignment maps to user_ids on the task. Work order status (New/In Progress/Complete) maps to Odoo stage_id via value mapping defined per pipeline.

Line items on Service Toolz work orders — parts, labor, travel — merge into sale.order.line if the work order generated a billable quote, or into project.task description if it represents internal service work. Parts with product codes map to product.product by SKU match; unknown SKUs create placeholder product records flagged for review.

Service Toolz quotes become Odoo sale.order records in draft state. Quote number maps to name. Line items map to sale.order.line with product_id resolution. Quote expiration dates become validity_date on the order. Accepted quotes in Service Toolz trigger confirmation workflow — confirmed quotes map to sale.order with state='sale'.

Service Toolz products and services with pricing map to Odoo product.product. Unit price from Service Toolz maps to list_price. Products marked as 'service' type in Service Toolz set product_type='service' in Odoo. Bundle or package products map as is — Odoo's product pack module handles multi-item bundles if present.

Service Toolz status values (New, Scheduled, In Progress, On Hold, Complete, Cancelled) map to Odoo project.task stage records. We create stages matching the source status names in the target project's stage sequence. Stage transition timestamps from Service Toolz audit logs become stage_id change dates on the task record.

Service Toolz technicians and admin users resolve by email match against Odoo res.users. Unmatched users are flagged before migration — your Odoo admin creates the user record first or assigns records to a fallback user. Technicians assigned to work orders become user_ids on project.task. System-generated notes about technicians not yet migrated are preserved as message notes on the task.

Service Toolz file attachments on work orders and quotes re-upload to Odoo ir.attachment records linked to the corresponding res.partner, project.task, or sale.order. File size limits apply per Odoo's request configuration. Inline images in Service Toolz notes download and rehost as binary attachments in Odoo's filestore.

Service Toolz custom properties on work orders — user-defined fields like 'priority_level', 'service_category', or 'contract_id' — create new fields on project.task via Odoo Studio or direct model inheritance. Field type is inferred from source value format (text→char, number→integer, yes/no→boolean). Custom fields are created in the target Odoo database before migration runs.

Service Toolz scheduled appointments map to Odoo calendar.event records linked to the assigned technician's res.users and the related project.task. Event start/end times preserve original scheduled values. If Odoo is running the Appointments module, events can be rendered as public booking slots — confirmed appointments map with state='open'.

Service Toolz invoice records and payment status map to Odoo account.move (invoices) and account.payment. Invoice total maps to amount_total; payment records map to account.payment with matching partner_id. If Service Toolz invoices reference a sale.order, we link the account.move to that sale.order via the invoice_lines relationship.

Service Toolz workflows and automation rules do not migrate. These include quote approval chains, work order routing rules, notification triggers, and field-update automations. We export workflow definitions as JSON blueprints for reference. Rebuild in Odoo uses Automate Action (ir.actions.server) and Studio workflow stages.

Service Toolz custom reports and dashboards do not transfer. The underlying data (work orders, quotes, invoices) migrates, but the report layouts, calculated fields, and visualization configurations must be rebuilt in Odoo using the Reporting module, custom queries, or a BI connector.

Third-party integrations from Service Toolz — including QuickBooks Online sync, Twilio SMS, and Google Calendar links — do not migrate. We document each active integration with endpoint details and authentication method. Reconfiguration uses Odoo's Integration Apps or external API connectors with the same credentials.