Migrate from ServiceMonster to Odoo CRM

ServiceMonster customer records map directly to Odoo res.partner. The customer_name field becomes partner name, address fields map to street, city, state, zip, and country. ServiceMonster customer_type (residential/commercial) becomes a custom selection field on res.partner because Odoo does not distinguish residential from commercial natively.

ServiceMonster stores company data alongside customer records. When a customer record includes a company affiliation, we create a parent res.partner for the company and link the contact as a child partner via parent_id — preserving company hierarchy that ServiceMonster models in a single flat record.

ServiceMonster jobs map to Odoo project.task records. Each task links to a project record created per customer or per service category. Task name becomes the job description, scheduled_date maps to date_deadline, and job status (scheduled/in-progress/completed/cancelled) maps to Odoo stage values. Technician assignment becomes user_id on the task.

ServiceMonster job line items (services rendered) become sale.order.line records linked to the task's project. Each line references a product.product created from the ServiceMonster price list item. Quantity maps directly; unit price pulls from Odoo product.pricelist rules matching the customer segment.

ServiceMonster scheduled appointments map to Odoo mail.activity records with activity_type_id set to 'Meeting' or 'Call' based on appointment type. Original scheduled datetime, duration, and assigned technician (user_id) are preserved. Activity is linked to the corresponding res.partner or project.task record.

ServiceMonster route groupings (daily technician routes with ordered stops) have no direct Odoo equivalent. We create a project record per route, add task records for each stop in sequence order using a custom sequence field, and link the project to the assigned hr.employee for route visibility.

ServiceMonster technician profiles map to Odoo hr.employee records. Employee name, email, phone, and active status transfer directly. Skills and certifications become custom_char fields on hr.employee or tags in a dedicated skill.res.partner category — we assess which approach fits your Odoo configuration during discovery.

ServiceMonster price lists with area-based, square-footage, and flat-rate pricing map to Odoo product.pricelist and product.pricelist.item records. Each price list line becomes a pricelist.item rule with product_id, min_quantity, and fixed_price or percent_price values. Custom units of measure (gallons, sq ft) require product.template uom_id configuration.

ServiceMonster invoices map to Odoo account.move records with move_type='out_invoice'. Invoice lines link to product.product or sale.order.line depending on whether the invoice originated from a sale order. Payment state, invoice date, and due date transfer directly; reconciliation follows Odoo's accounting workflow.

ServiceMonster GPS check-in coordinates (latitude/longitude captured at job start and end) have no native Odoo field. We create custom decimal fields on project.task — sm_checkin_lat, sm_checkin_lng, sm_checkout_lat, sm_checkout_lng — storing the raw coordinates and timestamp for reference in Odoo's map widget or a custom view.

ServiceMonster custom fields of all types (text, number, checkbox, dropdown, date, file attachment) become Odoo custom fields via Settings > Technical > Custom Fields. Dropdown selection lists require ir.model.fields.selection entries matching the source pick-list values exactly. File attachments migrate as binary fields or stored as Odoo attachments linked to the record.

ServiceMonster file attachments on customers, jobs, and appointments become Odoo ir.attachment records with res_model and res_id pointing to the target Odoo model (res.partner, project.task). Original filename, mimetype, and create_date are preserved. Files are re-hosted in Odoo's filestore during migration.