Migrate from ClientTether.com to Microsoft Dynamics 365 Sales

ClientTether Contacts map to Dynamics 365 Contact records. We preserve all standard contact fields (name, phone, email, company association), communication history tied to SMS threads and email sequences, and tag assignments as custom fields on Contact. The primary phone and mobile fields map to Telephone1 and Telephone2; the ClientTether contact owner maps to the Dynamics 365 Contact OwnerId via email match against the User table.

ClientTether Leads (generated through web forms, IVR, or CSV import) map to Dynamics 365 Lead. Lead source attribution and originating campaign or form ID transfer to the Lead Source and a custom field capturing the original referral channel. Any lead score or prequalification data from ClientTether migrates to a custom numeric field on Lead.

ClientTether Accounts (franchisee entities, franchise owner accounts, FBC structures) map to Dynamics 365 Account with parent Account for hierarchy. We export the full ClientTether hierarchy as a parent-child relationship table and remap brand accounts, franchise owner accounts, and multi-unit structures to the closest Dynamics 365 equivalent. Any hierarchy depth exceeding Dynamics 365's nesting limits is flagged during discovery for manual reorganization before migration.

ClientTether Pipelines with customizable stage names and ordering map to Dynamics 365 Opportunity Record Types and Sales Processes. Each ClientTether pipeline becomes a Record Type on Opportunity, with its stages mapped to StageName values in a corresponding Sales Process. Stage probabilities migrate from ClientTether to the stage probability field on each Opportunity.

ClientTether Deals map to Dynamics 365 Opportunity. The deal stage property maps to the Microsoft Dynamics 365 Sales Process stage; the pipeline assignment maps to the Record Type. Deal amount, close date, and owner migrate directly. Any ClientTether custom fields on Deals transfer to custom Opportunity fields.

ClientTether Proposals carry template-based rich content, pricing line items, start/end dates, and optional Work Order linkage. We export proposal body text and line items; rich template formatting and embedded template constants may require reformatting at the destination. We flag proposals with non-standard template elements for manual review before final import. If the customer requires Work Order retention, we recommend a custom WorkOrder entity or Project Service integration rather than using Quote for operational tracking.

ClientTether Work Orders reference Proposals and carry operational data for franchisee execution. Work Order records, linked proposal dates, status, and assigned franchise owner migrate to a custom WorkOrder entity in Microsoft Dynamics 365 Sales or to Opportunity with a custom field capturing the work order context. The customer chooses the mapping strategy during scoping based on whether Work Orders need to remain separate from the sales pipeline.

ClientTether Tags serve as segmentation markers and automation trigger conditions across Contacts, Leads, Accounts, and Workflows. We export all tag assignments per record and map tag sets used for segmentation to Dynamics 365 multi-select picklist fields. Tags used for automation routing are flagged as requiring Power Automate or Microsoft Dynamics 365 Sales automation rebuild in the written handoff inventory.

ClientTether Email Sequences (time-triggered drip campaigns attached to Leads or Contacts) are exported with step content, timing delays, and enrollment status. We preserve the sequence step content in a written inventory document because Microsoft Dynamics 365 Sales sequences are a separate feature requiring the Sales Enterprise or Sales Premium tier, and complex sequences may need Power Automate or a sales engagement tool for full parity. The customer's admin rebuilds sequences post-migration.

ClientTether inbound and outbound call records (with duration, direction, and linked Contact) migrate to Dynamics 365 Task with TaskSubtype = Call. Call disposition, duration, and recording URL references transfer to custom Task fields. Missed-call follow-up task generation migrates as tasks with a custom priority field indicating the missed-call origin. Activity date ordering preserves the original call timestamp.

ClientTether custom fields on Contacts, Leads, Accounts, and other objects are enumerated during discovery. Field types and picklist options are mapped to equivalent Dynamics 365 field types (text, integer, decimal, picklist, lookup). We pre-create the destination schema in a Dynamics 365 Sandbox before migration and validate field type compatibility during the sandbox phase.

ClientTether User records (name, role, and Lead/Task assignment) export by email match against the Dynamics 365 destination User table. Any Hub Owner or franchise admin without a matching Dynamics 365 User is held in a reconciliation queue for the customer to provision before record import resumes. Open task assignments migrate by resolving the ClientTether owner email to the Dynamics 365 OwnerId.