Migrate from Field Force Tracker to Pipedrive

Field Force Tracker client records (name, email, phone, address) map directly to Pipedrive Person records. Primary contact email becomes the Person's email field; multiple phone numbers require custom fields or the primary phone field. If a client has multiple email addresses, we store the primary as the main email and place secondary addresses in a custom field for reference.

Field Force Tracker company-level client records map to Pipedrive Organization. Business address, industry classification, and employee count migrate as Organization fields. Client records without a company name land as standalone Persons. If a client record includes a parent‑company hierarchy, we preserve the top‑level organization and link subsidiary contacts to that Organization, maintaining the relationship structure.

Each Field Force Tracker work order becomes a Pipedrive Deal. Job description, status, and total invoice amount map to Deal fields. Work order ID is stored as Source_System_ID__c for traceability and delta-run deduplication. If the work order includes multiple line items or a parts breakdown, we store those as custom fields on the Deal to preserve detailed billing information.

Field Force Tracker job statuses (Scheduled, In Progress, Completed, Cancelled) map to Pipedrive deal stage values. We apply a value-by-value mapping plan before migration — you choose which stages exist in your Pipedrive pipeline. This mapping ensures that historical work order completion rates are reflected accurately in your deal stage distribution, supporting realistic pipeline reporting.

Field Force Tracker technicians are referenced in work orders but are not CRM contacts. We map technicians to inactive Pipedrive Users for assignment tracking, and optionally as Persons if your team tracks external contractor relationships. Inactive Users allow you to assign deals to technicians without granting them full CRM access, preserving data security while maintaining assignment records.

Field Force Tracker inventory items map to Pipedrive Products for quote and deal-line use. Stock levels, reorder points, and parts categories migrate as custom fields since Pipedrive's Products object lacks inventory management. These custom fields are populated at migration time and serve as static reference values; any subsequent inventory updates should be tracked outside Pipedrive or via a separate inventory system.

Field Force Tracker invoices and payment history have no Pipedrive equivalent. Invoice totals, payment status, and outstanding balance migrate as custom fields on the associated Deal. Full invoice PDFs are stored as file attachments. These custom fields capture the most recent invoice status and allow your sales team to view payment history directly within the Deal record, reducing the need to switch between systems.

Service contracts and agreement terms migrate as custom fields on the Organization record with contract dates, terms, and renewal reminders. Contract PDF attachments are linked to the Organization as files. Renewal reminders are set as custom date fields, enabling your team to receive alerts ahead of contract expiration and maintain proactive relationship management.

Field Force Tracker dispatch schedules and technician route data have no Pipedrive equivalent. We preserve schedule summary notes on the related Deal for historical reference but do not replicate the calendar structure. If your team relies on precise scheduling, consider using Pipedrive's calendar sync or an external scheduling tool to replicate dispatch functionality within your workflow.

Client equipment records in Field Force Tracker (make, model, install date, warranty status) map to custom fields on the Organization record. Multiple assets per client use a structured note format or custom field arrays. These equipment details support service history tracking, warranty validation, and proactive maintenance planning within your Pipedrive Organization view.

Field Force Tracker GPS tracking data is operational metadata with no Pipedrive equivalent. We do not migrate technician location history. Location-based client addresses migrate to Organization address fields. If address precision is critical, consider enriching Organization records with geocode data using a third-party enrichment service after migration.

Industry-specific job types (HVAC, plumbing, electrical) in Field Force Tracker migrate as custom pick-list fields on Pipedrive Deals. We create these fields before migration and map values value-by-value. These custom pick‑list fields can be used for filtering deals, building reports by service line, and triggering workflow automations based on the job category in Pipedrive.