Migrate from Connect Field Service to Pipedrive

Connect Field Service Contact maps directly to Pipedrive Person. Salesforce Contact.Name splits into Person.name (display name). Email, phone, and title transfer directly without transformation. The Salesforce AccountId lookup resolves to a Pipedrive Organization link during migration via the pre-built ID mapping table, ensuring each Person is associated with the correct Organization in the destination CRM.

Salesforce Account maps 1:1 to Pipedrive Organization. Account.Name becomes Organization.name. Billing address, shipping address, industry, and annual revenue migrate as standard Organization fields or custom fields based on whether Pipedrive has native equivalents. For fields without native support, we create custom fields during the pre-migration schema setup to preserve all relevant account data.

Salesforce Lead maps to Pipedrive Lead. All standard fields — Name, Company, Email, Phone, Status, LeadSource — transfer directly without transformation. Custom fields on Salesforce Lead migrate as Pipedrive Lead custom fields created during the pre-migration schema setup, ensuring that any extended lead data captured in Connect Field Service is preserved in the destination CRM.

WorkOrder is the primary FSL object with no Pipedrive equivalent, so it maps to Pipedrive Deal using a 1:1 transform. FSL-specific fields (Status, Priority, WorkType, ServiceTerritory, FSL__SchedulingPriority__c) migrate as custom Deal fields. The Deal title is constructed from WorkOrder.OrderNumber or a concatenation of Account name + work type.

Each WorkOrderLineItem row is a parts-or-labour line on a work order. In Pipedrive Deals, line items do not exist as sub-objects — we merge line item data into a serialized JSON custom field (Line_Items__c) on the parent Deal, or flatten the primary line item's description and quantity into Deal custom fields.

ServiceAppointment maps to Pipedrive Activity. The appointment's ScheduledStartTime becomes the Activity due date, Duration becomes the time estimate, and Status (None/Scheduled/Dispatched/Completed/Cancelled) migrates as a custom Activity field. ParentWorkOrderId links the activity to the corresponding Pipedrive Deal via the pre-built ID mapping table that translates Salesforce WorkOrder IDs to Pipedrive Deal IDs.

BookableResourceBooking tracks technician assignment and duration against a work order — Pipedrive has no equivalent resource-booking object. We preserve the full booking record as a JSON custom field (Resource_Bookings__c) on the related Deal, enabling post-migration reference even though Pipedrive cannot schedule from it natively.

Skill requirements attached to service resources or work orders have no Pipedrive equivalent. We create custom fields on the relevant Pipedrive Person or Deal — Skill_Requirements__c as a text field — holding comma-separated skill labels from Salesforce for reference and rebuild guidance.

ServiceTerritory defines geographic dispatch zones in Connect Field Service, controlling which technicians are assigned to work orders in specific regions. Pipedrive Organizations can store geographic data in custom fields; we map the primary territory name and region code to a Territory__c custom field on the Organization for territory-based filtering, routing, and reporting within Pipedrive after migration.

WorkType controls billing rates and duration estimates per job category. Since Pipedrive Deals have no native work-type field, we create a Work_Type__c custom pick-list on Deal and map each Salesforce WorkType.Name value to the corresponding Pipedrive pick-list option. Rate and duration fields from WorkType migrate as custom numeric fields on the Deal.

Files attached to WorkOrder or ServiceAppointment (photos, signatures, PDFs) are downloaded from Salesforce and re-uploaded to the corresponding Pipedrive Deal or Person as native Pipedrive attachments. Files are associated by matching the Salesforce parent record ID to the migrated Pipedrive record.

Salesforce User records map to Pipedrive Users by email address match. All WorkOrder, ServiceAppointment, and Contact owners are resolved against Pipedrive Users before migration. Unmatched owners are flagged and assigned to a fallback Pipedrive user or created as pending invitations.