Migrate from Trade Service Pro to Pipedrive

TSP customers map directly to Pipedrive Persons. Name, email, phone, address, and company association fields map to Person fields. TSP customers without an email receive a placeholder email (customer_[id]@placeholder.flitstack) to satisfy Pipedrive's uniqueness constraint. This mapping also preserves the original TSP customer ID as a custom field for future reference.

TSP stores company name as a property on the Customer object. In Pipedrive, the company becomes a separate Organization record, and the Person links via the Person's organization_id field. This requires creating the Organization first, then linking each Person. ensuring referential integrity across the dataset

TSP estimates and proposals map to Pipedrive Deals. Estimate amount becomes Deal value. Estimate status (draft, sent, accepted, declined) maps to a custom Deal stage or Pipedrive's built-in stage values. Multiple estimates per customer become multiple Deals linked to the same Person.

TSP invoices cannot map to a native Pipedrive billing object — Pipedrive has no invoice module. Invoice records are preserved as Activity Notes on the corresponding Deal, containing invoice number, amount, date, and status. For ongoing invoicing, Pipedrive integrates with QuickBooks or Xero post-migration.

TSP work orders have no Pipedrive equivalent. Work order fields (job type, technician, status, location, scheduled date) migrate as custom fields on the linked Deal. The Deal's Activity log records the work order history as timestamps. These custom fields are indexed for filtering, allowing you to report on job type and technician performance directly in Pipedrive.

TSP pricebook products and services map to Pipedrive Products. Product name, unit price, and unit description map directly. Products can be linked to Deals as line items via the Pipedrive ProductLinks API. Each product record also stores a reference to its TSP pricebook identifier, enabling traceability after migration.

TSP payment records have no Pipedrive equivalent. Payment records (transaction ID, amount, date, method) are preserved as Activity Notes on the linked Deal. Payment processing must be migrated to Pipedrive's integrated payment tools or an external processor post-migration. for accurate financial reporting

TSP user records map to Pipedrive users by email match. TSP technician and admin roles have no Pipedrive equivalent — these map to standard Pipedrive user roles (admin, manager, regular). Owner resolution is done before migration; unmatched owners are flagged for manual assignment.

TSP custom form fields capture industry-specific data (e.g., HVAC license number, insurance policy, property type). These require custom fields in Pipedrive on the relevant object (Person for customer attributes, Deal for job attributes). Field types are matched to Pipedrive's 16 supported custom field types.

TSP timesheet records (clock-in, clock-out, job timers) have no Pipedrive equivalent. Timesheet data is preserved as Activity Notes or Tasks on the related Deal for audit purposes, but Pipedrive does not support timesheet-native functionality. Post-migration, teams use dedicated time-tracking tools integrated via Zapier or native Pipedrive automations.

TSP scheduled jobs map to Pipedrive Activities. Appointment date, time, technician assignment, and location become a Pipedrive Event linked to the Deal and the assigned Person. Pipedrive's calendar sync with Google Calendar or Outlook can be configured post-migration to surface these events.

TSP files (photos, documents, signed forms) attached to customers, work orders, or estimates upload to Pipedrive's Files object. Files are linked to the corresponding Person, Organization, or Deal. File size limits follow Pipedrive's attachment constraints. Inline images in notes are re-hosted on Pipedrive's file storage.

TSP notes attached to customers or work orders map to Pipedrive Activity Notes on the corresponding Person or Deal. Original timestamps and author information are preserved as Note metadata. This preserves the full context of each note, enabling team members to review historical communication without accessing the legacy TSP system.

TSP integrations (e.g., QuickBooks sync, payment gateway connections) cannot migrate to Pipedrive. Each integration must be reconnected manually. FlitStack documents the integration list from TSP as a rebuild checklist for the Pipedrive admin. This checklist also includes OAuth scopes, API credentials, and any required field mappings for each external service.