Migrate from ClientTether.com to Nutshell

ClientTether Contacts migrate to Nutshell People. Standard fields — name, phone, email, company association, address — map directly to Nutshell's People object fields. Communication history (call logs, email records, meeting records) attaches to the Person record via Nutshell's activity timeline. We resolve the Contact-to-Account linkage and set the Person's Company field to the corresponding migrated Account. Any tags on the Contact migrate as a multi-select picklist or tag field on Person, depending on Nutshell's field configuration at the destination account tier.

ClientTether Leads (generated via web forms, IVR, or CSV import) map directly to Nutshell Lead records. Lead source attribution and the originating campaign or form ID migrate to custom fields on the Lead since Nutshell's standard Lead object tracks source name and status but not campaign ID natively. We flag any Leads with a status of 'converted' in ClientTether and resolve them to a corresponding Person or Deal record at migration time.

ClientTether Accounts (franchisee entities, franchise owner organizations, FBC structures) map to Nutshell Company records. The key migration work is hierarchy flattening: ClientTether's nested brand accounts, franchise owner accounts, and FBC structures translate to Nutshell Company records with a parent_company_id reference where the nesting depth is one level. Multi-level hierarchies (brand account > franchise owner > franchise entity) are remapped to two levels of parent_company references and flagged for manual review because Nutshell supports only single-level parent Account nesting. The franchise owner type designation migrates as a custom field on the Company record.

ClientTether Pipelines map to Nutshell Pipelines with their stage definitions. Stage names, positions, and probabilities migrate to Nutshell Pipeline stages. If ClientTether uses multiple named pipelines (e.g., separate pipelines per brand or FSO), these map to separate Nutshell Pipelines with distinct stage sets. We configure the pipeline and stage structure in Nutshell before any Deal records are imported.

ClientTether Deals map directly to Nutshell Deals. The dealstage and pipeline assignments from ClientTether map to the corresponding Nutshell Pipeline and Stage values created during pipeline configuration. Closed-Won and Closed-Lost reason fields from ClientTether custom properties migrate to Nutshell Deal custom fields. We resolve AccountId and OwnerId at migration time using the Account and User mapping.

ClientTether Tags used as segmentation markers on Contacts, Leads, Accounts, and Deals migrate to Nutshell Tags. Tag assignments are preserved per record, and tags used as automation trigger conditions are flagged separately in the migration inventory. Nutshell Tags are a first-class object and display in list views and filtering, so the segmentation logic carries forward even though the triggering automation does not.

Custom fields on Contacts, Leads, Accounts, and Deals in ClientTether are enumerated during discovery. We map field types (text, number, date, picklist, checkbox, phone) to Nutshell's equivalent custom field types. Picklist fields migrate with their option values preserved. Fields that have no direct Nutshell equivalent (e.g., franchise-specific multi-select fields) are translated to text fields and flagged for review. We pre-create all custom fields in Nutshell before record import begins.

ClientTether inbound and outbound call records — duration, direction, timestamp, disposition, linked Contact — migrate to Nutshell Activity records of type call. We preserve the original call timestamp as the Activity date, call duration as a custom field (since Nutshell's standard call activity does not include a dedicated duration field), and the disposition note as the Activity description. The Contact association is resolved via the Contact-to-Person migration mapping.

ClientTether email sequence enrollment records and email engagement history (sent, opened, clicked timestamps) migrate to Nutshell Activity records linked to the corresponding Person. Email body content migrates as a note or activity description depending on content length and format. If ClientTether tracks email sequence step position, this is stored as a custom field on the activity record for sequence reconstruction documentation.

ClientTether scheduled meetings and task records migrate to Nutshell Activity records. Meeting records preserve date, time, duration, and linked Contact. Tasks migrate with status (open, completed), due date, assigned user, and description. Task assignment is resolved via the Owner mapping from ClientTether users to Nutshell users.