Migrate from The Clinic Place to Pipedrive

The Clinic Place patient records map directly to Pipedrive People. The patient's name splits into first_name and last_name, email and phone carry over directly, and address fields map to Pipedrive's address subfields. A custom field stores the original The Clinic Place patient ID for traceability and delta-run deduplication.

The Clinic Place clinic locations or practice sites map to Pipedrive Organizations. Organization name, address, phone, and website fields map directly. Multi-location practices create one Organization per site. If The Clinic Place stores referring physician or referring practice as separate entities, they map to separate Organizations.

The Clinic Place appointments become Pipedrive Activities. Appointment type (e.g., 'New Patient', 'Follow-Up', 'Consultation') becomes the Activity subject. Original appointment date and time are preserved as the Activity due date and end time. Appointment status (Completed, Cancelled, No-Show) maps to Pipedrive Activity completed flag. The clinician who owned the appointment resolves to the Pipedrive user by email match.

The Clinic Place invoices map to Pipedrive Deals. Invoice amount becomes Deal value. The associated patient becomes a Person link, and the clinic or location becomes the Organization link. Pipeline and stage are set to the default or a custom pipeline; practices may want separate pipelines for different service lines (e.g., 'Consultations', 'Procedures') which map to separate Pipedrive pipelines.

The Clinic Place insurance carrier, policy number, group number, and eligibility status have no Pipedrive native equivalent. These migrate as custom fields on the Person record: Insurance_Carrier__c, Insurance_Policy_Number__c, Insurance_Group__c, Insurance_Eligible__c. Pipedrive's custom field hash key is assigned per account, so FlitStack AI creates these fields during workspace setup before migration.

The Clinic Place diagnosis codes and clinical notes have no Pipedrive equivalent. Diagnosis codes migrate as a custom pick-list or text field (Diagnosis__c). Freeform clinical notes are converted to Pipedrive Notes attached to the Person record. This is a manual review item — practices should decide whether clinical notes belong in a CRM or a separate system.

Prescription details (medication name, dosage, prescriber, date) stored in The Clinic Place become custom fields on the Pipedrive Person record: Prescription_Medication__c, Prescription_Dosage__c, Prescription_Prescriber__c, Prescription_Date__c. Pipedrive does not have a native prescription object; custom fields provide the reference record. These fields capture medication name, dosage strength, prescriber, and date, allowing staff to view prescription history within Pipedrive. They are created during workspace setup following Pipedrive naming conventions.

The Clinic Place documents and clinical charts are exported and re-uploaded as Pipedrive Files. Each file is associated to the corresponding Person record. Pipedrive stores files separately from notes; documents appear in the Files tab of the Person detail view. Large imaging files or PDFs require manual review to confirm correct association post-migration.

The Clinic Place clinicians and staff members map to Pipedrive Users by email address match. If a clinician email in The Clinic Place matches a Pipedrive user email, the user is linked automatically. Unmatched clinicians are flagged before migration — practices either invite them to Pipedrive first or assign their records to a fallback user during migration.

Referral source (e.g., 'Physician referral', 'Insurance network', 'Walk-in') stored in The Clinic Place as a patient property becomes a Pipedrive custom field: Referral_Source__c. This field can be a pick-list if The Clinic Place uses a defined set of referral sources, or a free-text field if referral sources vary.

Payment records from The Clinic Place (amount paid, payment date, payment method) are merged into the corresponding Pipedrive Deal as custom fields (Payment_Amount__c, Payment_Date__c, Payment_Method__c) and an Activity note recording the payment event. Partial payments are not native Pipedrive Deal objects — custom fields preserve the payment record.