Migrate from Field Nexus to Pipedrive

Field Nexus customers map 1:1 to Pipedrive Persons. Each customer record transfers as a Person with name, email, phone, and address fields populated. Customers with multiple service locations: the primary location becomes the Person address; additional locations migrate as custom fields on the Person record.

Field Nexus companies map to Pipedrive Organizations. Company name becomes Organization name, domain becomes website. Industry and employee count migrate to Organization custom fields since Pipedrive Organizations do not have native industry or headcount fields. Including sector classification and workforce size that your team can reference on each Organization record.

Field Nexus work orders are the migration's central object. Each work order becomes a Pipedrive Deal. The work order status (e.g., Scheduled, In Progress, Completed, Cancelled) becomes a Pipedrive deal stage. We create Pipedrive deal stages that mirror your Field Nexus work order statuses. Work order value or estimated price maps to Deal value.

Each Field Nexus work order status (e.g., Quoted, Scheduled, Dispatched, Completed, On Hold) maps to a corresponding Pipedrive deal stage we create in your Pipedrive account. Stage probability and forecast category are applied per stage based on your historical close rates from Field Nexus.

Field Nexus technician names and IDs are preserved as custom fields on the Deal and Activity records where they appear, not as Pipedrive Users. Technician-to-user email matching is attempted so the Activity owner resolves to a Pipedrive User where an email match exists. Scheduling assignment data (which technician was booked for a given work order) migrates as a custom field.

Field Nexus service history entries — completed visits, notes, technician check-ins — migrate as Pipedrive Activities with original timestamps and owners preserved. Activity type maps to Pipedrive Activity type (Call, Meeting, Task, Note). Service description and outcome are stored in the Activity subject and details fields.

Field Nexus supports multiple service addresses per customer. Pipedrive Organizations have one primary address field. We create custom fields (Service_Location_2__c, Service_Location_3__c, etc.) on the Organization or Person record to hold additional addresses. Address labels from Field Nexus (e.g., Primary, Billing, Job Site) map to custom field names.

Field Nexus estimates split into two Pipedrive records: open estimates with monetary value become Deals (with a Won/Lost stage reflecting acceptance), and rejected or historical estimates become Activities for reference. Estimate line items migrate as custom fields on the Deal (item count, unit price, total) or as Activity details.

Field Nexus custom fields on work orders — service type, priority level, dispatch zone, equipment used — are created as Pipedrive custom fields on the Deal object before migration. Field types are matched (pick-list, number, date, text) using Pipedrive's 16 field types. Custom field API keys are retrieved from Pipedrive post-creation for mapping.

Field Nexus job photos, signatures, and documents attached to work orders are downloaded and re-uploaded to Pipedrive Files, linked to the corresponding Deal record. File size limits apply: Pipedrive's file size limits per plan govern re-upload. We handle inline images from Field Nexus notes by downloading and rehosting.

Field Nexus automations — dispatch rules, customer notification triggers, scheduling auto-assignment — are field-service-specific and have no Pipedrive equivalent. FlitStack does not migrate automations. We export your automation definitions as a rebuild reference for your Pipedrive admin. To assist in recreating workflows in Pipedrive's Automation platform.

Field Nexus integrations (calendar sync, accounting software, payment processors, GPS/routing tools) cannot migrate to Pipedrive. Pipedrive's integrations are CRM-focused (Slack, Zapier, email). Each integration must be evaluated and rebuilt separately after go-live. Including calendar synchronization, accounting, payment processing, and routing services that need to be reconnected post-migration.