Migrate from BSI CRM to Pipedrive

BSI CRM Contact records map directly to Pipedrive Person. Standard fields (first_name, last_name, email, phone, job_title) transfer directly. Custom Contact fields migrate as Pipedrive custom fields on Person, which must be created in Pipedrive before migration. BSI's contact owner assignment maps to Pipedrive user_id on the Person record via email-based lookup.

BSI CRM Company records map to Pipedrive Organization. Fields like name, website, industry, address, and phone transfer directly. BSI's hierarchical parent-child company relationships map to Pipedrive's Organization hierarchy via the parent_org_id field. Industry classification from BSI's modular vertical configuration migrates to a custom field if Pipedrive's standard industry picklist does not cover the specific BSI vertical.

BSI CRM Deals map to Pipedrive Deals. Pipeline stages from BSI's industry-specific configuration require explicit mapping to Pipedrive pipeline stages during scoping because BSI stage names and counts vary by deployment. Deal value, expected close date, owner assignment, and custom properties migrate directly. BSI's deal stage probabilities map to Pipedrive stage weighted values if configured in BSI.

Each BSI CRM pipeline configuration becomes a Pipedrive pipeline. BSI stage names map to Pipedrive stage names and stage order. Probabilities assigned in BSI migrate to Pipedrive's stage probability values. Pipedrive supports multiple pipelines from the Growth tier onward, so multi-pipeline BSI deployments map cleanly without tier restrictions.

BSI CRM logged calls, emails, meetings, and tasks map to Pipedrive Activity records. Each activity type (call, email, meeting, task) has a corresponding type field in Pipedrive. Activity timestamps preserve ordering in Pipedrive's timeline. BSI's activity linkage to Contacts and Deals maps to Pipedrive's person_id and org_id links on the Activity record, resolved at migration time via the Contact-to-Person and Deal ID lookups.

BSI CRM Users and Owners migrate to Pipedrive Users. Resolution is by email match. Any BSI User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets are not transferred because Pipedrive's role model is independent.

BSI CRM custom objects and fields require pre-migration enumeration during discovery because the schema is not self-documenting in BSI. Each custom object becomes a set of custom fields on the relevant Pipedrive object (Person, Organization, Deal, or Activity). Field types are mapped: BSI text to Pipedrive text, BSI number to Pipedrive number, BSI date to Pipedrive date, BSI dropdown to Pipedrive select. Multi-select classifications in BSI map to multi-select custom fields in Pipedrive. Custom object schema must be deployed in Pipedrive before data migration begins.

File attachments associated with BSI CRM Contacts, Deals, or Activities are exported individually and linked back to their parent record in Pipedrive via the deal_id, person_id, or org_id foreign key. BSI's file storage structure varies by deployment configuration, so we enumerate attachment locations during discovery and normalize paths before mapping to Pipedrive's Files object.

BSI CRM tags and custom classification fields migrate to Pipedrive Labels. Labels in Pipedrive apply across Persons, Organizations, Deals, and Products, providing the same cross-object tagging capability that BSI supports. Tag frequency analysis during discovery identifies high-volume tags that may warrant a dedicated custom field rather than freeform labels.

BSI CRM email engagement records (email body, timestamp, direction, recipient) map to Pipedrive Activity with type = email. Email content is stored in Pipedrive's activity body field. The person_id and org_id links on the Activity record connect the email to the correct Person and Organization in Pipedrive. Attachments on emails migrate as Pipedrive Files linked to the Activity.

BSI CRM call engagements map to Pipedrive Activity with type = call. Call duration, disposition, and outcome from BSI transfer to custom fields on the Pipedrive Activity record. Timestamp preserves the original call date for timeline ordering. Owner assignment migrates via email-to-user lookup.

BSI CRM meeting engagements map to Pipedrive Activity with type = meeting. Meeting title, description, location, and duration transfer directly. Attendee information from BSI's meeting record migrates to the Pipedrive Activity's participant list linked via Person lookups. The activity timestamp and duration preserve the original meeting schedule for calendar and timeline fidelity.