Migrate from Core Practice to Pipedrive

Core Practice patients map directly to Pipedrive People. Name, email, phone, address, and date of birth transfer as standard Person fields using FlitStack's direct field mapping. For patients without an email address on file, FlitStack assigns a placeholder email flag so your team can identify and complete those records post-migration. This prevents incomplete Person records and ensures your Pipedrive database remains clean and actionable for downstream sales and communication workflows.

When a Core Practice patient has an associated family or employer record, FlitStack AI creates a Pipedrive Organization and links the Person to it via the org_id field. This preserves the patient-company relationship without collapsing it into a single flat record.

Core Practice appointment records (date, time, duration, appointment type, status) map to Pipedrive Activities. Each appointment becomes a Task or Event activity with the original start/end timestamps and the appointment type stored in a custom field (Appointment_Type__c). Cancelled appointments are migrated as completed tasks with a Cancelled status.

Core Practice treatment plans list procedures, prices, and stages (e.g. Initial Exam, Orthodontics, Surgery). FlitStack creates a Pipedrive Deal per treatment plan, sets the deal value to the plan total, and attaches the full procedure list as a Note. Individual procedures are stored in custom fields on the Deal.

Core Practice invoices (amount, status, line items) have no native Pipedrive equivalent. FlitStack migrates invoice metadata as custom fields on the linked Deal (Invoice_Status__c, Total_Invoice__c) and attaches the original invoice PDF as a Pipedrive File. Payment history is stored in a custom Activity Note.

Core Practice staff records (name, role, email) map to Pipedrive Users. FlitStack resolves each Core Practice practitioner by email match against Pipedrive user accounts. Unmatched staff are flagged before migration so you can create Pipedrive accounts or reassign their records.

Dental insurance information—including provider name, policy number, and coverage percentage—stored in Core Practice is mapped to custom fields on the Pipedrive Person record. These include Insurance_Provider__c, Policy_Number__c, and Coverage_Pct__c fields created via Pipedrive's API before migration. The data migrates as informational reference only, since Pipedrive has no billing ledger or claims-processing capability. Your team should maintain insurance records in a dedicated dental practice management or accounting tool post-migration.

Core Practice clinical notes per patient attach as Pipedrive Notes linked to the Person record. FlitStack preserves the original note date and author in the Note body header. Large chart attachments (X-rays, intraoral photos) are downloaded and re-uploaded as Pipedrive Files with a link back to the Person.

Core Practice products (dental materials, equipment items used in treatment) map to Pipedrive Products. Product name, unit price, and unit description transfer. Stock levels and supplier information are stored as custom fields since Pipedrive Products track price and SKU only.

If Core Practice has a pre-appointment inquiry or marketing lead record, those map to Pipedrive Leads. Leads inherit all custom fields configured for Pipedrive Deals. Unqualified leads remain in the Pipedrive Lead Inbox until your team converts them to Deals.

Core Practice appointment reminders, SMS confirmations, and recall workflows are platform-native constructs with no Pipedrive equivalent. FlitStack exports the workflow definitions as a structured JSON document for your team to rebuild in Pipedrive Automations or a third-party scheduling tool like Calendly.

Core Practice clinical and financial dashboards have no Pipedrive equivalent. The underlying data (appointment counts, revenue per patient, treatment plan values) migrates into Pipedrive Deals and Activities so you can rebuild equivalent reports in Pipedrive's Insights module or connect to a BI tool.