Migrate from ClientTether.com to Salesforce Sales Cloud

ClientTether Contacts are the primary CRM record, containing name, phone, email, company association, and communication history. We split Contacts into Salesforce Lead (for prospects without a converted relationship) and Contact (for qualified relationships attached to an Account) based on ClientTether tag values and pipeline stage. Any Contact with a franchise owner entity association maps to Contact under the corresponding Account. We preserve the original ClientTether contact ID in a custom field ct_contact_id__c on both Lead and Contact for audit traceability.

ClientTether Leads generated through web forms, IVR, or CSV import map directly to Salesforce Lead. Lead source attribution and originating campaign or form ID migrate to Salesforce LeadSource and a custom field ct_original_campaign__c. HubSpot-style lead scoring (if configured in ClientTether) migrates to a custom numeric field ct_lead_score__c.

ClientTether Accounts (franchisee or franchise owner entities) map to Salesforce Account. The ClientTether hierarchy — brand accounts, franchise owner accounts, FBC structure — exports as a nested parent-child relationship and maps to Salesforce Account with a self-referencing ParentAccountId lookup. We flag any hierarchy depth that exceeds Salesforce's five-level nesting limit during discovery.

ClientTether Pipelines map to Salesforce Opportunity record types and sales processes. ClientTether Deals migrate to Opportunity with dealstage mapped to Salesforce StageName, pipeline mapped to the relevant Record Type, and closedate preserved. Deal value, probability, and custom properties migrate as typed Opportunity fields.

ClientTether Proposals carry template-based rich text content, line items, pricing, start/end dates, and optionally link to Work Orders. Salesforce has no native Proposals object in Sales Cloud without CPQ. We store proposal body text and line items in custom fields on Opportunity (ct_proposal_body__c as long-text area, ct_proposal_line_items__c as long-text area) and flag any non-standard template elements for manual review. If the customer licenses Salesforce CPQ post-migration, the proposal migrates as a Quote.

ClientTether Work Orders reference Proposals and carry operational execution data. We migrate Work Order records as Salesforce Task (with WhatId pointing to the linked Opportunity) or as a custom Work_Order__c object if the customer requires the full schema. Proposal dates and status migrate to Task custom fields or custom Work Order fields, preserving the linkage to the originating Opportunity.

ClientTether Tags serve as both segmentation markers and automation trigger conditions. We export all tag assignments per Contact, Lead, Account, and Deal record. Tags migrate to Salesforce as custom multi-select picklist fields on the relevant object (ct_tags__c) or as a custom tagging object with TagAssignment records if the customer prefers a scalable approach. Tag-based trigger logic is preserved as documentation for Flow rebuild.

ClientTether email sequences are time-triggered drip campaigns attached to Leads or Contacts. We export sequence step content, timing delays, and enrollment status. At the destination, sequence step content migrates as Salesforce EmailTemplate records or as a custom Sequence__c object. Enrollment status (active, paused, completed) and original enrollment date migrate to custom fields. Full cadence automation requires manual rebuild in Salesforce Flow or Sales Engagement.

ClientTether inbound and outbound call records (duration, direction, linked Contact, missed-call follow-up task) migrate to Salesforce Task with TaskSubtype = Call. Call disposition, duration in seconds, and recording URL (if available via ClientTether API) migrate to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original ClientTether timestamp.

ClientTether 2-way SMS threads have no direct Salesforce equivalent. We migrate SMS message content, timestamps, and direction as a custom SMS_History__c object (ContentDocumentLink attached to the parent Contact or Lead) or as Task records with a custom SMS subtype. The customer chooses the destination shape during scoping.

ClientTether custom fields on Contacts, Leads, Accounts, Deals, Proposals, and Work Orders are enumerated during discovery. Field types (text, number, date, picklist, checkbox) map to Salesforce field types during schema design. Picklist options are enumerated and mapped to Salesforce picklist values. Custom fields are deployed to the Salesforce Sandbox before data migration begins.

ClientTether user records (name, role, assignment of Leads and Tasks) map to Salesforce User. We match by email address. Any ClientTether user without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Open tasks assigned to the original user reassign to the mapped Salesforce User.