Migrate from Novo Work Order to HubSpot

Novo work orders map 1:1 to HubSpot tickets. Work-order number migrates as Ticket ID for traceability. Status, priority, description, and assigned-to fields map directly. Work-order type becomes a custom Ticket property. Asset linkage handled via custom association object linking tickets to assets.

Novo work-order status values (New, In Progress, On Hold, Completed, Cancelled) map to HubSpot ticket pipeline stage values via a value-mapping table. Each status maps value-by-value to ensure correct ticket lifecycles in HubSpot's default or custom ticket pipelines without losing historical context.

Novo priority values (Emergency, High, Normal, Low) map to HubSpot ticket priority via value mapping. This ensures correct triage in HubSpot's ticket queue view. Emergency and High-priority tickets surface immediately in HubSpot dashboards and can trigger workflow alerts.

HubSpot has no native asset object. We create a custom Asset object mirroring Novo's asset fields — serial number, location, category, condition, and purchase date — and configure the schema before migration data loads. Assets link to tickets via a custom Asset-Ticket association.

Novo links work orders to assets with a 1:N relationship natively. HubSpot requires a custom junction object or association property to replicate this. We create an Asset_Ticket_Link__c junction object capturing the relationship type (Installed Base, Repair Site, etc.) and link it per ticket.

Novo PM schedules map to a HubSpot custom PM_Schedule__c object containing interval, frequency, last-performed date, and next-due date fields. PM tasks linked to specific assets also migrate, with asset IDs preserved for re-association in HubSpot to maintain maintenance history continuity.

Novo customer records map directly to HubSpot contacts. Full name, email, phone, and address fields map 1:1. Multiple Novo customers can link to a single HubSpot contact record if your deduplication rules apply. Source system ID is preserved for delta-run de-duplication.

Novo company or organization records map to HubSpot companies. Company name, domain, industry, and employee count map directly where populated. Novo customer-to-company associations become HubSpot contact-company associations using HubSpot's native linking mechanism.

Novo departments (Public Works, Water, Parks, etc.) map to HubSpot Teams via transformation. We create HubSpot teams pre-migration matching Novo's department names and assign migrated users accordingly. Department-based routing in Novo must be rebuilt as HubSpot workflow rules or ownership assignments.

Novo work-order attachments — photos, PDFs, inspection reports — download and re-upload to HubSpot Files. Original filenames and parent-record associations preserved. Inline images in notes are extracted and rehosted as HubSpot-hosted assets. HubSpot's 25MB-per-file limit is enforced during migration.

Novo users and technicians resolve by email match to HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a fallback owner. Department affiliation on the user record maps to the HubSpot team assignment.

Novo workflows, auto-routing rules, and trigger-based assignments do not migrate. They must be rebuilt in HubSpot's workflow builder. We export full workflow definitions from Novo — trigger conditions, routing logic, and department assignments — as a rebuild reference document for your HubSpot admin.