Migrate from Novo Work Order to Nutshell

Novo Work Orders map to Nutshell Deals. Department, priority, and status values — which have no native equivalent in Nutshell's Deal object — are stored as custom pick-list fields (Department__c, Work_Order_Priority__c, Work_Order_Status__c). Original work order number is preserved as Work_Order_Number__c for traceability.

Recurring maintenance schedules (daily, weekly, monthly, quarterly) and next-occurrence date are translated into Nutshell Tasks. The frequency field becomes Maintenance_Frequency__c custom pick-list; the next-due date maps to the Task due date. Assigning technician is resolved by email match to Nutshell users.

Equipment and infrastructure assets in Novo map to Nutshell Companies. Parent-child asset-location hierarchies (parent asset referencing a location asset) are handled via Asset_Location__c and Parent_Asset__c custom fields on the Nutshell Company record, since Nutshell's flat Company model does not natively support hierarchical asset-location structures.

Technicians and requestors stored as contacts in Novo map directly to Nutshell People. Name, email, phone, and address fields map directly. Email-match resolution against Nutshell users assigns OwnerId for task/deal ownership. Additionally, any duplicate detection based on email ensures that existing Nutshell People are linked rather than recreated, preserving activity history. Inactive or archived contacts are flagged for review, and unmatched contacts are assigned to a default owner until resolved.

File attachments (photos, PDFs, inspection reports) associated with a Novo Work Order are re-uploaded to Nutshell as Notes with a 'has_files' flag, or linked via the Nutshell Files API. Original file names and upload timestamps are preserved in the Note body or as custom fields.

Novo's multi-department routing structure (utilities, public works, facilities, cemeteries, airports) has no native equivalent in Nutshell. Department names are extracted from each Work Order and mapped to a Department__c custom pick-list field on the Deal. Your admin configures the pick-list values before migration.

Priority values (Emergency, High, Medium, Low, Preventive) from Novo Work Order are mapped value-by-value to a Work_Order_Priority__c custom pick-list on the Nutshell Deal. The full list of values is extracted from your Novo configuration during the planning audit. During migration, each record's priority field is validated against this list, and any unexpected values are logged for manual review, ensuring no priority data is lost or mis-assigned.

Novo Work Order status values (Open, In Progress, On Hold, Completed, Cancelled) are mapped to a Work_Order_Status__c custom pick-list on the Deal. Closed and Completed statuses set the Deal as Closed Won or Closed Lost based on your specification. Any status values not in the predefined list are logged for review, ensuring consistency and preventing accidental stage mis-assignments.

Parts and labor line items from Novo (description, quantity, unit cost, total cost) are aggregated and stored on the Nutshell Deal as Labor_Hours__c, Labor_Cost__c, Parts_Cost__c, and Total_WO_Cost__c custom number fields. If your team uses Nutshell's Products module, line items can alternatively be created as Product records linked to the Deal.

Internal work order notes and chronological activity log entries are migrated as Nutshell Notes attached to the corresponding Deal. Original timestamps and author names are preserved in the Note body. Public-facing customer communications from Novo's portal are stored as Notes with a 'customer-facing' flag.

Physical location records (buildings, facilities, zones) that are structured as parent-child hierarchies in Novo are represented in Nutshell as Companies with a Location_Type__c flag ('Facility', 'Zone', 'Site') and a Parent_Location__c lookup field. Nutshell's flat company model does not natively support hierarchical location trees.

Novo Work Order tags (e.g., 'HVAC', 'electrical', 'permit-required') have no native tagging system in Nutshell Deals. We preserve them as a comma-separated Tags__c custom text field on each Deal for filtering and reporting in Nutshell. After migration, you can build dynamic Nutshell reports that filter by these tags, and the Tags__c field can be updated manually or via Nutshell's API to reflect new categories as your service portfolio evolves.

Technicians and department heads assigned as owners in Novo are resolved against Nutshell users by email address. Unmatched owners are flagged before migration for your team to either invite to Nutshell or reassign to a fallback user. No record lands without a valid Nutshell owner.

Novo Work Order workflow rules (auto-routing, approval chains, email notifications, assignment logic) are not migrated. Nutshell's automation tools (sequences, task automation, pipeline rules) must be rebuilt. We export your Novo workflow definitions as a configuration reference document for your Nutshell admin to use during rebuild.