Migrate from Teleos to Freshsales

Teleos clients map directly to Freshsales Contacts. The client name splits into FirstName and LastName on the Contact record. Email, phone, address, and billing contact fields map to their Freshsales equivalents. If the client record contains both a home and mobile phone, the secondary maps to Contact.secondary_phone__c.

Street, city, state, postal code, and country on the Teleos client record map to Freshsales Contact address fields. Multiple address types (billing vs. shipping) stored in Teleos collapse to the primary address on the Freshsales Contact; the secondary address type is stored in a custom field if needed.

Teleos patients have no Freshsales native equivalent. We create a Patient__c custom object linked to the Contact record via a lookup field (Client__c). Species, breed, date of birth, weight, microchip number, and insurance policy number become custom fields on Patient__c. Medical history and vaccination records are stored as formatted text fields or linked Notes attachments.

Teleos appointments carry patient, veterinarian, procedure type, and clinical notes. These map to Freshsales Events (for scheduled appointments with start/end times) or Tasks (for follow-up items). The patient context is preserved via the Patient__c lookup on the Event or Task record. Veterinarian assignment resolves by email match to Freshsales users.

Teleos prescriptions — medication name, dosage, frequency, start and end dates, refills remaining, and prescriber — become a Prescription__c custom object linked to the Patient__c record. We preserve the original prescription date as a custom datetime field since Freshsales has no native prescription entity.

Teleos invoices with line items, totals, payment status, and due dates become an Invoice__c custom object linked to the Contact record. Invoice line items are stored as a long-text custom field in JSON format for reference, since Freshsales has no native invoice line-item table. Payment status maps to a custom pick-list field.

Teleos treatment plans with procedure list, estimated cost, and status become a Treatment_Plan__c custom object linked to the Patient__c record. The plan narrative is stored as a formatted Notes attachment since Freshsales does not have a native clinical plan object.

Vaccination records — vaccine name, batch number, administration date, next due date, and administering staff — map to a Vaccination__c custom object linked to Patient__c. Next-due dates are preserved as custom date fields to support reminder workflow rebuilding in Freshsales.

Teleos product catalog items including medications, vaccines, and consumables map to Freshsales Product2 records. The product name, unit price, and description field transfer directly. Teleos stock quantity and reorder thresholds map to a custom Number field (Stock_Quantity__c) on Product2 since Freshsales Products do not natively track inventory levels or generate low-stock alerts.

Teleos staff and veterinarian accounts resolve against Freshsales users by email match. If a Teleos staff member has no Freshsales user account, their records are assigned to a fallback owner and flagged for review. Teleos staff roles do not map to Freshsales profiles — those permissions are configured independently in the destination account after migration.

Teleos appointment reminders, prescription renewal alerts, and vaccination reminders have no Freshsales native equivalent. We export the Teleos workflow definitions as a structured reference document so your Freshsales admin can rebuild the logic using Freshsales Workflows on Pro/Enterprise plans. Each automation trigger and condition is documented for manual recreation.

Teleos document attachments such as consent forms, lab results, and imaging files are re-uploaded to Freshsales Files and linked to the parent Contact or Patient__c record. File size limits from Freshsales apply; files exceeding 25MB are flagged for chunked upload or alternative storage with a reference link stored in Freshsales.