Migrate from Pulse Digital Clinic to monday CRM

Pulse Patient maps to a Monday CRM Contact for name/email/phone and to an Item on a dedicated Patient Board for medical fields (blood type, allergies, DOB). Monday Contacts hold the standard Person columns; the Patient Board holds healthcare-specific columns as custom fields.

Pulse assigns a numeric patient_id per record. Monday CRM has no native patient-ID field. We create a Text column (pulse_patient_id__c) on the Patient Board to store the original Pulse ID for traceability and de-duplication. This column persists on every patient item as a read-only identifier that references the source Pulse system for data integrity across the migration.

Pulse Physician maps to a Monday CRM Contact (Person type) so they appear in the Person column on appointment items. A Doctor Board holds physician-specific columns: specialty, years_of_experience, and license_number as custom fields. Each physician record maintains a pulse_doctor_id__c column linking back to the source Pulse physician identifier for cross-system reference.

Pulse Appointments become Items on a dedicated Appointment Board. Each Item links to the Patient and Doctor via Monday's Person column. Date and time store as Date/Time columns; visit_type, status, and notes map to custom Status and Text columns on the item.

Pulse billing entries (total_amount, amount_paid, payment_status, amount_remaining) map to Items on a Monday Deals board. Amount fields use Numbers columns. payment_status maps to a Status column with values matching Pulse's pick-list (Paid, Pending, Overdue, Refunded). The Deals board replaces Pulse's billing module since Monday has no native billing entity.

Pulse prescriptions (medication, dosage, frequency, start_date, end_date) migrate as Items on a Prescription Board. Medication and dosage use Text columns; frequency and dates use Status and Date columns. If prescriptions are many-per-patient, they become Sub-items under the patient item on the Patient Board.

Pulse insurance fields (provider_name, policy_number, group_number) have no Monday CRM equivalent. They become custom Text columns on the Patient Board linked to each patient item. Insurance lookup is manual — Monday does not support a native insurance entity. Each insurance column is created as a custom field before migration so the board schema accepts the incoming data without validation errors.

Pulse diagnosis fields (diagnosis_code, diagnosis_description, medical_history_summary) migrate as custom Text columns on the Patient Board. Multi-value history entries use Sub-items on the patient item so each condition is a separate row with its own date and status. This structure preserves the longitudinal nature of medical records while fitting Monday's hierarchical item model.

Pulse's multi-location capability maps to Monday Groups within each board (e.g., Group by clinic name on the Patient Board). Each Group scopes its items to one location, preserving data locality without requiring a separate board per clinic. Group-level filtering in Monday allows administrators to view patients or appointments per location without switching boards.

Pulse file attachments (lab results, imaging, consent forms) are downloaded and re-uploaded to Monday Files attached to the relevant patient item. Monday's file storage limits apply per plan (5 GB Basic, 20 GB Standard, 100 GB Pro, unlimited Enterprise). Large imaging files may require compression before upload to stay within plan storage quotas.

Pulse's created_by and assigned_to fields resolve by email match against Monday CRM users and populate the Person column on each item. Unmatched owners are flagged pre-migration so your team can either invite them to Monday or assign a fallback user before the run.

Pulse automations (appointment reminders, billing alerts, follow-up sequences) have no Monday CRM equivalent and must be rebuilt manually. We export Pulse workflow definitions as a JSON reference document your team can use to configure equivalent Monday automations post-migration. Monday's automation engine uses recipes with triggers and actions that differ fundamentally from Pulse's event-based sequences, so each workflow requires manual reconstruction in the Monday recipe builder.