Migrate from Service Buddy to Pipedrive

Service Buddy customers map to Pipedrive People. The customer name splits into first_name and last_name on the Person record. Email, phone, and address fields map directly. Service Buddy's custom fields for flooring-specific notes become Pipedrive custom fields on the Person record.

Service Buddy stores one primary company per customer profile. We map that as the Organization record linked to the Person via the Person's organization_id field. Service Buddy's multi-location stores map as separate Organization records with a parent-child relationship preserved using Pipedrive's org hierarchy.

Service Buddy quotes become Pipedrive Deals. The quote status (Draft, Sent, Accepted, Expired, Declined) is preserved in a custom Deal field (quote_status__c) and mapped to Pipedrive stage. Quote open date maps to Deal add_time; quote expiry date maps to close_date. Line items and product references migrate as Deal Products.

Service Buddy jobs and quotes are related but separate records. Both merge into a single Pipedrive Deal: the quote fields populate the Deal record, and the job's scheduling and crew data are preserved as custom fields on that same Deal. Job status (Scheduled, In Progress, Completed, Cancelled) maps to Deal stage.

Service Buddy tracks deposit paid, remaining balance, and BuddyPay status per quote or job. These become custom fields on the Pipedrive Deal: deposit_paid__c (currency), remaining_balance__c (currency), and buddypay_status__c (string). Pipedrive has no native multi-payment record; payment history is reconstructed from Activity notes linked to the Deal.

Service Buddy inventory items with name, SKU, price, and stock count map to Pipedrive Products. QR codes and warehouse locations cannot be stored on Pipedrive Products natively — we create custom fields product_qr_code__c and warehouse_location__c on the Product record during setup. Fulfillment status tied to specific jobs does not transfer.

Service Buddy staff members are matched to Pipedrive users by email address. Unmatched owners are flagged before migration — your team either creates the Pipedrive user first or assigns records to a fallback user. This prevents orphaned records with no activity owner in Pipedrive.

Service Buddy job activities — calls, emails, meetings, and internal notes — map to Pipedrive Activities. Each Activity is linked to the Deal that resulted from the Job. Original timestamps, subject lines, and assigned crew members are preserved. Job-specific scheduling details that don't fit a standard Activity field become custom Activity fields.

Service Buddy files attached to customers, quotes, or jobs are downloaded and re-uploaded to Pipedrive Files. Each file is linked to the corresponding Person, Organization, or Deal record. File size limits apply per Pipedrive plan. Inline images in notes are extracted and rehosted as separate files.

Service Buddy's industry-specific custom fields — job type, crew, materials used, room measurements, subfloor condition — have no Pipedrive standard equivalent. We create Pipedrive custom fields on the Deal or Activity object before migration, matching field type (text, number, picklist) to the source. Floors, materials, and measurement fields become number or text fields depending on data type.

Service Buddy's BuddyAI layer — automated insights, follow-up suggestions, and AI-suggested actions — is a platform feature with no direct Pipedrive equivalent. We export the current state of automated rules and follow-up flags as a reference document for rebuilding in Pipedrive Automations or an external tool.

Service Buddy's BuddyPay processor tracks card-on-file, ACH, and Apple Pay payment records per job. Pipedrive has its own payment integrations but not a native equivalent to BuddyPay's integrated payment ledger. We preserve payment method and transaction status as custom fields on the Deal and link to Pipedrive's payment integration if one is enabled.