Migrate from Bp Premier to Pipedrive

BP Premier clinical data has no native Pipedrive equivalent — custom fields required for every clinical attribute

BP Premier stores structured clinical data (prescriptions, diagnoses, Medicare billing codes, clinical notes) that maps to no native Pipedrive field. Pipedrive's custom field API accepts 16 field types, but each must be created in the target Pipedrive account before migration using hash-keyed field identifiers. FlitStack generates a custom field creation manifest from BP Premier's form field inventory. If your BP Premier setup has 50+ custom form fields, expect the field mapping phase to extend 2–3 days beyond the data migration window. Clinical attributes stored as free-text notes in Pipedrive may lose searchability compared to BP Premier's structured fields.

BP Premier appointment book has no Pipedrive scheduling equivalent — recall workflows must be rebuilt as Pipedrive automations

BP Premier's Appointment Book is a fully-featured scheduling system with provider availability, appointment types, recall reminders, and Medicare billing integration. Pipedrive Activities lack a scheduling component — they are task records with due dates, not calendar-slot reservations. Migrations from BP Premier to Pipedrive do not transfer appointment-booking configuration. FlitStack migrates appointment history as Activity records with timestamps and outcomes, but the scheduling logic (available slots, appointment durations, provider calendars) cannot translate. Your team must configure Pipedrive Calendar integration (Google Calendar or Outlook) and rebuild recall logic as Pipedrive automation rules triggered by Activity due_date.

BP Premier provider records must resolve to Pipedrive users by email — unmapped providers become orphaned Activities

Pipedrive's Activity model requires a user_id to associate the activity with an owner. BP Premier provider records do not contain Pipedrive user IDs. FlitStack resolves BP Premier provider records to Pipedrive users by matching the provider's email address against Pipedrive user accounts. If a BP Premier provider has no corresponding Pipedrive user (because they won't use Pipedrive, or their email doesn't match), their appointment history and clinical notes migrate as Activities without a valid user_id — these appear in Pipedrive as unassigned records owned by the migration service account. Your admin must decide whether to pre-create Pipedrive users for all BP Premier providers or accept unassigned Activity records.

Pipedrive's per-seat pricing means costs scale linearly with user count — BP Premier's per-practice model does not

BP Premier licenses practices at a flat per-practice rate regardless of user count within that practice. Pipedrive charges per seat per month. If your BP Premier setup has 5 providers and 10 administrative staff but only 3 will use Pipedrive, the per-seat cost is lower than BP Premier's equivalent. However, if 15 staff need Pipedrive access (for business development, outreach, and client management), Pipedrive's per-seat cost ($14–$99/user/month depending on tier) can exceed BP Premier's per-practice licensing at scale. Migration planning should include a user-count analysis against Pipedrive's pricing tiers before committing to migration.

Document attachments migrate as Pipedrive Files but lose BP Premier's clinical document metadata

BP Premier attachments (referral letters, imaging results, consent forms) store document-level metadata including document type, author, creation date, and classification. Pipedrive Files attach to Person records but store only filename, file type, and upload date. Clinical document metadata (document type, referring provider, urgency flag) is not captured in Pipedrive's file model. FlitStack migrates the file binary and original filename but cannot preserve BP Premier's internal document metadata unless your team accepts a custom document metadata field approach in Pipedrive.