Migrate from ServicePower HUB to Odoo CRM

ServicePower HUB work orders map 1:1 to Odoo crm.lead records. The work order number becomes the lead name; job type (warranty, COD, standard) becomes a custom picklist field x_job_type. Original create date is preserved as x_original_create_date since Odoo's create_date reflects migration time.

ServicePower HUB customers map to Odoo res.partner records with partner_type = 'contact'. Primary service location becomes the partner's default address, and service locations are migrated as child address records (type = 'other') on the same partner. The original ServicePower HUB customer ID is stored in x_servicepower_customer_id for de‑duplication. If multiple contacts exist, each is created as a separate res.partner linked via parent_id, with billing or dispatch roles stored as tags.

Each ServicePower HUB service location maps to a res.partner address record with type = 'other' linked to the parent customer partner. Longitude/latitude data from ServicePower HUB is stored in Odoo's x_latitude and x_longitude custom fields to enable geo‑based routing rebuild. The original ServicePower HUB location ID is preserved in x_servicepower_location_id for reconciliation, and multiple locations per customer are supported as separate child partners.

Employed technicians in ServicePower HUB map to Odoo hr.employee records. Email addresses resolve by matching against existing Odoo users; any unmatched technicians are flagged in a pre‑migration report for account creation. Skill‑set tags from ServicePower HUB become Odoo skill records linked to the employee, and capacity‑band definitions (max jobs per day, working hours) are stored in custom fields for scheduling rebuild.

Contractor records from ServicePower HUB's contracted workforce model map to res.partner with x_is_contractor = True. Contract rates, W-9 status, and insurance expiry dates from ServicePower HUB migrate as custom fields on the partner record for compliance rebuild. Capacity‑band definitions (maximum jobs per day, working hours, coverage zones) are stored as custom fields on the partner for scheduling rebuild, and the ServicePower HUB contractor ID is preserved in x_servicepower_contractor_id for reconciliation.

ServicePower HUB service agreements and warranty contracts map to Odoo sale.subscription records when the subscription module is active. For CRM-only Odoo instances, contracts migrate as custom fields on the linked crm.lead. Contract start/end dates and billing frequency are preserved as x_contract_start_date, x_contract_end_date, and x_billing_frequency.

Parts used in ServicePower HUB work orders map to Odoo product.product records. The service parts catalog migrates as Odoo products with type = 'product'. Per-work-order parts lines become Odoo stock.move records linked to the corresponding crm.lead via a custom x_work_order_ref field. Distributor reference numbers map to vendor product codes.

Technician resolution notes from ServicePower HUB migrate to the crm.lead description field. If the note contains rich‑text diagnostics, parts‑replacement narratives, or inline images, the content is preserved as a mail.message record attached to the lead, maintaining full audit history visibility. Timestamps from ServicePower HUB are kept in the message creation date, and any referenced attachments are imported as ir.attachment records linked to the same lead.

ServicePower HUB capacity‑band definitions (max jobs per day, working hours, geographic coverage zones) have no native Odoo equivalent. We migrate them as custom fields x_capacity_band_max_jobs, x_capacity_band_start_time, x_capacity_band_end_time, and x_coverage_zone on the relevant hr.employee or res.partner record. These fields are intended for Odoo’s planning module or a field‑service add‑on to rebuild scheduling logic, and multiple capacity bands per technician are stored as separate records if needed.

Technician skill sets and performance criteria from ServicePower HUB map to Odoo's hr.skill model via ir.model.data references. Performance metrics (first-time fix rate, average job duration) become custom numeric fields on hr.employee. If Odoo Skills app is not installed, we create them as custom char fields x_skill_set and x_performance_rating.

COD payment records from ServicePower HUB map to Odoo account.payment records when the accounting module is active. Payment amount, method, date, and associated partner are preserved. If Odoo Accounting is not enabled, we preserve COD payment data as custom fields on the crm.lead (x_cod_amount, x_cod_payment_date).

Third‑party administrator (TPA) submission records from ServicePower HUB’s warranty job flow have no native Odoo equivalent. We preserve the TPA name, submission ID, authorization number, and claim status as fields (x_tpa_name, x_tpa_submission_id, x_authorization_number, x_claim_status) on the linked crm.lead. Submission timestamps are stored in x_tpa_submission_date, and the x_job_type = 'warranty' field ties the lead to these TPA fields, allowing Odoo’s accounting module to generate vendor invoices when the claim is approved.

ServicePower HUB tracks work order status transitions (created, dispatched, in-progress, completed, invoiced). Odoo crm.lead has stage_id transitions natively; we map ServicePower HUB status values to Odoo stage names. The full transition timestamp history is preserved as a JSON array in a custom field x_status_history for rebuild in Odoo's stage automation rules.

Photo attachments and documents uploaded to ServicePower HUB work orders (diagnostic images, signed forms) migrate to Odoo ir.attachment records linked to the crm.lead. File size limits from Odoo apply (default 25MB). Images inline in notes are downloaded, rehosted in Odoo's filestore, and relinked.