Migrate from Novo Work Order to Pipedrive

Each Novo Work Order maps to a Pipedrive Deal. The work-order title becomes the Deal name, work-order status (Open, In Progress, Completed) maps to a corresponding Pipedrive deal stage, and the customer account referenced in Novo becomes the linked Organization. Work-order description text migrates as the Deal's first note or as a custom text field depending on length.

Individual work-order line items — parts used, labor entries, and status-change events — split into Pipedrive Activities. Each labor entry becomes a Task with type='Work Order Labor'; each status change becomes a Note with a timestamp. This preserves the operational history without forcing it into a flat Deal structure.

Novo Assets are physical equipment or locations tracked for maintenance. They map to Pipedrive Organizations with custom fields capturing the asset's serial number (Asset_Serial__c), equipment type (Asset_Type__c), and last service date (Last_Service_Date__c). If an asset has a linked customer account, the Organization is created under that account; standalone assets get a placeholder Organization.

Novo's parent-child asset relationships map directly to Pipedrive's Organization parent field. The top-level asset is created as the parent Organization; each child asset becomes a child Organization linked through the parent_org_id reference, preserving the original location and equipment hierarchy within Pipedrive. If the hierarchy exceeds two levels, FlitStack flattens deeper nodes or stores the full lineage in a custom text field (Asset_Hierarchy__c) for reference.

PM tasks in Novo have trigger conditions (meter-based or date-based) and procedure steps. These map to Pipedrive Activities with type='Task', a due date matching the PM schedule, and a custom text field (PM_Procedure__c) holding the procedure steps. Recurring PM tasks generate one Activity per occurrence in the migration window; historical PM history becomes Notes.

Novo technicians and requesters are contact records with name, email, phone, and department. They migrate as Pipedrive People, preserving email for owner resolution. Role (Technician vs. Requester) is stored in a custom field (Novo_Role__c) so Pipedrive users can distinguish who logged a work order versus who performed the service.

Novo departments (Public Works, Utilities, Facilities) map to a custom pick-list field on the Person record (Novo_Department__c) if the department is tied to a contact, or to an Organization label if tied to a company. We map each department name value-by-value to ensure no labels are lost in translation.

Novo tracks total work-order cost as labor hours times rate plus parts cost. Pipedrive has no native cost-tracking object, so FlitStack creates custom fields Labor_Cost__c, Parts_Cost__c, and Total_WO_Cost__c on the Deal. The deal's value (Amount) can optionally be set to Total_WO_Cost__c for reporting continuity.

Novo file attachments on work orders and assets—such as photos, PDFs, and inspection reports—are re‑uploaded to Pipedrive Files and linked to the corresponding Deal or Organization using Pipedrive's file API. Pipedrive enforces a 25 MB per‑file limit; any file exceeding this size is split into smaller chunks or flagged for manual handling. FlitStack tracks each attachment’s source ID and destination file ID in the migration audit log for traceability.

Novo's parts inventory has part numbers, stock levels, unit costs, and reorder points. Pipedrive has no inventory object. FlitStack migrates parts as a structured Note on the Organization representing the equipment that uses those parts, with part details (number, cost, stock) stored in a custom field for reference. Full inventory management must be handled separately or rebuilt in a dedicated inventory tool.

Novo's work-order statuses (Open, Scheduled, In Progress, On Hold, Completed, Cancelled) map to Pipedrive deal stages. Priority (Emergency, High, Medium, Low) maps to a custom pick-list field (Novo_Priority__c) on the Deal. Each mapping is value-by-value so the operational urgency is preserved in Pipedrive.