Migrate from Salesboom to Pipedrive

Salesboom's Lead tab has its own field structure separate from Contact. We assess each Lead record at migration time: Leads with no Opportunity association and no sales-qualified status become Pipedrive Persons. Leads with an associated Salesboom Opportunity or a qualified stage status become Pipedrive Deals, with the original Lead data stored as custom fields on the Deal. The decision depends on your Salesboom pipeline stages and is confirmed during scoping. Lead status and lead score from Salesboom migrate as custom fields on the Pipedrive Person or Deal.

Salesboom Accounts map directly to Pipedrive Organizations. The Account hierarchy (parent-account relationships) does not have a native Pipedrive equivalent; we store parent-account references in a custom field parent_organization__c on the Organization record. Billing address and shipping address from Salesboom merge into Pipedrive's single address block on Organization.

Salesboom Contacts map to Pipedrive Persons with the Account-to-Organization link preserved. Name, email, phone, title, and address fields migrate directly. Salesboom's custom Contact fields (unlimited at no extra charge) map to Pipedrive custom fields created during the pre-migration schema design phase. We resolve the Organization lookup before Person insert to satisfy Pipedrive's requirement that a Person's org_id references a valid Organization.

Salesboom Opportunities map to Pipedrive Deals. The deal stage in Salesboom maps to a Pipedrive pipeline stage; if Salesboom has multiple Opportunity stages, we create a corresponding Pipedrive pipeline with matching stage names. Deal amount, close date, probability (as custom field, since Pipedrive does not expose probability by default), and owner migrate directly. The Salesboom Opportunity name becomes the Pipedrive Deal title.

Each Salesboom Opportunity pipeline becomes a Pipedrive Pipeline with corresponding stages. Probability values from Salesboom are stored as custom fields on the Deal since Pipedrive's standard Deals do not include probability. We configure the pipeline before Deal import so that stage IDs are available at migration time.

Salesboom Tasks migrate to Pipedrive Activities of type Task. Subject, status, priority, due date, and owner migrate directly. We resolve the owner by email match against Pipedrive Users. Recurring Salesboom Tasks are flattened into individual Task records at the destination since Pipedrive does not support native recurring task patterns.

Salesboom Calendar Events migrate to Pipedrive Activities of type Event. Start time, end time, title, location, and attendees migrate. Attendees resolve by email match to Pipedrive Person or Organization records. Event associations to parent records (Account, Contact, Opportunity) migrate as Activity links in Pipedrive.

Salesboom Notes attached to any parent record (Account, Contact, Opportunity) migrate to Pipedrive Notes linked to the equivalent Person, Organization, or Deal. Rich-text formatting in Salesboom notes is preserved as plain text to ensure compatibility at the destination. Note ownership migrates by email match to Pipedrive Users.

Salesboom Cases (ticket-style support records with status, priority, origin, and resolution fields) do not have a native Pipedrive equivalent in standard plans. We migrate Cases as Pipedrive Leads or Deals depending on whether the Case represents a pre-sale inquiry or a post-sale support item. Auto-assignment rules and escalation workflows from Salesboom Cases are documented but not migrated as automation logic. If the customer has Pipedrive's optional Service Hub, Cases map to Pipedrive's ticket object.

Salesboom's unlimited custom fields on any standard tab migrate to Pipedrive custom fields. We create each custom field in Pipedrive during the pre-migration schema phase with a type-matched field (text, number, date, dropdown, checkbox, etc.) sourced from the Salesboom field type. Field data migrates as values on the corresponding standard object (Person, Organization, Deal, or Activity). Note that Pipedrive's custom field limits vary by plan and field type; we confirm available limits during scoping.

Salesboom Owner references on Contact, Account, Opportunity, and Activity records map to Pipedrive Users by email match. Any Salesboom Owner without a matching Pipedrive User goes to a reconciliation queue for your admin to provision before record import resumes. Inactive Salesboom users are mapped to inactive Pipedrive Users to preserve historical assignment.

Salesboom ERP modules (Accounts Payable, HR Policy Tracking, Payroll, PTO Management, Expense Tracking) are paid add-ons at $10/user/month with schemas distinct from CRM objects. We scope ERP module data during the pre-migration audit and present three options: migrate as Pipedrive custom objects (requires schema design and Pipedrive plan supporting custom fields), skip migration and rely on the originating ERP system's exports, or defer to a separate ERP-to-ERP migration. Pipedrive does not have native ERP capabilities; integration to QuickBooks or Xero via Pipedrive's marketplace is the standard post-migration path.