Migrate from axiUm Dental to Pipedrive

Clinical data (treatment notes, CDT codes, odontograms) has no native Pipedrive home

axiUm's clinical records — chart notes, perio charting, CDT procedure codes, and odontogram data — are structured for a dental EHR and cannot map to Pipedrive's sales-oriented data model without significant flattening. FlitStack AI preserves clinical notes as Activity notes and stores CDT codes and treatment labels in custom fields on Deal and Activity records, but these are reference data only. Pipedrive's UI does not surface clinical context the way axiUm does; your clinical team must use axiUm's exported reports or a dedicated clinical tool for treatment documentation after migration. This is not data loss — it is honest acknowledgment that a sales CRM does not replace a dental EHR.

axiUm provider assignments do not map natively to Pipedrive user assignments

axiUm appointments carry a provider name and student-assignment for each clinical visit. Pipedrive Activities have an assigned_to_user_id field that links to a Pipedrive user by email. FlitStack AI resolves axiUm providers against Pipedrive users by email match — if a provider does not have a Pipedrive account, their name is stored as a custom field (provider_name_c) on the Activity. Academic institutions using axiUm's student-faculty assignment model will see student names stored as custom fields on Activities rather than as native Pipedrive user assignments, since students typically do not have Pipedrive seats.

axiUm patient status (active/inactive/archived) requires a custom field in Pipedrive

Pipedrive has no native patient-lifecycle status field. axiUm patient records with inactive or archived status will import as active Pipedrive People by default. FlitStack AI creates a custom patient_status_c field and maps the original axiUm status value so you can filter inactive patients out of Pipedrive workflows after migration. Without this field, inactive patients remain in active Pipedrive lists and may receive unintended outreach sequences.

Custom fields in axiUm become Pipedrive custom properties — key names differ per account

Pipedrive's API assigns random 40-character hash keys to custom fields (e.g., c_0f8a3b2e1d...), and the hash differs per Pipedrive account even for fields with the same display name. FlitStack AI creates the custom fields in your destination Pipedrive account during the pre-migration schema setup step and records the resulting hash keys for the field mapping. This means the custom field creation step is account-specific and cannot be pre-configured from a template. We surface the exact field keys in the migration plan before data moves.

Multi-site axiUm deployments require per-site organization mapping to Pipedrive

Large dental groups and dental schools using axiUm across multiple clinics or campuses typically have site-specific provider pools, appointment books, and billing ledgers. Pipedrive does not have a native multi-site concept — each location must be represented as an Organization record, a Pipeline, or a Label. FlitStack AI maps each axiUm site to a Pipedrive Organization or a labeled pipeline during discovery, and your admin chooses the representation that best fits your team's structure before migration runs.