Migrate from Denticon to Pipedrive

Direct map. Denticon patient contact fields (name, email, phone, address) migrate to Pipedrive Person standard fields. Patients without a referral source attachment link to a default 'Unassigned' Organization record in Pipedrive. If an email address is missing, FlitStack uses the patient's phone number formatted as a contact identifier in the Email field to maintain uniqueness.

Direct map. Street address, city, state, postal code, and country migrate as Pipedrive address components. Patients with multiple addresses use the most-recently-modified address as primary; secondary addresses stored as custom text fields. If the country code differs from Pipedrive's ISO standard, FlitStack normalizes it to the two-letter ISO code before loading.

Direct map. Primary email address migrates to Pipedrive Email field. Secondary or undeliverable email addresses preserved as custom text fields on the Person record for reference. FlitStack also flags duplicate email addresses across patients to prevent unintended merging in Pipedrive and logs each occurrence for review.

Direct map. Primary phone migrates to Phone field; mobile phone to Mobile Phone field; additional phone numbers (e.g., emergency contact) stored as custom varchar fields. FlitStack validates phone number formats and strips non-numeric characters, then formats them according to Pipedrive's E.164 standard when possible.

Denticon referral sources — individual providers, other dental practices, or corporate referral partners — map to Pipedrive Organizations with type='Referral'. Referral type (provider, practice, corporate) and cost fields migrate as custom fields on the Organization. If a referral source name appears multiple times, FlitStack appends a numeric suffix to ensure distinct Organization names.

Outgoing referrals to specialist providers map to Pipedrive Organizations with type='Specialist'. Referral status, completion date, and referred-to-provider fields preserved as custom fields for referral program reporting. FlitStack also records the original Denticon referral ID as a custom field to enable cross-referencing and audit trails.

Primary insurance carrier becomes a separate Pipedrive Organization with type='Insurance'. Secondary insurance handled as a second Organization link via custom field or custom text field storing carrier name. Full claims history stays in Denticon. FlitStack also maps the insurance plan type (e.g., PPO, HMO) as a custom picklist field on the Organization for segmentation.

Denticon providers map to Pipedrive Users by email match. Provider specialty, NPI number, and license expiration preserved as user custom fields. Providers without email addresses are flagged before migration — your admin assigns them to an existing Pipedrive User or creates a placeholder.

Appointment summaries (date, type, provider, status, production type) migrate as Pipedrive Activities with Type='Appointment'. Original appointment timestamp preserved as a custom datetime field. Detailed clinical notes from appointments migrate as separate Note records. FlitStack also maps the appointment status (e.g., completed, no-show) to the Pipedrive Done flag, ensuring accurate pipeline activity tracking.

Free-text appointment notes and clinical observations migrate as Pipedrive Notes attached to the Person record. Notes exceeding Pipedrive's character limit are split across multiple Note records with sequencing markers. Each split note retains a header indicating its sequence number and total parts, so the original note can be reassembled if needed.

Treatment plan names, procedure codes, and overall status migrate as Notes on the Person record for reference. Detailed tooth-specific charting, x-ray references, and clinical periodontal data have no Pipedrive equivalent — exported as a separate reference file. FlitStack also preserves the treatment plan creation date as a custom datetime field on the Note for timeline analysis.

Denticon allows alphanumeric custom fields (up to 25 characters per field name) across patient, referral, and account categories. These map to Pipedrive custom fields on Person with matching data types: varchar to varchar, date to date, picklist to enum. FlitStack pre-creates all custom fields before migration.

Pipedrive's CreatedDate reflects migration time, not the original patient record creation. FlitStack preserves the original Denticon create date as Patient_Created_Date__c (datetime) on the Person record for reporting continuity. This custom field enables historical reporting on patient acquisition trends and supports date-based segmentation in Pipedrive analytics.

Denticon's internal patient UUID stored as Source_System_ID__c on Pipedrive Person for traceability, cross-reference during reconciliation, and delta-run deduplication to prevent duplicate records on subsequent migrations. The UUID also facilitates data lineage tracking if you later need to map Pipedrive records back to Denticon for audit or compliance purposes.

Multi-location DSO setups require Office_ID__c custom field on Person to identify which Denticon office a patient belongs to. FlitStack delivers a visibility-group mapping plan so your Pipedrive admin configures data access controls per location post-migration. This plan includes a matrix of Office_ID values versus Pipedrive user groups, simplifying the visibility configuration steps.