Migrate from Panacea to Twenty CRM

Panacea's client owner (the person who brings an animal in for care) maps directly to Twenty's People object. The owner's name, email, phone, address, and contact preferences migrate as standard People fields. Panacea owners without a company affiliation land as standalone People records in Twenty.

Panacea's patient animal has no direct Twenty CRM equivalent — Twenty's standard objects are People, Companies, and Opportunities. We create a custom Patient object in Twenty's Data Model with fields for species, breed, date of birth, weight, vaccination status, and medical history. The Patient object links to the owner via a relation field pointing back to the People record.

Panacea client owners can be linked to a company (e.g., a farm for livestock clients, a breeding kennel, or a corporate pet-insurance partner). Where a Panacea owner has a company affiliation, that company migrates as a Twenty Companies record with name, domain, industry, and employee count fields populated from Panacea's business entity data.

Panacea appointment records (date, time, duration, type, assigned veterinarian) translate into Twenty Tasks. The task subject carries the appointment type and patient name; the scheduled date maps to the Task due date; the assigned veterinarian resolves to a Twenty Workspace Member by email match. Completed appointments carry the original completion timestamp as a custom field.

Panacea treatment records and clinical notes attach to the patient. We migrate these as Twenty Notes linked to the Patient custom object record. The original note timestamp, author (veterinarian), and note type (diagnosis, prescription, surgery) are preserved as Note metadata and custom fields. Rich-text formatting is retained where Panacea exports it.

Panacea invoice records do not have a native destination in Twenty's standard CRM model. We create a custom Invoice object in Twenty with fields for invoice number, date, total amount, amount paid, balance outstanding, payment status, and a relation to the People (client owner) record. Payment line items migrate as child records under the Invoice object where Twenty's data model supports that relationship.

Vaccination history attached to a patient animal migrates as a custom Vaccination object linked to the Patient record. Fields include vaccine name, date administered, due date for next dose, batch number, and administering veterinarian. This preserves the regulatory vaccination record independently from clinical notes.

Panacea file attachments (lab results, consent forms, radiograph images, insurance documents) are downloaded from Panacea's storage and re-uploaded to Twenty Files, then linked to the appropriate Patient or People record by ID. File size limits apply — files exceeding Twenty's upload threshold are flagged for manual re-upload with a reference link to the source.

Panacea staff records (veterinarians, technicians, front-desk staff) map to Twenty Workspace Members. Email addresses serve as the unique matching key. During migration, each Panacea staff member's ID is stored as Source_System_ID__c on the corresponding Twenty Workspace Member so appointment assignments resolve correctly without creating duplicate users.

Panacea product inventory used in treatments (medications, vaccines, retail items) migrates as a custom Product object in Twenty if the clinic wants to track supply usage alongside billing. Fields include product name, SKU, unit price, quantity on hand, and reorder threshold. This object is optional — only created when the source Panacea data includes inventory records.

Panacea reminder schedules (annual vaccination reminders, 6-month dental checkups, monthly heartworm prevention) have no direct equivalent in Twenty's workflow model. We export the reminder configuration as a reference document and create a custom recurring-note setup or a custom field on the Patient record storing the next reminder date. The actual automation must be rebuilt in Twenty's workflow builder.

Individual payments made against a Panacea invoice are migrated as Payment records linked to the corresponding custom Invoice object in Twenty. Each Payment carries the payment date, amount, payment method, and a reference back to the Invoice and People records.