Migrate from Teleos to Pipedrive

Teleos contacts with a primary organization link become Pipedrive persons linked to the migrated organization record. The contact's name, email, phone, and address fields map directly to Pipedrive person fields. FlitStack resolves the OrganizationId reference after the Organizations load completes.

FlitStack extracts Teleos contacts that lack a primary organization link and inserts them as unlinked Pipedrive persons. The migration preserves all standard fields (name, email, phone) while flagging each record with a custom Teleos_ID__c for later reconciliation. The customer's admin can then decide to attach these persons to a default organization in Pipedrive, or keep them standalone for reporting purposes.

Each Teleos organization is created as a Pipedrive organization, copying name, address, website, and industry fields directly. FlitStack maps the domain field to Pipedrive’s domain attribute for duplicate detection. Where Teleos records a parent–child relationship, the child organization’s parent_id is set to the migrated parent’s Pipedrive ID, preserving the original hierarchy within the new CRM.

FlitStack loads each Teleos deal into Pipedrive as a deal record, copying title, value, expected close date, and owner reference. The Teleos stage label is mapped to the Pipedrive stage ID, and probability is set per the schema plan. Custom fields on the Teleos deal become Pipedrive custom fields and are populated during the load. Deal–person and deal–organization links are resolved after the related entity loads to preserve referential integrity.

Teleos deal stage labels are translated to Pipedrive stage names on a per‑pipeline basis, using the mapping defined during schema setup. For each stage, FlitStack assigns the corresponding Pipedrive probability percentage and forecast category, ensuring that reporting and AI forecasting reflect the original pipeline logic. If a Teleos stage has no exact Pipedrive counterpart, the admin selects a fallback stage or creates a new one before migration.

Teleos patient records do not have a Pipedrive native equivalent. Patient name, species, breed, medical notes, and vaccination history are stored as Pipedrive custom fields on the linked person record. If a Teleos contact has multiple patients, additional records are appended as JSON text in a designated custom field.

Teleos logged calls, emails, and meetings migrate as Pipedrive activities with original timestamps, subject, and owner attribution preserved. Pipedrive's API restricts export of activities from inactive users — FlitStack flags any gaps and migrates as much as the API permits.

FlitStack loads each Teleos note as a Pipedrive note attached to the matching person, organization, or deal record. The original HTML or rich‑text content is stored in Pipedrive’s content field without transformation. Author name and creation timestamp are written to Pipedrive’s user_id and add_time fields; if the author lacks a Pipedrive account, the note is attached to the service user and flagged for review. Teleos note attachments are not transferred.

FlitStack imports Teleos products and services as Pipedrive products, preserving the name, unit, pricing, and description fields. If Teleos stores a product code or tax rate, those values are saved to Pipedrive custom fields on the product record. When a Teleos deal references a product, FlitStack creates a deal‑product entry in Pipedrive linking the deal to the migrated product, and the quantity and price are copied from Teleos.

Any Teleos custom property — text, number, date, pick-list, or multi-select — is replicated as a Pipedrive custom field on the equivalent entity (Person, Organization, or Deal). Pipedrive assigns a 40-character hash key; FlitStack documents the mapping for API reference.

FlitStack converts each Teleos appointment into a Pipedrive meeting activity, copying the start time, end time, location, and duration. The Teleos practitioner is set as the Pipedrive activity owner (matched by email). Appointment type, notes, and any custom fields are stored on the linked person record using dedicated Pipedrive custom fields. If the appointment recurs, FlitStack creates a series of Pipedrive meetings and links them to the same person.

Teleos owners and practitioners are resolved by email match against Pipedrive user accounts. FlitStack creates a mapping table and flags any Teleos owner without a Pipedrive user account for the customer's admin to provision before migration or assign to a fallback user.