Migrate from Inception to Pipedrive

Direct 1:1 mapping. Inception's Healthcare Professional (HCP) contact records map to Pipedrive People. HCP specialty, license number, and prescribing class fields from Inception migrate as custom fields on the Pipedrive Person record. Owner resolution uses email match against Pipedrive users.

Direct mapping. Inception company records (pharmacies, hospitals, clinic accounts) map to Pipedrive Organizations. For parent/branch structures, the parent becomes the Pipedrive Organization and each branch location is added as an extra address entry or linked activity note. The original Inception company ID is stored in a custom field for traceability, and associated contacts stay linked to the parent Organization.

Direct mapping with stage transformation. Inception deal stages (e.g., Initial Call, Sample Delivered, Rx Written) map to Pipedrive stage values. Each Inception pipeline becomes a Pipedrive pipeline. Deal values and close dates migrate directly. Custom fields for Rx type (new prescription, refill, sample) become Pipedrive custom fields.

Inception's field visit records (timestamp, HCP linked, territory visited, outcome) map to Pipedrive Activities of type 'Visit' or 'Call'. Visit outcomes (seen, not seen, sample left) are stored as custom fields or notes in Pipedrive since Pipedrive Activities do not have a native outcome-status field. Original visit timestamps are preserved in the activity start/end times.

Inception call logs with HCP name, call duration, and discussion notes map directly to Pipedrive Activities of type 'Call'. Notes content migrates to the Pipedrive activity note field. Call outcome (interested, not interested, follow-up scheduled) becomes a custom field on the activity.

Inception sample records (product, quantity, lot number, HCP, date) do not have a direct Pipedrive equivalent. FlitStack maps sample transactions to Pipedrive Products linked via Deal Line Items, with sample-specific fields (lot number, expiry) stored as custom fields on the product or as note attachments. Compliance reporting fields must be manually reconfigured in Pipedrive.

Inception territories (geographic or product-based rep assignments) have no Pipedrive native equivalent. We create a Territory__c custom field on both Person and Organization objects in Pipedrive. Territory assignment rules (which rep owns which territory) must be rebuilt using Pipedrive's Automations.

Inception's rep target settings (monthly Rx targets, sample budgets, call frequency goals) do not map to any Pipedrive native object. These migrate as custom fields on Pipedrive User records or as goal-related custom fields on Deals. Pipedrive's revenue forecasting replaces the target-attainment model; teams must define new targets in Pipedrive's goal-setting module.

Inception emails logged against HCP contacts migrate as Pipedrive Email Activities linked to the corresponding Person. The email's from, to, and cc addresses are stored in Pipedrive's standard email fields, and thread identifiers are captured. Email body content and timestamps are preserved. Attachments are uploaded to Pipedrive Files and linked to the activity record. If an email references a previous call or visit, the link is noted in the description.

Freeform notes attached to Inception contacts, companies, or deals migrate as Pipedrive Notes. Rich-text formatting in Inception notes may be simplified during migration; HTML notes are converted to plain text with basic formatting preserved where possible. The original creation date and author are stored in custom fields, and any file attachments within the notes are extracted and uploaded to Pipedrive Files, then linked back to the note.

Inception product catalog (pharmaceutical products, samples, promotional items) maps directly to Pipedrive Products. Unit price, SKU, and description migrate. Custom fields specific to Inception (e.g., product category, sample eligibility) become Pipedrive custom fields on the Product object. Product images are uploaded to Pipedrive Files and linked to the product record. For bundled or kit products, each component is created as a separate Pipedrive Product and linked via a bundle relationship.

Inception HCP specialty codes (e.g., Cardiologist, General Practitioner, Oncologist) have no Pipedrive equivalent. We create a Specialty__c pick-list custom field on the Pipedrive Person object with values mapped from Inception. The source specialty code is preserved in the field for reference.