Migrate from ClientTether.com to Zoho CRM

ClientTether Contacts map directly to Zoho CRM Contacts. The primary fields—Full Name, Email, Phone, Mobile, Mailing Address—translate to their Zoho equivalents. Communication history (SMS thread summaries, email sequence status, call duration and disposition) migrates as Notes attached to the Contact record. Tags assigned to Contacts become a multi-select picklist field contact_tags__c, with values preserved exactly as they appear in ClientTether. We use email as the dedupe key for Contact import.

ClientTether Leads (generated through web forms, IVR, or CSV import) map to Zoho CRM Leads with lead source attribution and originating campaign ID preserved in custom fields. Lead status values map to Zoho Lead Status picklist options; we enumerate all ClientTether lead stages during discovery and configure matching Zoho picklist values before import. Lead scoring from ClientTether migrates to a custom number field lead_score__c.

ClientTether Accounts (franchisee entities, franchise owner entities) map to Zoho CRM Accounts. The Account Name maps to Account Name, and the franchise entity type is preserved in a custom picklist field franchise_entity_type__c. Account fields like billing address and phone migrate directly. Email serves as the dedupe key for Account import.

ClientTether Pipelines and their custom stage names and ordering map to Zoho CRM Deals with a custom pipeline configuration. We pre-create Zoho pipeline stages matching ClientTether stage names before Deal import. Probability percentages per stage migrate from ClientTether to Zoho stage probability values. If ClientTether has multiple pipelines, we configure multiple Zoho pipeline views (Zoho Professional and above supports multiple pipelines) or use a custom picklist pipeline_name__c to distinguish them in a single Zoho pipeline.

ClientTether's franchise infrastructure creates nested structures—brand accounts at the top, FSO entities, franchise owner accounts, FBC management layers, and individual franchise owner entities—that have no native equivalent in Zoho CRM. We export the full hierarchy as a parent-child relationship and map it to Zoho Account with Parent Account set. The top-level brand account becomes a root-level Account; FSO and franchise owner entities become child Accounts under the brand. We flag any hierarchy depth that exceeds Zoho's nesting limits (Zoho supports three levels of parent-child Account nesting by default) and document the truncation point for the customer's admin.

ClientTether Deals map to Zoho CRM Deals. Deal Name, Amount, Closing Date, Stage (mapped to the pipeline stage configured in step 4), and Owner (resolved by email match to Zoho Users) migrate directly. The ClientTether deal-linked Account maps to the Zoho Deal's Account Name lookup. Custom fields on Deals enumerate and map to Zoho custom fields of matching type before import.

ClientTether Proposals carry template-based rich content, line items, start/end dates, and optional Work Order linkage. Zoho CRM has no native Proposal object at Standard tier. We configure a Zoho custom module called Proposals with fields for proposal body, line items, dates, and linked Deal. Proposal rich text and template constants may require reformatting; we flag proposals with non-standard template elements for manual review before final import and preserve original proposal PDFs as Zoho Attachments linked to the Proposal custom module record.

ClientTether Work Orders reference Proposals and carry operational data for franchisee execution. We configure a Zoho custom module called Work Orders with fields for linked proposal reference, franchise owner assignment (lookup to Account), status, and execution dates. If the customer prefers a lighter approach, Work Orders map to Zoho Tasks with a custom field work_order_id__c and description content preserved. We export Work Order status and the linked franchise owner Account during discovery.

ClientTether Email Sequences (time-triggered drip campaigns attached to Leads or Contacts) contain step content, timing delays, and enrollment status. The sequence step content and timing windows migrate as a documented output: we export each sequence as a structured table listing step number, step type (email, delay, task), delay duration, and body content. Zoho's Blueprint and Workflow combination can reproduce some sequence behavior, but the cadence must be rebuilt manually. We do not migrate sequences as live automations.

ClientTether call records (inbound and outbound, with duration, direction, and linked Contact) map to Zoho Tasks with Subform or Task subtype marked as Call. Call disposition and duration migrate to custom fields call_duration__c and call_disposition__c. The linked Contact lookup resolves via email match. Activity timestamp is preserved as the Task due date for timeline ordering.

ClientTether Tags are used as segmentation markers and automation trigger conditions on Contacts, Leads, Accounts, and Deals. We export all tag assignments per record and map them to Zoho multi-select picklist fields named contact_tags__c, lead_tags__c, account_tags__c, and deal_tags__c respectively. The tag values themselves are enumerated as picklist options before import. Any tags used as automation triggers are flagged in the automation inventory document for rebuild in Zoho Workflows or Deluge.

ClientTether custom fields on Contacts, Leads, Accounts, Deals, and other objects are enumerated during discovery with their field types and picklist options. We create matching Zoho CRM custom fields of equivalent type (text, number, date, picklist, multi-select, checkbox, currency, phone, URL) before import. Picklist values migrate as picklist options. Validation constraints in ClientTether (required fields, format rules) are documented for manual configuration in Zoho field settings.

ClientTether Users (unlimited per account) map to Zoho CRM Users. We use email as the dedupe key for User resolution. Any ClientTether User without a matching Zoho User by email is held in a reconciliation queue for the customer's admin to provision before record import proceeds, because Owner lookups on Deals and other records require a valid Zoho User ID.