Migrate from Teleos to Twenty CRM

Teleos animal-to-owner N:N relationship collapses to 1:N in Twenty's Pet custom object

Teleos allows a single animal record to be linked to multiple owners (e.g., co-owners or a primary owner plus an emergency contact). Twenty CRM's relation model on custom objects supports one-to-many rather than many-to-many natively. We handle co-owner scenarios by creating one primary People record as the primary owner link and surfacing secondary owners in a custom text field or note. Your admin decides whether to create separate People records for co-owners and link them via a junction table if both-owner relationship integrity is required.

Teleos API rate limits may restrict bulk export window for large clinics

Teleos's business-tier API imposes per-minute and per-day request limits that affect how quickly we can extract records during the migration window. For clinics with 10,000+ records (animals, visits, invoices), we implement a pagination strategy with rate-limit-aware throttling using the Retry-After header. Export jobs exceeding Teleos's daily quota are split across multiple sessions. This adds 4–8 hours to the extraction phase and is reflected in the project timeline before validation begins.

Twenty CRM CSV import requires fields to exist before import — custom objects must be created first

Twenty's CSV import creates records but not fields — this is explicitly documented in Twenty's import guide. If your Teleos instance uses custom fields beyond the standard animal and owner fields, your Twenty admin must pre-create those fields in Settings → Data Model before we run the import. We deliver a field-creation checklist with exact field names, types, and pick-list values so your admin can configure the schema before data lands. Failure to pre-create fields results in those columns being silently ignored during import.

Vaccination and prescription alerts require manual rebuild in Twenty's workflow builder

Teleos's built-in vaccination-due reminders and prescription-renewal notifications are automation rules that have no equivalent in Twenty CRM's migration scope. Once custom objects Pet and Vaccination are created in Twenty, your admin can build workflow triggers using Twenty's Organization-tier workflow builder (e.g., 'Vaccination nextDueDate is in 7 days → create Task for People record'). We export a machine-readable JSON of Teleos workflow definitions as a rebuild reference. The automation rebuild typically takes 4–8 hours for a clinic with 3–5 active alert rules.

Teleos date-of-birth and weight fields need type validation before mapping

Teleos instances with long usage histories sometimes store dates in mixed formats (DD/MM/YYYY vs MM/DD/YYYY) and weights in mixed units (kg vs lbs). We run a pre-migration type audit that flags records with inconsistent date formats and non-numeric weight values. These are corrected against the clinic's documented locale settings before mapping to Twenty's date and number fields. Unresolved date ambiguity results in null values for those specific records — flagged in the reconciliation report.