Migrate from Trade Service Pro to HubSpot

TSP customers map directly to HubSpot Contacts (person-level records) and HubSpot Companies (business-level records). When a TSP customer record has an associated business name, we create both a Contact and a Company and link them via the Company Association. TSP customer notes and custom fields migrate as HubSpot contact properties and custom properties respectively.

TSP estimates and proposals map to HubSpot Deals. The estimate name becomes the Deal name, the estimated value becomes Deal Amount, and the TSP status (Pending, Sent, Accepted, Declined) maps to a configured HubSpot pipeline stage. We preserve the original estimate create date and TSP estimate ID for traceability.

TSP work orders have no HubSpot native equivalent — they migrate as a custom object named Work_Order__c under HubSpot Enterprise or Service Hub Starter. The custom object stores work order number, status, type, service address, assigned technician, scheduled date, and line items for materials and labor. The TSP customer and contact link as lookup associations in HubSpot.

TSP scheduling records track technician, job date and time, duration, job type, and job address. We create a Schedule__c custom object in HubSpot to hold these records with the same field structure. The schedule links to the associated Work_Order__c custom object and the Contact record for the customer being served.

TSP line items on estimates — service descriptions, quantities, unit prices, and tax — migrate as HubSpot Deal Line Items attached to the corresponding Deal. The line-item name, quantity, and unit price map directly. HubSpot supports line items on Deals at all Sales Hub tiers.

TSP invoices carry invoice number, total amount, payment status, and payment method. Since HubSpot has no native invoice object in the CRM layer, we create an Invoice__c custom object preserving invoice number, contact association, line items, total, status, and payment date. Payment status migrates as a pick-list custom property.

TSP intake forms captured lead source, service type, job size, and urgency. We create an Intake__c custom object in HubSpot that stores the form name, submission date, associated contact, and key intake field values as custom properties. The intake record links to the contact created from the lead record.

TSP activity records — phone calls, notes, and messages attached to customers or work orders — map to HubSpot Engagements. Calls become HubSpot Calls with subject, body, and duration. Notes become HubSpot Notes attached to the relevant Contact or Deal. Original timestamps and the technician or user who logged the activity are preserved.

TSP user and technician accounts map to HubSpot Users by email address. TSP user names become HubSpot user full names. TSP user roles and permissions do not migrate — HubSpot roles and permissions are configured separately in HubSpot Settings under Users & Teams.

TSP service catalog entries — service name, description, and standard rate — migrate as HubSpot Products. When TSP line items reference a pricebook entry, we link the HubSpot Deal Line Item to the corresponding HubSpot Product by name match. Unit prices and quantities map directly from the pricebook entry to the line item.

TSP timesheet entries track clock-in, clock-out, break duration, and total hours per technician per day. We create a Timesheet__c custom object in HubSpot linked to the TSP technician's HubSpot User record and the associated Work_Order__c or Schedule__c custom object. Total labor cost and labor rate fields preserve the financial context.

TSP automations (dispatch triggers, payment reminders, status-change notifications) do not migrate to HubSpot. We export a structured reference document listing each TSP workflow's trigger, condition, and action so your HubSpot admin can rebuild equivalent automations in HubSpot's Automation or Breeze tools. This is manual work outside the data migration scope.