Migrate from Teleos to HighLevel

Teleos stores client (owner) records as Contact objects. The name, email, phone, and address fields map directly to HighLevel Contact fields. Primary client identifier is preserved as Source_System_ID__c for delta-run de-duplication and audit traceability. This custom field ensures that any records modified in Teleos during the migration window can be matched and updated in HighLevel without creating duplicates.

Teleos animal records (patient name, species, breed, date of birth, weight, microchip ID) have no native equivalent in HighLevel's standard objects. We create a Patient custom object in HighLevel via POST /custom-objects and map each Teleos field to a corresponding custom field with appropriate data types (text, date, number).

Teleos treatment histories and case notes map to a Treatment custom object linked to the Patient custom object via a relationship field. Each treatment record preserves the procedure code, date, veterinarian name, notes, and outcome — migrated as separate object instances with parent link IDs resolved after Patient records land.

Teleos visit and appointment logs migrate as Visit records in a custom object. The visit date, time, duration, associated patient, and attending vet are mapped to custom fields. Note that Teleos calendar configuration does not transfer — calendar booking links must be rebuilt in HighLevel's Calendar module.

Teleos invoice records (invoice number, date, amount, payment status, line items) migrate to a custom Invoice object in HighLevel. Payment method and payment date are preserved. HighLevel Payments integration handles future billing post-migration — historical invoice PDFs are downloaded and reattached to the Invoice records.

Teleos flat tags on client and patient records map directly to HighLevel tags on the Contact object. Tags used for segmentation logic (e.g., VIP client, lapse risk, breed category) are also preserved as Custom Fields where the tag encodes a structured value rather than a simple label.

Teleos text notes attached to client or patient records migrate as HighLevel Notes linked to the Contact or Patient custom object. Note create date and author are preserved. Rich-text formatting in Teleos notes is flattened to plain text for HighLevel compatibility.

Teleos file attachments (vaccination certificates, consent forms, lab reports) are downloaded from Teleos storage and re-uploaded to HighLevel Files, linked to the relevant Contact or Patient record. File size limits and MIME-type restrictions follow HighLevel's file handling defaults. During the discovery audit, we identify all attachments and flag any that exceed the 25 MB per-file limit for chunked upload or compression before migration.

Teleos staff records used as veterinarian or technician assignments on cases map to HighLevel Users (for owner assignment) and also as Contact records (for staff directory visibility). Owner resolution is performed by email match against HighLevel user accounts. Staff records that cannot be matched by email are held in a staging queue and flagged for your team to either create a corresponding HighLevel user account or assign to a fallback user before the migration proceeds.

Teleos prescription records (medication name, dosage, frequency, start/end dates, prescribing vet) map to a Prescription custom object linked to the Patient record. Prescription status and refill history are preserved as pick-list fields in HighLevel. The prescribing veterinarian reference is resolved via email match to the corresponding HighLevel User, similar to the staff resolution process used for Treatment records.

Teleos appointment reminders and follow-up tasks map to HighLevel Tasks linked to the Contact or Patient. Task status, due date, and assigned user are preserved. Recurring reminder rules do not migrate — those must be rebuilt as HighLevel Workflow triggers.