Migrate from ClientTether.com to Freshsales

ClientTether Contacts migrate to Freshsales Contacts with name, phone, email, and address fields preserved. Communication history (SMS threads, email logs, call metadata) migrates as Activity records attached to the Contact. We resolve any duplicate Contacts by email dedupe key and flag duplicates for customer review before final import. Tags on Contact migrate to Freshsales custom fields (multi-select picklist) or Topics per customer preference during scoping.

ClientTether Leads (generated through web forms, IVR, or CSV import) migrate to Freshsales Leads with lead source attribution and originating campaign ID preserved. The lead status property maps to Freshsales Lead Status picklist values. If the customer converts Leads as part of their sales process, Freshsales applies the conversion mapping (Lead to Contact, Account, and Deal) per Freshsales' standard lead conversion workflow during migration validation.

ClientTether Accounts (franchisee entities, franchise owner accounts) migrate to Freshsales Accounts. The franchise hierarchy (brand account at top, franchise owner account below, FBC structure) exports as parent-Account relationships. Freshsales supports Account hierarchy up to three levels by default, which accommodates most franchise structures; we flag any depth that exceeds this limit and map the excess to sibling Accounts under a common parent.

ClientTether Pipelines with named stages map to Freshsales Deal stages in the visual pipeline view. Each stage name and probability percentage migrates to the corresponding Freshsales stage definition. The pipeline assignment on Deals maps to the Freshsales Deal's stage field; we configure stage values in the destination workspace before Deal import begins.

ClientTether Deals map to Freshsales Deals with stage, amount, expected close date, and owner preserved. The ClientTether deal owner maps to Freshsales Deal owner by email resolution. If ClientTether Deals link to Accounts, we resolve the AccountId before Deal import so the relationship is intact at insert time. Loss reason and win reason from ClientTether custom fields migrate to Freshsales custom Deal fields.

ClientTether Proposals carry template-based rich content, pricing, and dates. Freshsales does not have a native Proposal object on Growth or Pro tiers, so we map Proposal content to Freshsales Deal custom fields (proposal_text__c, proposal_dates__c) and attach the proposal body as a Note linked to the Deal. Line items from proposals map to Deal product entries or custom fields. We flag proposals with non-standard template elements for manual review before final import.

ClientTether Work Orders reference Proposals and carry operational data for franchisee execution. Freshsales has no native Work Order object on standard tiers. We map Work Order records to custom fields on the related Account or Deal (work_order_status__c, work_order_dates__c, assigned_franchise_owner__c) and flag the mapping for the customer's admin to validate against their operational workflow.

ClientTether Tags used as segmentation markers and automation triggers migrate to Freshsales custom multi-select picklist fields on the relevant object. Tags that represent content classification migrate to Freshsales Topics with TopicAssignment records. We enumerate all tag values during discovery and align them to Freshsales field types during schema design.

ClientTether Email Sequences (time-triggered drip campaigns) enroll status and step content migrate as reference data attached to the Contact or Lead record. Freshsales Workflows provide automation capabilities, but the cadence model differs from ClientTether sequences. We export sequence step content, timing delays, and enrollment status as a written inventory document so the customer's Freshsales admin rebuilds enrollment logic in Freshsales Workflows or Sequences if available on their tier.

ClientTether inbound and outbound call records (duration, direction, linked Contact) migrate to Freshsales Tasks with TaskSubtype = Call. Call disposition and duration migrate to custom Task fields. The linked Contact is resolved by email before Task insert. Activity date ordering is preserved so the Contact timeline reflects the original call timestamps.

ClientTether custom fields on Contacts, Leads, Accounts, and Deals migrate to Freshsales custom fields of equivalent type. We enumerate field types during discovery (text, number, date, picklist, multi-select) and map them to Freshsales field types during schema design. Picklist values migrate as options on Freshsales picklist fields. Custom field API names preserve the ClientTether naming convention where possible, with Freshsales naming standards applied where conflicts occur.