Migrate from Novo Work Order to HighLevel

Novo Work Orders map directly to HighLevel Opportunities. The work order name becomes the Opportunity name, the current status maps to a custom picklist field, and the assigned technician resolves to a HighLevel user by email match. Closed and open status is preserved; cancelled orders are flagged via a status label in the custom field.

Novo's priority levels (Low, Medium, High, Emergency) map value-by-value to a custom Priority picklist on HighLevel Opportunities. This preserves the original priority label for reference during work order execution. No probability weighting is applied automatically; HighLevel's Pipeline stage probability handles deal-stage forecasting separately from work-order priority, meaning your team will see the priority field in reports but it won't affect deal win probability calculations.

Novo's total work order cost field migrates as a custom currency-formatted number field on the Opportunity. HighLevel does not support multi-line cost breakdowns natively; parts, labor, and materials are stored in a separate Custom Object (Work Order Line Items) linked to the parent Opportunity.

Novo assets are equipment or infrastructure records that carry location, serial number, and maintenance history. These map to HighLevel Companies with address and contact data populated from the asset's primary location. Equipment serial numbers and asset IDs are stored in custom fields on the Company record for traceability.

Novo PM schedules define recurring work orders based on time intervals or meter readings. HighLevel has no native preventative maintenance object. PM data is migrated as a Custom Object record with interval, unit, and last-completed fields; recurring triggering must be rebuilt in HighLevel Workflows using the custom object's date fields as the trigger condition.

Novo's multi-department model assigns work orders to specific departments with independent routing and permissions. HighLevel does not have a native department object. Department labels migrate as a custom picklist field on Opportunities and Contacts, and department-level routing is replaced with HighLevel Teams or individual user assignment based on the source department's member list.

Novo contacts associated with work orders — including requestors, dispatchers, and assigned technicians — map directly to HighLevel Contacts. Email, phone, name, and address fields carry over directly. User records in Novo are matched to HighLevel users by email address; technicians without HighLevel accounts are migrated as Contacts and flagged for team assignment.

Novo records labor hours against work orders with technician name, hours worked, and hourly rate. HighLevel Opportunities do not have a native labor line item. We create a Work Order Labor custom object linked to the parent Opportunity, storing technician, hours, rate, and total cost as separate fields.

Novo's communication logs, status updates, and internal notes map to HighLevel Tasks. The original timestamp and owner are preserved. HighLevel Tasks do not support hierarchical sub-entries natively; long note strings from Novo are stored in the Task description field with the original author noted in a custom field.

Novo custom fields on any object are migrated to identically named custom fields in HighLevel. Picklist custom fields preserve their value set. Multi-select picklists map to HighLevel's multi-select format. Custom field type conversions (date to text, number to currency) are applied based on the source field's data type as read from the export.

Novo work order attachments and documents are re-uploaded to HighLevel as Files linked to the parent Opportunity or Contact. File size limits apply; HighLevel supports up to 100MB per file on most plans. We re-upload inline images from notes and preserve the original file name in the HighLevel file record.

Novo tracks parts and inventory consumed per work order. HighLevel does not have a native inventory management feature. Parts used are migrated as a custom Parts Inventory object linked to the Opportunity, storing part name, SKU, quantity, unit cost, and total cost. Stock replenishment triggers must be rebuilt as HighLevel Workflows if needed.