Migrate from SalesPro CRM to Pipedrive

SalesPro Contact records map directly to Pipedrive Person objects. We map name, email, phone, company association, and address fields to Pipedrive Person standard fields. The salespro_contact_id is preserved in a custom field for dedupe validation during migration. Permission-based sharing settings from SalesPro do not have a direct Pipedrive equivalent; we set all migrated Persons to default visibility based on Pipedrive's team sharing model.

SalesPro Company records map to Pipedrive Organization. The company name becomes the Organization name field, and any domain or website data maps to the Organization URL field. We resolve the Contact-to-Company linkage as the Person's org_id reference in Pipedrive after Organization records are inserted first.

SalesPro Event records (containing date ranges, group details, venue specs, and BEO references) map to Pipedrive Deals. The event title becomes the Deal title, start and end dates map to the Deal's close date or custom date fields, and the event description becomes the Deal's notes. Each Event's BEO reference is preserved in a custom Deal field beo_reference__c pointing to the reconstructed BEO record. Owner assignment migrates by email lookup against the resolved Pipedrive User records.

SalesPro BEO records are derived outputs from Events and do not exist as standalone objects in the data model. We reconstruct BEO data as a Pipedrive custom object named BEO, capturing cost calculations, timeline specifications, and event signatures as custom fields. The custom object is pre-created in Pipedrive before migration, and the beo_reference__c field on each Deal resolves to the corresponding BEO record ID. Pipedrive's Advanced plan supports custom objects; Essential and Professional tiers cannot host custom objects and require a workaround of custom fields on Deal or Activity records.

SalesPro Task records (with assignees, due dates, email reminders, and completion status) map to Pipedrive Activity records with type = Task. Assignee resolution uses email-to-User lookup. Due dates map to the Activity due_date field, and completion status maps to Activity done (boolean). Email reminder flags from SalesPro do not have a direct Pipedrive equivalent and are noted in the migration inventory for admin review.

SalesPro Milestones are custom goal-based markers tied to sales cycles or deals. In Pipedrive, we map milestones to a custom multi-select picklist field on Deal if the destination plan supports custom fields, or to a mapped Deal stage if the milestone represents a pipeline stage transition. The mapping strategy is confirmed during scoping based on the customer's milestone naming convention and whether they use Pipedrive's standard stage model.

SalesPro pipeline stages map to Pipedrive Pipeline stages by name and relative ordering. We preserve stage names exactly and set stage probability percentages to match SalesPro values where available. Custom stage names require pre-configuration in Pipedrive before migration because Pipedrive stage values must exist in the pipeline before Deals can be assigned to them.

SalesPro Users are mapped to Pipedrive Users by email address. Active SalesPro users become active Pipedrive Users; inactive or archived users become inactive Pipedrive Users to preserve assignment history. The migration cannot insert records with OwnerId references pointing to Users that do not yet exist, so User provisioning is validated before any record import phase begins.

SalesPro Calendar entries (bookings with start/end timestamps and resource assignments) map to Pipedrive Activity records with type = Meeting. The calendar booking title becomes the Activity subject, start and end times map to Activity start and end fields, and resource assignments map to Activity participants. Attendees are linked to Person or Organization records by email where a matching record exists in Pipedrive.

SalesPro does not expose a bulk attachment export endpoint via its webhook API. Attachments associated with Events, BEOs, or Contacts cannot be programmatically retrieved without direct database access. We notify customers before migration that file attachments will not transfer. As a partial workaround, we document which records have attachments and flag the affected Contacts, Events, and BEOs so the customer's admin can manually upload after cutover. This limitation is documented in the migration scope agreement before work begins.