CRM migration
Field-level mapping, validation, and rollback between The Dental System and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
The Dental System
Source
Pipedrive
Destination
Compatibility
13 of 14
objects map 1:1 between The Dental System and Pipedrive.
Complexity
BStandard
Timeline
48–72 hours
Overview
The Dental System is a dental practice management platform that stores patient demographics, clinical charts, treatment plans, appointments, and billing records. Pipedrive is a sales CRM built around Person, Organization, Deal, and Activity objects designed for pipeline management. These two platforms serve fundamentally different use cases: clinical workflow management versus sales process tracking. The migration challenge lies in translating dental-practice data into a CRM structure where it can support patient communications, follow-up scheduling, and sales pipeline activities. FlitStack AI maps The Dental System patient records to Pipedrive Persons, appointments to Activities, and treatment plan data to custom fields on both Person and Deal records. Clinical fields that have no CRM equivalent (dental chart data, perio measurements, procedure codes) are preserved as Pipedrive custom fields so your team retains the reference information. Owner resolution happens via email match against Pipedrive users. Pipedrive's API rate limit of 80 requests per 2 seconds and 10,000 POST/PUT requests daily per user governs our migration throughput, and we batch operations accordingly to avoid throttling. Pipedrive's Leads feature may also be relevant for pre-patient leads if your practice captures referrals before they become scheduled patients.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a The Dental System object lands in Pipedrive, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
The Dental System
Patient
Pipedrive
Person
1:1The Dental System patient records map directly to Pipedrive Persons. Patient name, date of birth, contact information, and address fields transfer as Person fields. Original patient ID preserved as Source_System_ID__c for traceability and delta-run deduplication.
The Dental System
Patient Address
Pipedrive
Person (address fields)
1:1Street address, city, state, and postal code from The Dental System map to Pipedrive's address subfields on Person. Multiple addresses (mailing vs. billing) require Pipedrive custom address fields if both are needed in the same record.
The Dental System
Patient Phone / Email
Pipedrive
Person (phone, email)
1:1Primary phone, mobile phone, and email from The Dental System map to corresponding Pipedrive Person fields. Additional phone numbers stored as Pipedrive custom fields since Pipedrive Person supports limited phone slots by default.
The Dental System
Appointment / Scheduling
Pipedrive
Activity (Task / Event)
1:1The Dental System appointments map to Pipedrive Activities. Scheduled appointment date and time become Activity due dates. Appointment type (cleaning, consultation, procedure) becomes Activity subject with type stored in custom field. Completed appointments become completed Activities with original timestamps preserved.
The Dental System
Treatment Plan
Pipedrive
Deal + custom fields on Person
many:1Treatment plans in The Dental System often contain multiple proposed procedures with associated values. We create a Pipedrive Deal representing the total treatment plan value, with procedure details stored as custom fields on the Deal and Person. Deal stage reflects treatment plan status (Proposed, Accepted, In Progress, Completed).
The Dental System
Insurance Information
Pipedrive
Custom fields on Person
1:1The Dental System insurance carrier, policy number, and coverage details have no native Pipedrive equivalent. We create custom fields on Person for Insurance_Carrier__c, Policy_Number__c, and Coverage_Type__c. This data is preserved for reference but Pipedrive doesn't have a native insurance workflow model.
The Dental System
Clinical Notes / Chart Notes
Pipedrive
Note on Person
1:1Clinical notes from The Dental System transfer as Pipedrive Notes attached to the Person record. Original note date and author preserved. Notes are not searchable in Pipedrive's default full-text search but appear in record detail views and can be included in custom reports.
The Dental System
Prescription Records
Pipedrive
Custom fields on Person
1:1Prescription data from The Dental System migrates as custom fields on Person (Prescription_Date__c, Prescription_Medication__c, Prescription_Notes__c). Pipedrive has no native prescription object, so this data serves as historical reference only.
The Dental System
Referring Dentist / Source
Pipedrive
Organization + custom field
1:1Referring dentist or referral source in The Dental System maps to a Pipedrive Organization record representing the referring practice. A custom field on the Person (Referral_Source_ID__c) links back to the source organization for reporting on lead source effectiveness.
The Dental System
Billing / Ledger
Pipedrive
Custom fields on Person
1:1Account balance, last payment date, and outstanding amounts from The Dental System ledger transfer to Pipedrive custom fields (Account_Balance__c, Last_Payment_Date__c, Outstanding_Amount__c). Pipedrive is not a billing system so these serve as reference data only.
The Dental System
User / Provider
Pipedrive
Pipedrive User
1:1The Dental System provider and staff records are resolved by email match against Pipedrive users. Unmatched providers are flagged and assigned to a fallback Pipedrive user. Provider specialties are stored as a custom field on the Pipedrive user profile for routing purposes.
The Dental System
Patient Owner / Responsible Staff
Pipedrive
Person (owner_id)
1:1The Dental System staff member assigned as patient's primary contact resolves to Pipedrive Person owner via email match. This ensures follow-up tasks and activities route to the correct team member in Pipedrive.
The Dental System
Procedure History
Pipedrive
Activity with custom fields
1:1Completed procedures from The Dental System map to Pipedrive Activity records with procedure codes and notes in custom fields. Procedure date becomes Activity due date. This creates a searchable procedure history attached to the Person record without using Pipedrive's native deal model.
The Dental System
Recall / Re-care Schedule
Pipedrive
Activity with due date
1:1The Dental System recall appointments (e.g., 6-month cleaning reminders) become Pipedrive Activities with future due dates. A custom field (Recall_Type__c) distinguishes hygiene recall from other appointment types so your team can filter recall activities in Pipedrive's list view.
| The Dental System | Pipedrive | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Patient Address | Person (address fields)1:1 | Fully supported | |
| Patient Phone / Email | Person (phone, email)1:1 | Fully supported | |
| Appointment / Scheduling | Activity (Task / Event)1:1 | Fully supported | |
| Treatment Plan | Deal + custom fields on Personmany:1 | Fully supported | |
| Insurance Information | Custom fields on Person1:1 | Fully supported | |
| Clinical Notes / Chart Notes | Note on Person1:1 | Fully supported | |
| Prescription Records | Custom fields on Person1:1 | Fully supported | |
| Referring Dentist / Source | Organization + custom field1:1 | Fully supported | |
| Billing / Ledger | Custom fields on Person1:1 | Fully supported | |
| User / Provider | Pipedrive User1:1 | Fully supported | |
| Patient Owner / Responsible Staff | Person (owner_id)1:1 | Fully supported | |
| Procedure History | Activity with custom fields1:1 | Fully supported | |
| Recall / Re-care Schedule | Activity with due date1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
The Dental System gotchas
No documented public API
Custom field discovery requires manual audit
Insurance carrier and payer data may require re-credentialing
Document storage may not be directly accessible for bulk export
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
Export and audit The Dental System data
We extract patient records, appointments, treatment plans, procedure history, recall schedules, and referring source data from The Dental System via API or CSV export. Our team audits the export for duplicate records, orphaned appointments (patient records with no valid link), inconsistent date formats, and missing owner assignments. You receive a written data audit report before field mapping begins, identifying records that need cleanup or manual resolution.
Configure Pipedrive custom fields and pipelines
Before importing data, we create the custom fields in Pipedrive required for dental practice data: Insurance_Carrier__c, Policy_Number__c, Account_Balance__c, Recall_Type__c, Procedure_Code__c, Source_System_ID__c, Original_Create_Date__c, and others identified during the audit. We also configure a Treatment Plans pipeline in Pipedrive with stages (Proposed, Accepted, In Progress, Completed, Lost) that match your practice's case acceptance workflow. Your Pipedrive admin approves the schema before migration runs.
Resolve owners by email match against Pipedrive users
The Dental System provider and staff assignments resolve to Pipedrive users by email address. Unmatched providers (staff records with no corresponding Pipedrive user) are flagged and assigned to a fallback Pipedrive user designated by your admin. For practices with providers who don't have Pipedrive accounts, we create a note in the custom field Provider_Name__c on the Person record so the provider name is preserved even without an active Pipedrive assignment.
Run test migration on sample subset
A representative sample (typically 100-500 records spanning patients, appointments, treatment plans, and activities) migrates to Pipedrive first. We generate a field-level diff showing source values versus destination field contents so you can verify mapping accuracy before the full run. Common verification points include: patient name formatting, appointment dates and times, treatment plan values, recall scheduling, and referring source linking. You approve the test results in writing before we schedule the full migration.
Execute full migration with delta-pickup window
The full migration runs against Pipedrive's API using batched requests that respect rate limits. A delta-pickup window (24-48 hours after migration start) captures any new appointments, updated treatment plans, or new patient records created in The Dental System during the cutover period. Your team continues working in The Dental System during migration; FlitStack AI uses scoped read access only. After the delta-pickup closes, we run a final validation comparing record counts between source and destination.
Deliver audit log and rollback capability
Every migration operation is logged with source record ID, destination record ID, field mappings applied, and timestamp. If reconciliation reveals missing records or incorrect values, one-click rollback reverts all changes in Pipedrive. We deliver a migration summary report showing record counts by object, any records that failed to migrate with error reasons, and a list of Pipedrive custom fields that require ongoing maintenance (insurance updates, recall scheduling, etc.)
Platform deep dives
The Dental System
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across The Dental System and Pipedrive.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
The Dental System: Not publicly documented.
Data volume sensitivity
The Dental System doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during The Dental System to Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your The Dental System to Pipedrive migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave The Dental System
Other ways to arrive at Pipedrive
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.