Migrate from Field Service Trakker to Pipedrive

Field Service Trakker stores customer name, company, phone, email, and address on a single Customer record. We split this into Pipedrive: Organization record holds company-level fields (name, domain, address), and a Person record holds contact-level fields (name, email, phone, title). Both are linked via the Organization-Person relationship.

Each Field Service Trakker Work Order migrates as a Pipedrive Deal. The deal name is set to the work order number or customer-plus-site reference. Pipeline and stage are mapped from the work order status (e.g., 'Scheduled' → 'Open', 'Completed' → 'Won'). Custom fields on the work order (service type, priority, parts used) migrate as Pipedrive Deal custom fields.

Completed service visits and job summaries from Field Service Trakker become Pipedrive Activities (type='task') with the service description as the subject and the technician's notes as the body. Timestamps and owner assignments are preserved. Inline attachments are re-uploaded to Pipedrive Files.

Field Service Trakker stores multiple service locations per customer. Pipedrive Organizations hold one primary address. Secondary locations are preserved as Organization custom fields (e.g., Location_2_Address__c, Location_3_Address__c) or as separate Organization records flagged as secondary sites — your team chooses the approach before migration.

Pipedrive Users are matched to Field Service Trakker technicians by email. If a technician has no email in the source, FlitStack creates a placeholder User record or assigns their records to a fallback owner. Pipedrive User permissions and visibility groups must be configured manually after migration.

Field Service Trakker equipment records (make, model, serial number, installation date) have no native Pipedrive equivalent. We migrate them as Organization-level custom fields or as Pipedrive Products linked to the deal — your admin decides the preferred layout before migration runs.

Service agreement terms (contract start/end date, SLA tier, billing frequency) migrate as custom fields on the Deal. Pipedrive has no native contract management object. If contract documents exist as attachments, they re-upload to Pipedrive Files linked to the associated Organization.

Field Service Trakker invoices and payment history have no direct Pipedrive object. We migrate invoice metadata — such as invoice number, amount, date, and payment status — as a Note attached to the Organization record, and we optionally store the invoice ID in a custom text field for quick lookup. Supporting PDF invoices are re‑uploaded as Pipedrive Files linked to the same Organization. Ongoing financial reconciliation should be performed in an accounting system after migration.

Parts and inventory items in Field Service Trakker map to Pipedrive Products, preserving unit price, description, SKU, and cost or stock data. Products can be linked to Deals via the deal‑product association, giving Pipedrive users visibility into service parts on each deal, and allowing the same product to appear across multiple deals for recurring service scenarios. We map them to Pipedrive Product Categories to keep reporting tidy.

Field Service Trakker custom objects vary per account. We map each to Pipedrive Organization-level or Deal-level custom fields with matching types (text, number, date, dropdown). If a custom object has a one-to-many relationship (e.g., multiple inspections per work order), we preserve it as a comma-separated value list in a custom field.

Field Service Trakker tags — such as service category, technician skill tag, and region — migrate as Pipedrive Organization Tags, enabling segmentation and filtered reporting across accounts. Tags attached to individual contacts are transferred as Person Tags, maintaining contact-level categorization. Pipedrive's tag system is flat, so nested hierarchies from the source are flattened into single-level tags, and your team may choose to simulate hierarchy by using naming conventions or prefix patterns.

Field Service Trakker estimates map to Pipedrive Deals, storing the estimate number, estimated value, and any expiry date as custom fields on the Deal, while the line‑item products are linked via the deal‑product association. The estimate status (accepted, rejected, revised) is mapped to the corresponding Pipedrive deal stage, and any discount or tax information is preserved in additional custom fields to keep the full pricing context in Pipedrive.