Migrate from Service Suite FSM to Pipedrive

Service Suite FSM persons and contacts migrate directly to Pipedrive Persons. The primary organization link uses FSM's Customer-Contact association, resolved to a Pipedrive Organization by name match before the person record is written. Email addresses are validated and deduplicated against existing Pipedrive Person records, and phone numbers are normalized to E.164 format during the migration to ensure consistent formatting in Pipedrive.

FSM Customers map to Pipedrive Organizations. Parent-company hierarchies use the FSM parent account field, mapped to Pipedrive's Organization owner_id for multi-level structures. Multi-contact customers are linked via Pipedrive's Organization-Person relationship. The migration validates domain names for organizational accounts and standardizes address formatting to Pipedrive's address field structure.

Work Orders map 1:1 to Pipedrive Deals. The FSM work order number becomes the deal name prefix. FSM work order status (New, In Progress, On Hold, Completed, Cancelled) is mapped to Pipedrive stage names per pipeline. Deal value carries over directly from the FSM estimated cost or invoice amount.

FSM Projects attach to their primary Customer record, which becomes the Pipedrive Organization. Project-level data (project name, project manager, project status) migrates as custom fields on the linked Organization record. The migration also validates that all referenced Customer records exist in Pipedrive before creating Project-Organization links, flagging any missing organizations for manual review to prevent orphaned data.

FSM Tasks and Work Order Tasks map to Pipedrive Activities — type='task' for standalone tasks, type='call' for phone activities, type='meeting' for on-site visits. Task status values (New, In Progress, Completed) are preserved as custom fields on the Activity since Pipedrive Activities lack a status pick-list equivalent to FSM's task lifecycle.

FSM Service Category is a taxonomy field on Work Orders with values like HVAC, Plumbing, Electrical. Pipedrive has no native service category — we create a custom pick-list field (Service_Category__c) on Deals and map each FSM value to a corresponding Pipedrive pick-list option.

FSM Assets track customer equipment, serial numbers, install dates, and service history. Pipedrive has no Asset object. Asset data is stored as a custom field (Asset_Record__c) on the Pipedrive Organization, containing serialized JSON with serial number, install date, and last service date for reference.

FSM technician assignments on Work Order Tasks have no Pipedrive equivalent — Pipedrive Activities are owned by the activity creator, not assigned to a technician. Technician name migrates as a custom text field (Technician_Name__c) on both the Deal and related Activities for service history continuity.

FSM products and parts catalog items map to Pipedrive Products with name, SKU, unit price, and unit description. Parts used on Work Orders create Pipedrive Deal-Product links (deal_products) with quantity and price from the FSM line items. The migration verifies SKU uniqueness across the product catalog and flags duplicate SKUs for resolution before inserting into Pipedrive.

FSM file attachments on Work Orders, Projects, and Customers are re-uploaded to Pipedrive's Files section and linked to the corresponding Person, Organization, or Deal record. Pipedrive enforces a 25MB per-file size limit — larger files are split or archived with a reference link.