Migrate from Affinity Fieldreach to Pipedrive

Affinity Person records (first name, last name, email, phone, job title) map directly to Pipedrive Person records. Primary email address resolves as the unique identifier for de-duplication during import. Affinity Person custom properties migrate as Pipedrive custom fields using the hash-key reference system.

Affinity Organization records (company name, domain, industry, employee count) map to Pipedrive Organization records. Multi-location organizations in Affinity require splitting into one primary Organization with additional addresses stored as custom fields on the primary record or linked via Pipedrive's address composite field.

Affinity Work Orders map to Pipedrive Deals. The Affinity work-order name becomes the Deal name; work-order status (Open, In Progress, Completed) maps to Pipedrive deal stage values. Custom fields on the work order (priority, job type, dispatch method, estimated duration) migrate as Pipedrive Deal custom fields. Original work-order create date preserved as a custom datetime field for audit continuity.

Affinity work-order activities (technician check-ins, site visits, job-completion logs) map to Pipedrive Activities. Completed visits become Pipedrive completed meetings with the technician name as the activity owner and original timestamp preserved. Affinity's multi-step job history surfaces as a chain of linked activities on the corresponding Deal.

Affinity field-worker records resolve to Pipedrive Users by email match. Workers with recognized email addresses become Pipedrive Users and receive the Deal owner assignment. Workers without matching Pipedrive user emails land as Person records with a custom 'Field Worker Origin' flag so admins can decide whether to invite them as system users or keep records as contact references.

Affinity Asset records (equipment name, serial number, warranty expiration, maintenance schedule) migrate as Pipedrive Products. Serial numbers and warranty dates become custom fields on the Product. Active maintenance schedules do not translate to Pipedrive's task system natively — they are preserved as custom date fields and surfaced as a rebuild reference for Pipedrive automations or a connected maintenance tool.

Affinity Service Location records (street address, city, region, postal code, location notes) merge into the linked Organization's address composite in Pipedrive. Multiple service locations per customer collapse to one primary Organization address, with secondary locations stored as custom address fields (Location 2, Location 3) or linked notes for dispatch reference.

Affinity custom fields on Work Orders (such as job category, service type, on-site requirements, customer sign-off) require creation of corresponding Pipedrive Deal custom fields. Field type mapping: Affinity text fields map to Pipedrive varchar; Affinity date fields map to Pipedrive date; Affinity pick-list fields map to Pipedrive set options with value-by-value mapping where source values differ from Pipedrive's defaults.

Files attached to Affinity Work Orders (photos, signed forms, inspection reports) re-upload to Pipedrive Activity records as attachments linked to the corresponding Deal. File size limit is Pipedrive's 100MB per file. Inline images from Affinity job notes download and rehost to maintain visual context in Pipedrive.

Affinity dispatch rules, scheduling constraints, and SLA timer automations have no native equivalent in Pipedrive's automation engine, which triggers on CRM object events rather than field-dispatch workflows. FlitStack exports Affinity automation definitions as JSON and delivers a rebuild playbook mapping each rule to Pipedrive Workflow Automations or a third-party scheduling integration.

Affinity list fields with predefined options (such as job priority: Low, Medium, High, Critical) map to Pipedrive set-type custom fields with corresponding options. Option order and color coding are not preserved — these require manual reconfiguration in Pipedrive's field settings after migration.

Affinity's internal record IDs are stored on migrated Pipedrive records as a custom text field named Source_System_ID__c for traceability, cross-reference, and delta-run de-duplication. This prevents duplicate record creation if the migration runs multiple times against the same source data. The source system ID also enables post-migration audit trails, rollback operations, and integration mapping back to the original Affinity records.