Migrate from Fieldproxy to Pipedrive

Fieldproxy contacts map directly to Pipedrive People using a one-to-one field correspondence. Core contact fields including email address, phone number, and physical address migrate as-is without transformation. The primary company association from Fieldproxy becomes the Organization link in Pipedrive's Person record, establishing the relationship between contacts and their employer. If a contact record in Fieldproxy has no associated company, it imports as an unlinked Person record in Pipedrive without organizational affiliation.

Fieldproxy companies map to Pipedrive Organizations through a direct field-to-field translation. The company name, domain/website, industry classification, employee count estimate, and address components (street, city, state, zip, country) migrate as standard Organization fields in Pipedrive. Parent-child hierarchical relationships between companies in Fieldproxy are preserved by mapping them to Pipedrive's Owner's organization link or the organization hierarchy feature if that structure exists in your Pipedrive account.

Fieldproxy job records are the core transformation object. Job title becomes Deal name. Job status (scheduled, in-progress, completed, cancelled) maps to Pipedrive Deal stage via a configurable status-to-stage mapping table. Job value or quoted amount maps to Deal value if present.

Fieldproxy job line items (parts, labor) migrate to Pipedrive Deal Products. Each line item becomes a product entry on the Deal. Pricing, quantity, and description carry over. Products must exist in Pipedrive's product catalog first or get created during migration.

Fieldproxy technician records map to Pipedrive Users through email address resolution as the primary matching key. Active technicians who are currently working in Fieldproxy become active Users in Pipedrive with full platform access. Inactive or archived technicians from Fieldproxy become Pipedrive Users with inactive status, preserving the historical assignment context for reporting purposes without consuming a paid Pipedrive seat if your admin chooses that configuration.

The technician assigned to a Fieldproxy job becomes the Owner of the corresponding Pipedrive Deal after migration. Owner resolution relies on email address matching against the existing Pipedrive Users list. Technicians from Fieldproxy whose email addresses do not match any Pipedrive User are flagged in the pre-migration audit and assigned to a configurable fallback owner before the migration run commits to prevent orphaned deals.

Fieldproxy's activity log entries including call logs, site visit notes, status updates, and internal communications migrate to Pipedrive Activities as a direct record transfer. The activity type in Fieldproxy determines the Pipedrive activity kind (call, meeting, or task). Original creation timestamps and the activity owner's user ID are preserved and populated into Pipedrive's activity record fields during import.

Fieldproxy notes attached to jobs, contacts, or companies migrate to Pipedrive Notes with preservation of the attachment relationship. Notes are associated with the corresponding Person, Organization, or Deal record in Pipedrive based on the parent object reference in Fieldproxy. Rich-text formatting exported as HTML from Fieldproxy is preserved in Pipedrive's HTML note format; plain-text fallback applies automatically for notes that contain no formatting markup.

Fieldproxy file attachments including job photos, customer signatures, and invoice PDFs that have accessible URLs are downloaded from Fieldproxy's storage and re-uploaded to Pipedrive Files, then programmatically linked to the parent Deal, Person, or Organization record. Files exceeding Pipedrive's 25MB per-file limit are identified in the pre-migration audit and flagged for manual re-upload or Google Drive integration linking after the migration completes.

Fieldproxy custom fields defined on job records, such as service_type, site_location, and equipment_id, require pre-creation as Pipedrive custom deal fields before migration execution. FlitStack analyzes Fieldproxy's custom field definitions including data types and pick-list values, then generates a Pipedrive field creation script that your admin runs to provision the corresponding fields using Pipedrive's REST API or manual field editor.

Fieldproxy custom contact fields such as preferred_service_area and contract_type migrate to Pipedrive custom person fields. The mapping handles field type equivalence: pick-list fields become Pipedrive pick-list fields, text fields become text fields, number fields become number fields, and date fields become date fields. Multi-select fields from Fieldproxy that allow multiple chosen values map to Pipedrive's multi-option field type to preserve all selected values.

Fieldproxy AI-powered workflows including dispatch rules, scheduling automations, parts replenishment triggers, and customer notification workflows have no direct equivalent in Pipedrive's feature set. These automation definitions must be rebuilt using Pipedrive's Automation builder or exported as JSON definitions for a Pipedrive-certified implementation partner to recreate. FlitStack exports all workflow definitions as JSON reference documentation included in the pre-migration deliverable package.