Migrate from Pulse Digital Clinic to Twenty CRM

Pulse Digital Clinic patient records map directly to Twenty's People object. Patient name, date of birth, contact information, address, and medical history fields migrate as standard and custom fields on the People record. Source system patient ID is stored as Source_System_ID__c for delta-run de-duplication.

Pulse Digital Clinic stores the primary clinic name and location data. This maps to Twenty's Companies object as the clinic's organizational record. If Pulse Digital Clinic tracks referring partner clinics as separate entities, each becomes a distinct Company record in Twenty.

Pulse Digital Clinic appointment records (date, time, physician, patient, type, status) transform into Twenty Tasks linked to the corresponding People record. The appointment type maps to Task type, and the physician-assigned owner resolves by email match against Twenty Workspace Members.

Pulse Digital Clinic physician profiles (name, specialty, credentials) do not have a direct equivalent in Twenty's user model. We migrate physician identity as a custom field on People records and create a physician lookup field so patients can be linked to their primary physician without creating duplicate user accounts.

Pulse Digital Clinic billing records (amount, status, payment date, insurance provider) have no native equivalent in Twenty CRM. We create a custom BillingLedger object with fields for amount, status, payment_date, insurance_provider, and patient_link. Invoicing functionality must be rebuilt in a separate billing tool post-migration.

Pulse Digital Clinic e-prescription records (medication, dosage, prescriber, date) have no clinical field type in Twenty CRM. We store prescription history as a multi-line text or JSON-formatted custom field on the People record. Clinical e-prescribing workflows must be handled by a dedicated healthcare tool post-migration.

Pulse Digital Clinic chat and messaging history linked to patient records migrates as Twenty Notes attached to the corresponding People record. Original timestamps and sender identity are preserved. Messaging is not a native Twenty object — notes capture the content and metadata.

Pulse Digital Clinic campaign management tracks patient outreach and health-awareness campaigns. Twenty CRM has no native campaign object. Campaign membership data migrates as a custom pick-list field on People; campaign content and scheduling notes migrate as attached Notes. Outbound campaign automation must be rebuilt in Twenty's workflow builder or an external marketing tool.

Pulse Digital Clinic intake form fields (emergency contact, insurance details, consent status, referral source) have no native equivalent in Twenty's People object. We create custom fields for each intake attribute. Referral source maps to a custom pick-list field for downstream reporting.

Pulse Digital Clinic stores individual visit records with date, physician, diagnosis codes, and notes. We merge visit history into Notes attached to the People record and surface key clinical flags (chronic conditions, allergies) as custom fields. Detailed diagnosis coding requires a custom object or external EMR integration.