Migrate from Teleos to Zoho CRM

Teleos client records migrate as Zoho Contacts. The primary pet associated with the client is stored in a custom field (Primary_Pet__c) since Zoho does not have a native pet object. Client phone, email, address, and job title fields map directly to Zoho Contact standard fields.

If Teleos distinguishes between referring veterinarians (business leads) and pet-owner clients, referring vets with no active treatment plan route to Zoho Leads while active pet-owner clients land in Contacts. This split is defined by a Teleos custom status field or by the presence of a linked Treatment_Plan record.

Teleos businesses, referring clinics, and vendor practices map to Zoho Accounts. Zoho Account.Name is the primary field; Industry defaults to 'Veterinary' for clinic-type records. If Teleos stores a clinic hierarchy (parent practice with satellite locations), the parent-child relationship maps to Zoho Account.Parent_Account.

Teleos treatment plans with an open status migrate as Zoho Deals. The Teleos plan name becomes Deal_Name, the estimated cost maps to Amount, and the plan stage maps to the Zoho Deal Stage pick-list. Stage names are mapped value-by-value; plans without a named stage default to Zoho's 'Qualification' stage.

Teleos appointments migrate as Zoho Events with Subject = appointment type (e.g., 'Annual Exam', 'Vaccination'), Start_DateTime and End_DateTime from Teleos slot times, and OwnerId resolved by email match to Zoho users. Recurring appointments are written as individual Event records in Zoho.

Teleos treatment logs and clinical notes migrate as Zoho Tasks linked to the patient Contact record. Subject pulls from the Teleos log type (e.g., 'Vaccination Administered', 'Prescription Filled'), and the full clinical note text goes into Task.Description. Original log date and staff owner are preserved.

Teleos inbound and outbound client calls become Zoho Tasks with Task.Subject = 'Client Call', Task.Type = 'Call', and duration captured in a custom field. Call outcome (left message, spoke with client) migrates as a pick-list value in a custom field on the Task.

Every Teleos custom field not represented in Zoho standard fields is created as a Zoho Custom Field under the appropriate module (Contacts, Accounts, Deals). API names follow Zoho's uppercase-underscore convention (e.g., Rabies_Vaccination_Date__c). Pick-list custom fields in Teleos replicate their values in Zoho pick-list setup.

Teleos subforms — such as line items within a Treatment Plan (services, medications, dosages) — cannot map 1:1 to Zoho because Zoho subform support is module-restricted. FlitStack creates a custom module named 'Treatment_Plan_Line_Items' and stores each row as a record linked to the parent Deal via a lookup field. The parent deal is identified by a cross-reference stored in a custom field during migration.

Vaccination schedules in Teleos subforms — with rows for each vaccine, due date, and administration status — migrate to a 'Vaccination_Record' custom module linked to the patient Contact. Administered vaccines carry a status of 'Complete' and due vaccines are flagged 'Pending' so Zoho users can run workflow reminders on the pending set.

Teleos files attached to patient records (lab results, imaging, consent forms) are re-uploaded as Zoho Attachments linked to the corresponding Contact or Deal record. Zoho's 25MB per-file limit applies; files exceeding this are flagged for manual download and re-upload by the client.

Teleos staff who created or own records are resolved by email match against Zoho CRM users. Unmatched staff are flagged before migration so the client can either invite them to Zoho or assign their records to a fallback Zoho user. No record lands without a resolved OwnerId.