Migrate from FieldFX to Pipedrive

FieldFX Job is the parent record for work orders and tickets. The Job name becomes the Pipedrive Deal name, Job total amount maps to deal value, and Job status (Pending, In Progress, Completed) maps to Pipedrive stage values. Original Job create date is preserved in a custom datetime field since Pipedrive's created_at is migration-set.

FieldFX Work Orders are linked to Jobs and contain line items, labor hours, and work type. Each Work Order becomes a Pipedrive Deal with the Work Order number stored in a custom field, work order status mapped to a deal stage, and labor/total amounts aggregated into the deal value. Work Order Line Items map to Pipedrive Deal Products. Multiple work orders per Job create multiple Pipedrive Deals linked to the same Organization.

FieldFX Tickets are support or service records attached to a Work Order or Job. Ticket records migrate as Pipedrive Activities of type 'task' with the ticket subject as the activity subject, ticket status mapped to Pipedrive activity priority, and ticket description stored in the activity note. Original ticket number stored in a custom activity field.

FieldFX Customer records sit on the Salesforce Account object. Customer name maps to Pipedrive Organization name, industry maps to Pipedrive industry (value-by-value for standard values, custom for non-matching), and address fields map to Pipedrive address fields. Parent-child customer hierarchies in FieldFX map to Pipedrive Organization hierarchy.

FieldFX Contact records map directly to Pipedrive Person. First name, last name, email, phone, mobile phone, and job title map field-for-field. The Contact's primary Customer (Account) lookup becomes the Pipedrive Person's linked Organization. Multiple contacts per customer map to multiple Pipedrive Persons under the same Organization.

Pipedrive has no native Asset object. FieldFX Asset records — equipment name, serial number, install date, warranty expiry — migrate as custom fields on the linked Pipedrive Organization. Asset status (Active, Under Maintenance, Retired) maps to a custom pick-list field. Multiple assets per customer become repeating custom field values or a structured text block.

FieldFX Work Order Line Items contain part number, description, quantity, and line amount. Each line item becomes a Pipedrive Deal Product entry linked to the destination Deal. Product name and description map from the line item; quantity and unit price are set from the line item fields. Tax and discount handling follows Pipedrive's product pricing model.

FieldFX work order status values (e.g., Unscheduled, Scheduled, En Route, In Progress, On Hold, Completed, Cancelled) require value-by-value mapping to Pipedrive stage names. The mapping is defined during the pre-migration schema review. Probability and forecast category are re-applied based on Pipedrive's stage configuration.

FieldFX custom objects and their fields migrate as Pipedrive custom fields on the nearest equivalent object (Deal, Person, or Organization). N:N relationships in FieldFX require flattening in Pipedrive since junction objects are not available — the migration plan surfaces these cases for your team to choose between a custom text block or activity log approach.

FieldFX owner assignments on Job, Work Order, Ticket, and Contact map to Pipedrive User by email match. Unmatched owners are flagged before migration — your team either invites them to Pipedrive or assigns their records to a fallback user. This is the only owner resolution mechanism; FieldFX role-based assignments do not map to Pipedrive's visibility group model.

FieldFX records technician calls, emails, and meetings linked to Work Orders or Tickets. These map directly to Pipedrive Activities — call type = 'call', email type = 'email', meeting type = 'meeting' — with original timestamps and owners preserved. Call recordings do not export due to Pipedrive API restrictions. Email exports are limited to records from active users who have shared their email data.

Pipedrive does not have a native file attachment object. FieldFX file attachments on Work Orders or Tickets are preserved by downloading and re-uploading to Pipedrive's activity notes or linking via URL in a custom field. Large files (over Pipedrive's per-file limit) require alternative storage with the link recorded in Pipedrive.