Migrate from Teleos to Nutshell

Teleos guardian records containing client name, email, phone, and address information map directly to Nutshell Person fields using standard field mapping. Guardian IDs from Teleos are stored as Nutshell custom fields (Guardian_ID__c) to maintain traceability back to the original Teleos source record, enabling data validation and supporting delta-sync operations during migration.

Guardian address components including street address, city, postcode, and country map directly to Nutshell Person address fields using standard field correspondence. Multi-line addresses are automatically parsed during the migration load process and assigned to the correct Nutshell address sub-fields (address, city, state, postalCode, country), ensuring proper formatting and geocoding capability in the destination system.

Teleos animal records have no direct Nutshell equivalent, requiring a custom mapping approach. We map animals to People records with species, breed, date_of_birth, weight, and medical_history stored as Nutshell custom fields. The primary guardian relationship is preserved through a custom Guardian_ID__c field linking each animal to its owner. Practices that treat animals as business entities can alternatively map them to Companies instead for scenarios involving breeding operations or animal-related businesses.

Teleos links each animal to one or more guardians, creating a one-to-many relationship between animal records and their owners. In Nutshell, the primary guardian becomes the primary Person record linked to the animal. The guardian relationship is captured via a custom Person field (Primary_Guardian_ID__c) that stores the guardian's Nutshell Person ID, enabling bidirectional lookup between animal records and their associated guardians. Additional guardian relationships beyond the primary are stored in secondary custom fields for post-migration reconciliation by the practice team.

Teleos appointment records containing date, time, veterinarian, species, reason, and status map to Nutshell Tasks or Events depending on the appointment type. Appointment-specific details including appointment type, veterinarian name, species, and reason are stored as custom fields on the Activity record to preserve clinical context. The appointment status (Scheduled, Completed, Cancelled, No-show) maps directly to Nutshell Task status values for proper workflow tracking and calendar synchronization after migration.

Teleos prescription records containing drug name, dosage, frequency, start_date, end_date, and prescribing veterinarian are stored as custom fields on a Task-type Activity linked to the animal's Person record. Each prescription becomes a separate Task to maintain the one-to-one relationship with clinical documentation. Multi-drug prescriptions where an animal has multiple medications are serialized into a single custom text field with drug names, dosages, and frequencies formatted for readability and future reference by the veterinary team.

Teleos invoices, line items, payment status, and amounts have no Nutshell equivalent. We preserve invoice data as a custom Activity with invoice_number, amount, payment_status, and line_items as custom fields — suitable for reporting but not for accounting reconciliation in Nutshell.

Teleos treatment plans contain procedure names, scheduled dates, costs, and outcomes. We migrate these as custom field groups on the animal's Person record — plan name, procedure list, status, and cost totals are mapped to custom fields; detailed steps are preserved as a custom text block.

Any Teleos custom property defined on animal records—such as insurance_policy_number, microchip_id, vaccination_status, or breeder information—is re-created as a Nutshell Person custom field before migration begins. This ensures all custom data elements are available in Nutshell's schema before record loading starts. Pick-list values and dropdown options in Teleos are mapped to Nutshell choice-type custom fields with corresponding allowed values, preserving the original data structure and enabling filtering and reporting capabilities in the destination system.

Teleos custom fields defined on guardian records—such as billing_preferences, referral_source, marketing_opt_in, or practice_notes—are re-created as Nutshell Person custom fields prior to data migration. Fields that contain free-form text content are converted to Nutshell text custom fields to preserve the complete original text. Structured values like dropdown selections, boolean flags, or numeric data become Nutshell choice-type custom fields or appropriate field types to maintain data integrity and enable filtering, segmentation, and reporting in Nutshell's CRM environment.

Teleos user accounts representing veterinarians, veterinary technicians, and administrative staff map to Nutshell Users representing team members who will access the CRM. FlitStack AI resolves each Teleos user by matching their email address against existing Nutshell users in the destination account. Unmatched users are flagged in a pre-migration resolution report so the practice team can create Nutshell accounts first or assign their Teleos records to a fallback Nutshell user before the migration run executes, preventing data loss for unmapped user references.