Migrate from DGL Practice Manager to Pipedrive

DGL stores patient demographics (name, DOB, contact details, NHS/GMC identifiers) as the core EPR record. FlitStack maps these directly to Pipedrive Person fields: first_name, last_name, email, phone, and the address compound fields. DGL's internal patient ID is preserved as Source_System_ID__c custom field on the Person for delta-run de-duplication and traceability back to the DGL record.

DGL's clinic or referring practice entity holds the organisational context for a patient — the clinic name, address, and primary contact. FlitStack maps this to Pipedrive Organisation with name, address fields, and website. For multi-clinic DGL setups, each clinic becomes a separate Organisation record and DGL patients are linked via the Organisation field on each Person record.

DGL appointment diary entries contain appointment date, time, practitioner, appointment type (e.g., new patient, follow-up, procedure), and status. FlitStack translates these to Pipedrive Activities: the appointment type determines the activity type field (Meeting for consultations, Task for administrative appointments), the DGL practitioner email resolves to a Pipedrive user as the activity owner, and both Person and Organisation are linked via the Person ID and Organisation ID fields on the activity.

DGL's appointment type flags (new patient consultation, follow-up, diagnostic, procedure, emergency) have no 1:1 Pipedrive equivalent since Pipedrive activity types are limited to Call, Meeting, and Task. FlitStack creates an Appointment_Category__c custom field on Activity and maps each DGL appointment type to a corresponding custom value. This preserves the clinical distinction in Pipedrive's activity list view.

DGL clinical notes and procedure records store the clinical narrative, procedure performed, and clinical outcome attached to a patient. FlitStack migrates these as Pipedrive Notes linked to the Person record, with the procedure type and date preserved in the note content and a Procedure_Type__c custom field for filtering. Notes preserve the original DGL timestamp and practitioner attribution from the record's metadata.

DGL practitioners and consultants are users in the DGL system with names, specialisms, and email addresses. FlitStack resolves DGL practitioner records against Pipedrive users by email match. Unmatched practitioners are flagged before migration — the team either creates Pipedrive user accounts first or assigns their records to a fallback Pipedrive user so no appointment or note is orphaned.

DGL's billing module generates invoices with insurer submission status, shortfall amounts, and payment records. Pipedrive has no native billing object. FlitStack maps paid invoice amounts to Deal records with the Organisation as the linked account, and stores the outstanding shortfall, insurer name, and submission status as custom fields on the Organisation. This gives the billing history visibility within Pipedrive without requiring a separate accounting tool.

DGL generates Word-based correspondence letters linked to patient records. FlitStack migrates the letter content as a Note on the Person record with a Correspondence_Letter__c custom flag set to true, preserving the original letter date. For letters with attachments, the attachment is re-uploaded as a Pipedrive File linked to the Person. Very large attachments (over 25MB) are flagged for chunked upload.

DGL supports custom fields for referral source, clinical procedure codes, insurance scheme, and patient risk flags. Pipedrive requires these to be created as custom fields before migration. FlitStack creates the matching Pipedrive custom fields (text, numeric, or single-select per DGL's field type) and maps values field-by-field during import. Pipedrive's hash-key custom field naming is handled internally — the mapping document references DGL field names for clarity.

DGL stores insurer name, policy number, and coverage type per patient. FlitStack splits this: insurer name and address become a separate Organisation record (representing the insurer), and policy number plus coverage type become custom fields on the Person record. The Person is linked to the insurer Organisation via a custom relationship field for reporting on insurer distribution.

DGL's e-prescribing module records prescriptions issued during consultations. Pipedrive has no prescribing or pharmaceutical data construct. FlitStack migrates e-prescription records as Notes on the Person record with a Prescription flag, preserving the medication name, dosage, and issue date. Clinical teams should verify whether prescribing data requires separate PHI compliance handling in Pipedrive.