Migrate from Zedmed to Pipedrive

Zedmed patient demographics (name, date of birth, contact phone, Medicare number as custom field) map directly to Pipedrive Person fields. Date of birth migrates as a custom date field since Pipedrive has no native DOB. Medicare number, concession status, and healthcare card number migrate as custom fields on the Person record for reference.

Street address, suburb, state, and postcode from Zedmed patient records map to Pipedrive Person address fields. If the patient has multiple addresses recorded in Zedmed, the residential address maps as primary; postal address maps to a secondary address field or custom field depending on plan.

Zedmed stores emergency contact name and phone separately from the patient record. FlitStack maps these to Person custom fields (Emergency_Contact_Name__c, Emergency_Contact_Phone__c) so the information stays attached to the patient Person in Pipedrive for front-desk reference. This ensures administrative staff can retrieve emergency contact details quickly without accessing the clinical system, supporting streamlined patient intake and emergency protocols.

Zedmed practice or clinic records (name, address, phone, provider number) map to Pipedrive Organizations. The practice name becomes Organization name. Provider number and location-specific details migrate as custom fields. If the practice has multiple practitioners, each practitioner-Patient record links to the Organization.

Zedmed practitioner records (provider name, AHPRA registration, specialty) map to Pipedrive Persons flagged as practitioners. The practitioner name, specialty, and contact details migrate as Person fields; AHPRA number and provider number migrate as custom fields. Practitioners are linked to the Practice Organization.

Zedmed appointment records (date, time, type, practitioner) cannot map directly to Pipedrive deals or activities because Pipedrive has no appointment scheduling module. FlitStack creates Activity Tasks representing past appointments with subject, date, and practitioner name for historical reference. Future appointments require Pipedrive's calendar integration or a scheduling add-on.

Free-text clinical notes attached to Zedmed patient records migrate as Pipedrive Notes linked to the Person record. Note content is preserved verbatim. Any formatting from Zedmed's WP Templates (RTF format) is stripped to plain text during migration. Clinical notes are imported after Persons so the parent link resolves correctly.

Zedmed billing items (MBS item codes, private fees, payer types) associated with a patient encounter cannot map to Pipedrive Deals because there are no native Zedmed deals. FlitStack creates Person-level custom fields (Last_Billing_Item__c, Payer_Type__c, Concession_Status__c) to preserve billing reference data for front-desk and administrative staff.

Zedmed payer records (Medicare, DVA, TAC, WorkCover, health fund) are mapped as custom pick-list fields on Pipedrive Person (Primary_Payer__c, Secondary_Payer__c). Each payer type is preserved as a value so staff can filter Pipedrive views by patient payer category without accessing Zedmed.

Zedmed recall records for follow-up appointments migrate as Pipedrive Activity Tasks with a due date and subject indicating the recall type (e.g., 'Recall: Cervical Screening'). Active recalls map as open tasks; completed recalls map as completed tasks with the completion date preserved.

Patient referral letters and specialist referrals stored in Zedmed migrate as Notes on the Person record. Referring practitioner name and referral expiry date migrate as custom fields (Referrer_Name__c, Referral_Expiry__c) so sales or admin staff can track referral validity in Pipedrive without opening Zedmed.

Zedmed clinical templates and SmartForms used for structured clinical data collection have no Pipedrive equivalent. These must be recreated manually as Pipedrive Smart Docs templates or external document tools. FlitStack exports template field definitions as a reference document for your Pipedrive admin.