Migrate from ServiceTracker to Pipedrive

ServiceTracker Customer is a combined record with company details, primary contact, and billing address. FlitStack AI splits this into a Pipedrive Organization (company name, domain, industry, address fields) and a Person record (contact name, email, phone, job title) linked via the organization's ID. The primary contact becomes the Person; secondary contacts require additional Person records.

ServiceTracker Work Orders have no direct Pipedrive equivalent — Pipedrive deals track revenue opportunities, not service tasks. Each work order maps to a Pipedrive Deal with the deal name derived from the work order number and customer. Activities (service visits, parts installed, sign-offs) migrate as linked Pipedrive Activities (calls, tasks, meetings) attached to the deal. Original work order status and priority move to custom fields.

ServiceTracker Assets (equipment, serial numbers, location, warranty status) have no Pipedrive native equivalent. FlitStack AI migrates asset data as custom fields on the Organization record — fields include ST_Asset_Name__c, ST_Serial_Number__c, ST_Asset_Location__c, ST_Warranty_Expiry__c, and ST_Last_Service_Date__c. Asset service history attaches as Activities to the Organization.

ServiceTracker Contracts (SLA terms, start/end dates, renewal flags) have no Pipedrive equivalent. Contract dates migrate as custom datetime fields on both the Organization (ST_Contract_Start__c, ST_Contract_End__c) and the linked Deal (ST_SLA_Tier__c, ST_Renewal_Date__c). Active contract flags are stored as custom pick-list fields. Renewal alerts require Pipedrive automation rules to be built post-migration.

ServiceTracker Technicians are internal staff not represented in Pipedrive's People/Organization model. FlitStack AI resolves technicians by email match against Pipedrive Users — matched technicians become the deal owner or get assigned via a custom ST_Technician__c field on the deal. If no Pipedrive User exists for the technician email, the assignment is stored as a custom text field and flagged for admin review.

Work order notes migrate to Pipedrive Deal Notes (rich text preserved). File attachments (photos, signed forms, invoices) re-upload to Pipedrive Files attached to the corresponding deal. File size limits of 25MB per file apply. Inline images in notes are downloaded and re-hosted in Pipedrive's file storage.

ServiceTracker's work order activity log (status changes, technician check-ins, parts added) translates to Pipedrive Activities — each log entry becomes a Task or Event with original timestamp, technician owner, and a note describing the event. Activities are linked to the deal via deal_id so the full service timeline is visible in the deal's Activity tab.

ServiceTracker Invoices (amount, status, payment date) have no Pipedrive billing equivalent. Invoice amount may map to Deal.Amount if the work order is billable. Invoice status (paid, overdue, pending) migrates as a custom pick-list field (ST_Invoice_Status__c). Full invoice documents are stored as Pipedrive Files attached to the deal.

ServiceTracker Locations (service site addresses, GPS coordinates) map to Organization address fields in Pipedrive — Street, City, State, Postal Code, Country. GPS coordinates are stored in a custom text field (ST_GPS_Coordinates__c) for reference. Multiple service sites per customer become multiple Organization records or are consolidated as address lines on the primary Organization.

ServiceTracker custom fields (rate types, billing codes, client-specific attributes) require pre-creation in Pipedrive before migration. FlitStack AI creates the custom field via Pipedrive's POST /dealFields or POST /organizationFields API endpoint and captures the hash key returned. Source field values map to the new Pipedrive custom field by hash key. Pipedrive's field-type restrictions apply — if a custom field type changes after creation, the field must be recreated and data re-imported.