Migrate from tab32 to Pipedrive

tab32 patients map 1:1 to Pipedrive People. Name, email, phone, address, and DOB transfer directly without transformation. The patient's original tab32 ID is stored in a Source_System_ID__c custom field for traceability and duplicate detection on delta runs, ensuring that any future sync attempts can identify existing records accurately.

Insurance records do not have a Pipedrive equivalent. We migrate provider name, plan type, group number, and subscriber as custom fields on the Person record. Active claim status migrates as an Activity note — your billing team should track active claims separately post-migration.

Each tab32 treatment plan merges into a single Pipedrive Deal. The deal name uses the patient name + plan date. CDT codes, procedure descriptions, and estimated costs become custom fields on the Deal. The Deal is linked to the Person via Pipedrive's native Person-Deal association.

tab32 providers resolve to Pipedrive Users by email match. Unmatched providers are flagged before migration so your admin can create Pipedrive user accounts first. Activities and Deals owned by the provider assign to the matched User record, ensuring proper accountability tracking.

Scheduled appointments transfer as Pipedrive Activities with original timestamps, assigned provider, and appointment type preserved as Activity type labels. Subsequent visits for the same patient group under the Person record. The Activity is linked to both the Person and the Provider (User) record.

CDT procedure codes from tab32 treatment plans must be pre-created as Pipedrive custom text fields on the Deal object before data import begins. Each code is a separate field. Value mapping for code descriptions requires additional configuration if readable names are preferred over raw code strings.

Each tab32 location becomes a Pipedrive Organization. Location name, address, and phone map directly to Organization fields. For DSOs, we configure a parent Organization representing the enterprise group, then nest each location as a child Organization under it for cross-location reporting in Pipedrive analytics.

tab32 clinical charts (tooth charts, perio exams, radiographs) export as PDF documents and re-upload as Pipedrive Attachments on the Person record. Pipedrive cannot parse or display the clinical content — the attachment is a reference archive only. Your clinical team should retain tab32 read access for historical chart review.

Radiograph and imaging files from tab32 download and re-upload to Pipedrive as file attachments on Person records. No thumbnail or embedded viewer is available in Pipedrive. Staff click the attachment to download the original file for review; they cannot preview images inline.

Outstanding patient account balances migrate as a custom currency field (Account_Balance__c) on the Person record. tab32 billing transactions, insurance payments, and claim history have no Pipedrive equivalent — these records are summarized as Activity notes and exported as a separate billing CSV for your billing team's records.

The referral source field capturing how a patient found the practice transfers directly as a Pipedrive custom field on the Person record. If tab32 uses a pick-list, value mapping is applied to preserve the same options in Pipedrive's dropdown configuration.

tab32 recall records indicating when a patient is next due for a hygiene or recall visit migrate as a custom date field on the Person record. Pipedrive has no native recall system — your team can build an automation that checks this date and creates Activities, or maintain recall tracking in a separate report exported from tab32.