Migrate from Mobile Worker to Pipedrive

Field workers who are also customer contacts map directly to Pipedrive Person records. Worker name, email, phone, and role fields transfer as Person standard fields. Workers who are internal (not customer-facing) map to Pipedrive Users and are resolved as deal owners rather than Person records.

Customer organizations from the source platform map to Pipedrive Organizations. Address, industry, employee count, and domain fields translate to Organization standard fields. Source location or site records attach as custom fields or multiple Organization addresses if the source supports multi-site customer records.

Work orders become Pipedrive Deals. Source status (Open, In Progress, Completed, Cancelled) maps to Pipedrive stage values per pipeline. Work-order priority, service type, and assigned technician fields migrate as custom fields on the Deal. Deal value may be populated from billing amount or left as zero if the source records no monetary value.

Each source work-order status value maps to a corresponding Pipedrive stage name within the target pipeline. Pipedrive's stage pick-list values are configured per pipeline. Stage-entered timestamps from the source migrate as custom datetime fields (e.g., Stage_Entered__c) for reporting continuity. If a source status has no direct Pipedrive match, the migration creates a custom stage name to preserve the original workflow state.

Pipedrive has no native asset registry. Asset IDs, serial numbers, and service history migrate as custom fields on Organization. High-value or billable assets can map to Pipedrive Products linked to Deals via deal_products. Your admin decides whether to use Products for asset billing or custom fields for asset reference.

Source location or site records attach to the corresponding Organization as additional addresses via Pipedrive's address sub-object. If the source tracks GPS coordinates, these migrate as custom lat/long numeric fields on the Organization for geo-routing reference. The migration also validates address format completeness and fills missing city or postal code with placeholders if needed.

Work-order task checklists, pre-visit steps, and post-job sign-offs map to Pipedrive Activities of type 'task'. Original due dates, completion timestamps, and assigned worker (resolved as Pipedrive User) are preserved. Task subjects carry the source checklist item name for traceability. If a task lacks a due date, the migration assigns a default date derived from the related work-order schedule.

Scheduled or completed site visits migrate as Pipedrive Activities of type 'meeting' with start/end times preserved. If the source records visits as tasks without duration, they migrate as 'task' type Activities. Owner resolves to the Pipedrive User representing the field worker who performed the visit.

Service notes attached to work orders become Pipedrive Notes linked to the corresponding Deal. Original create timestamps and author (resolved as Pipedrive User) are preserved. If notes contain attachments, files are re-uploaded to Pipedrive and linked by reference. If a note is empty or contains only whitespace, it is still migrated as a blank note to preserve the record timeline.

Source custom objects (worker certifications, inspection results) that cannot map to a standard Pipedrive object become custom fields on the nearest entity. Certification expiry dates migrate as date fields; inspection pass/fail values migrate as dropdown or checkbox fields on the related Organization or Deal.

Photos, signed forms, and documents attached to work orders or assets re-upload to Pipedrive as Files attached to the target record. Pipedrive's file storage limits apply (plan-dependent). Inline images in notes are extracted and rehosted as standalone file attachments. If a file exceeds Pipedrive's size limit, the migration logs a warning and recommends manual upload via the Pipedrive UI.

Source users who performed work orders are resolved by email match against Pipedrive Users. Unmatched users are flagged before migration — your team either creates Pipedrive user accounts first or assigns their records to a fallback owner. No record lands without a valid Pipedrive User or default owner.