Migrate from WorkBuddy to Pipedrive

WorkBuddy customer records map to Pipedrive Persons with direct field translation for name, email, phone, and address. The primary organization link (company association) is resolved by creating the Organization record in Pipedrive first, then linking it via the Person.org_id field to maintain referential integrity between Person and Organization objects.

WorkBuddy company records map to Pipedrive Organizations. Business name, domain/website, industry, and address fields map directly. Employee count and annual revenue are optional fields — mapped when present. Parent-company hierarchy (if used in WorkBuddy) becomes a custom Organization field for reference.

WorkBuddy jobs map to Pipedrive Deals in a dedicated 'Jobs' pipeline. Job title becomes Deal name. Job value (estimated quote or fixed price) maps to Deal amount. Job status (scheduled, in-progress, completed, invoiced) maps to a custom Job_Status__c field and a separate Deal stage value within the Jobs pipeline.

WorkBuddy job priority values (low, medium, high, urgent) map to a custom pick-list field on Pipedrive Deals. Value-by-value mapping ensures no priority classification is lost. If WorkBuddy uses numeric priority scores, they map to the nearest label or a custom numeric field.

WorkBuddy job type and category become custom fields in Pipedrive Deals since Pipedrive has no native job-category concept. We create a custom pick-list field matching WorkBuddy's type values with value-by-value translation. Multi-type assignments (if WorkBuddy allows multiple categories per job) are stored as comma-separated text in Pipedrive to preserve all associated category information.

If the WorkBuddy job site is tied to a customer or company, the address migrates to the Organization's address fields. The specific site reference (unit number, floor, building) migrates as a custom Deal field. This preserves site-level context even when the Organization address is the primary billing address.

WorkBuddy's scheduled job completion date maps directly to Pipedrive's Deal close_date field, serving as the natural anchor for pipeline-stage forecasting. Historical jobs retain their original completion dates from WorkBuddy, while open jobs populate future close dates. This date field drives deal aging reports and stage-overdue alerts in Pipedrive.

WorkBuddy technician assignments resolve to Pipedrive users by email address matching. Any unmatched technicians are flagged in the pre-migration report — your team either invites them to Pipedrive or assigns records to a fallback owner. This ensures no Deal lands in Pipedrive without a valid owner assigned, preventing orphaned record issues post-migration.

Pipedrive has no native asset management object. WorkBuddy asset records (equipment, serial numbers, maintenance history) are preserved as custom text fields on the related Organization or Deal — asset ID and short description only. Full maintenance history requires a separate asset management tool.

WorkBuddy activities (calls logged, emails sent, tasks completed) map to Pipedrive Activities. Activity type, subject, timestamp, and owner resolve by email match. Activities link to the relevant Deal or Person in Pipedrive by looking up the WorkBuddy job or customer ID preserved on the destination record.

WorkBuddy job notes and comments migrate as Pipedrive Notes attached to the corresponding Deal. The original author name and timestamp are preserved in the Note body for audit continuity and traceability. Rich-text formatting from WorkBuddy is simplified to plain text in Pipedrive Notes to ensure compatibility across all Pipedrive interface views.

WorkBuddy file attachments on jobs or customers are re-uploaded to Pipedrive Files linked to the corresponding Deal or Person record. Standard Pipedrive file size limits apply by plan tier (default 100MB per file). Inline images embedded in WorkBuddy notes are extracted, downloaded locally, and rehosted as Pipedrive Files to preserve visual documentation.

WorkBuddy custom properties map to Pipedrive custom fields. Field type conversion is applied: dates stay dates, numeric fields stay numeric, pick-lists become Pipedrive pick-lists. Multi-select values are stored as comma-separated text. The Pipedrive custom field key (hash) is captured in the mapping plan for reference.

WorkBuddy users and technicians are matched to existing Pipedrive users by email address. If a WorkBuddy user does not have a Pipedrive account, they are added to a 'WorkBuddy Migrated Users' list for your admin to create before the final migration run.