Migrate from Zedmed to Salesforce Sales Cloud

Every Zedmed patient record becomes a Salesforce Contact. Medicare number, DVA number, and concession-card details migrate as custom fields on the Contact. Patient date of birth, address, and emergency contact details map directly to standard Salesforce Contact fields. The original Zedmed patient ID is stored in Source_System_ID__c for delta-run de-duplication.

Zedmed practitioners and referring doctors map to Salesforce Contacts with a Practitioner_Type__c custom pick-list field to distinguish GPs, specialists, and allied-health providers. Their Medicare Provider Numbers migrate as a custom text field (Provider_Number__c) used for billing traceability in Salesforce. Referring doctor details also populate the Related_Referral_Partner__c lookup field for referral tracking.

The Zedmed practice or clinic organisation maps to a Salesforce Account record. Multi-clinic practices use Salesforce's Parent Account field to establish a hierarchy matching Zedmed's location structure. Practice-level billing configuration (TYRO terminal settings, Medicare location IDs) migrates as custom fields on the Account.

Zedmed appointments with a status of 'Completed' map to Salesforce Tasks with Type='Appointment'. Future appointments map to Salesforce Events with the original start/end times preserved as Event Start and Event End. The appointment type (standard, telehealth, procedure) maps to a custom pick-list on the Task or Event record.

Zedmed billing records — item codes, fee levels, bulk-billing flag, payer type, and derived item logic — do not map to any standard Salesforce object. We create a Practice_Billing_Record__c custom object with a lookup to Contact (patient) and Account (practice). Each record stores Medicare item code, MBS fee amount, payer type (Medicare/DVA/WorkCover/TAC/health fund), and bulk-billing flag as custom fields.

Zedmed SmartForms and clinical note bodies export as RTF files. FlitStack converts RTF to plain text or Salesforce ContentNote (Lightning Experience compatible) and attaches each note to the corresponding Contact record. Complex RTF formatting that cannot be auto-converted is flagged for manual review post-migration.

Zedmed payer configurations (health fund IDs, WorkCover insurer IDs, TAC details, DVA contract numbers) map to a Payer_Config__c custom object linked to the Account. Fee schedules and item-level adjustments per payer are stored as related records on the Payer_Config__c object for auditability.

Zedmed's ZedSMS appointment reminders and SMS confirmation logs have no direct Salesforce equivalent. We preserve reminder logs as a custom Reminder_Log__c object linked to the Contact and original Event, storing the SMS sent datetime, message type, and patient confirmation status for continuity in patient communications.

Electronic prescriptions and referral letters in Zedmed migrate as Salesforce Files (ContentDocument/ContentVersion) attached to the Contact. The referral type (specialist referral, imaging referral, pathology referral) and expiry date store as custom fields on a Referral__c custom object linked to the Contact record.

Zedmed's HealthLink-integrated pathology and imaging results become Salesforce Custom Object records (Result__c) linked to the Contact. The result type, ordering practitioner, result status, and received date store as custom fields. PDF result files attach as Salesforce Files to the Result__c record.

Zedmed practitioner users resolve to Salesforce Users by email address match. Where a Zedmed practitioner does not have a corresponding Salesforce user licence, their records assign to a fallback practitioner owner flagged before migration. Unmatched owners are reported to the practice manager before the full run commits.

Files and attachments stored against any Zedmed record — patient documents, scanned consent forms, exported clinical letters — re-upload to Salesforce as ContentVersion records. They link to the corresponding Contact or custom object via ContentDocumentLink. File size limits follow Salesforce's 25 MB per ContentVersion.