Migrate from WennSoft to Pipedrive

WennSoft Service Calls are the core record — each call has a call number, customer, location, equipment, technician, status, problem type, billing rate, and timestamps. In Pipedrive, a Deal captures the commercial intent. We map call number to a custom field (Original_Call_Number__c), call status to a value-mapped custom field (Call_Status__c), and original create/update timestamps to custom datetime fields. The Deal's monetary value maps from WennSoft's estimated or actual billing amount.

WennSoft's customer master is the GP Customer record — it holds company name, address, billing terms, and the primary contact. In Pipedrive, Organizations hold company-level data. We map Name, Address, Phone, Web, and Industry directly. WennSoft's customer credit limit and tax schedule do not have Pipedrive equivalents and are stored as custom fields for reference.

WennSoft supports multiple service locations per customer — each with its own address, contacts, and equipment list. Pipedrive Organizations are flat. We map the primary location to the Organization record. Secondary locations are created as additional Organizations and linked via a custom Parent_Location_ID__c field, or flagged in the primary Organization's notes for admin review.

WennSoft's Equipment Manager holds serial number, model, install date, warranty expiration, and maintenance history per piece of equipment. Pipedrive has no native asset object. We create custom fields on the Organization record for serial number (Equipment_Serial__c), model (Equipment_Model__c), and install date (Equipment_Install_Date__c). Active work orders referencing equipment link the Equipment ID as a custom field on the Deal.

WennSoft Service Contracts define coverage scope, billing rates, contract terms, and renewal dates per customer or per equipment. Pipedrive has no contracts object. We store contract number in Contract_Number__c, coverage start/end dates in Contract_Start__c and Contract_End__c, and billing rate in Contract_Billing_Rate__c — all on the Organization record. Contract status (Active, Expired, Pending Renewal) maps as a value-mapped custom field.

WennSoft tracks technicians with employee records, skill certifications, and work order assignments. Pipedrive has no native technician object — users are identified by email. We match WennSoft technician employee IDs to Pipedrive users by email address. A Technican_ID__c custom field on each Deal preserves the original WennSoft technician reference for audit purposes.

WennSoft work orders contain line items: labor hours, parts used, materials, and other costs — each with its own cost element and billing rate. Pipedrive Deal has a single Amount field and no native line-item structure. We aggregate labor_cost + parts_cost + other_cost into the Deal.Amount value and store the cost element breakdown as custom fields (Labor_Cost__c, Parts_Cost__c, Other_Cost__c) for margin visibility.

WennSoft's Extended Pricing Matrix assigns billing rates and cost markups by call type, problem type, and equipment type. Pipedrive has no native price-list or pricing matrix. We create Billing_Rate__c, Labor_Rate__c, and Parts_Markup__c custom fields on the Deal. The admin applies these rates manually when generating invoices in Pipedrive.

WennSoft logs service call activities — dispatch calls, field updates, customer communications, and internal notes. Pipedrive Activities model tasks and events with type, subject, due date, and owner. We map email and phone call logs to Pipedrive Tasks with Type='Email' or Type='Call', meetings to Events with original start/end times, and notes to Pipedrive Notes. Original timestamps and owners are preserved.

WennSoft tracks unbilled labor and parts costs per work order via the Unbilled Costs report. Pipedrive has no native cost tracking. We create custom fields for unbilled labor (Unbilled_Labor__c) and unbilled parts (Unbilled_Parts__c) on the Deal. These values are reference-only in Pipedrive — actual invoicing must happen in the ERP or be managed manually by the admin.

Dynamics GP stores users and employees separately from Pipedrive's user model. We match GP employee email addresses to Pipedrive user accounts for owner resolution. Users without an email match in Pipedrive are flagged as unmatched_owners before migration — the admin either creates Pipedrive accounts or assigns their records to a fallback owner.