Migrate from ClientTether.com to Pipedrive

ClientTether Contacts map directly to Pipedrive Persons. The ClientTether contact record carries name, phone, email, company association, and communication history. We export all standard contact fields and associated tags during migration. The ClientTether contact.phone property maps to Pipedrive's phone field, contact.email to email, and contact.firstname/lastname to name fields split on the source full name. Tags on Contact migrate to Pipedrive Person custom fields (multi-select or label-based) or to Activity tags depending on the customer's preferred organization strategy.

ClientTether Leads are generated through web forms, IVR, or CSV import and flow into pipeline stages. We preserve lead source attribution and the originating form or campaign ID as custom fields on the Pipedrive Lead. The ClientTether lead status and pipeline stage assignment map to Pipedrive Lead status values that we configure during schema setup. Any lead routing rules (FSO assignment, franchise owner assignment) are preserved as custom fields and manual assignments noted for the customer's admin to re-implement in Pipedrive automation if needed.

ClientTether Accounts group Contacts under franchisee or franchise owner entities. The account hierarchy — brand account, franchise owner account, FBC structure — is exported as a flat list with parent-child relationship flags. We map each ClientTether Account to a Pipedrive Organization, preserving the account name and any custom fields. Parent-child hierarchy depth is flattened into a naming convention or custom fields (parent_account_name, hierarchy_level) since Pipedrive Organizations do not support multi-level nested hierarchy beyond a single parent link. We flag any depth exceeding three levels for manual review.

ClientTether Pipelines map to Pipedrive Pipelines with customizable stage names and ordering. We preserve stage names, positions, and the deals associated with each stage. Pipedrive supports multiple pipelines at all paid tiers, which accommodates ClientTether's multi-brand pipeline structure. Each ClientTether pipeline becomes a separate Pipedrive pipeline, and stage names are mapped one-to-one with probability percentages approximated to Pipedrive's integer stage weights.

ClientTether Proposals carry template-based content, pricing, start/end dates, and optionally link to Work Orders. We export proposal body text and line items as Deal details and custom fields. Rich template formatting may require re-rendering at the destination; we flag proposals with non-standard template elements for manual review before final import. Pipedrive's Smart Docs add-on (included on Premium and Ultimate) provides a proposal-building interface that the customer's team uses post-migration to recreate formal proposal documents from the migrated deal data.

ClientTether Work Orders reference Proposals and carry operational data for franchisee execution. We export Work Order records including linked proposal dates, status, and assigned franchise owner. Work Orders map to Pipedrive Deals with a custom Work_Order__c field carrying the original ClientTether Work Order ID, or to Activities (Tasks) if the customer prefers to track work order status as task completions rather than deal updates. The mapping choice is made during scoping based on how the customer uses Work Orders in their franchise operations.

ClientTether Tags are used as both segmentation markers and automation trigger conditions on Contacts, Leads, Accounts, and Workflow records. We export all tag assignments per record and map them to Pipedrive Labels on Person and Organization records. Tags used for automation trigger logic are flagged in the automation inventory document for rebuild in Pipedrive's automation builder. The customer chooses during scoping whether tags that functioned as trigger conditions should become Pipedrive labels (for segmentation) or custom field values (for filtering and automation).

ClientTether Email Sequences are time-triggered drip campaigns attached to Leads or Contacts. We export sequence step content, timing delays, and enrollment status. Pipedrive's Campaigns feature (an add-on at all tiers) handles email drip sequences, but it is a different cadence model from ClientTether's automation-based sequences. We deliver the sequence content and step structure as a written document so the customer's admin can reconstruct the cadence in Pipedrive Campaigns or a third-party sales engagement tool if preferred.

ClientTether inbound and outbound call records are automatically logged with duration, direction, and linked Contact. We export call metadata including missed-call follow-up task generation and map to Pipedrive Activities with the Call subtype. Call duration, direction (inbound/outbound), and disposition migrate to custom Activity fields. Activity timestamps are preserved to maintain the chronological call history against the correct Person record.

ClientTether custom fields on Contacts, Leads, Accounts, Proposals, and Work Orders are enumerated during discovery with their field types and picklist options. We map them to Pipedrive custom fields on Person, Lead, Organization, and Deal objects. Pipedrive supports string, number, date, datetime, single-select, multi-select, phone, email, URL, and address custom field types. Any field type that does not have a direct Pipedrive equivalent is flagged during discovery for the customer to choose a closest-available Pipedrive type or to store as a text field with original values preserved.

ClientTether user records include name, role, and assignment of Leads and Tasks. We export the user roster including any FSO or franchise owner role assignments. Users are matched to Pipedrive Users by email. Open tasks assigned to a ClientTether user are reassigned to the corresponding Pipedrive user during migration. Any ClientTether user without a matching Pipedrive user account goes to a reconciliation queue for the customer's admin to provision before migration continues.

ClientTether email engagement records (sent, opened, clicked, replied) are exported with content, timestamp, and linked Contact. We map them to Pipedrive Activities linked to the Person record. Email content is stored as Activity description or notes depending on the customer's preferred storage model. Engagement metadata (open count, click count) is preserved in custom Activity fields since Pipedrive does not natively track email engagement metrics on Activities.