Migrate from ClientTether.com to Twenty CRM

ClientTether Contacts map directly to Twenty Persons. The Person record preserves name, phone, email, company association (via workspaceCompany link), and all standard contact fields. We export contact tags as a multi-select picklist field on Person and resolve the linked Account to a workspaceCompany via the email domain or explicit company assignment. Communication history (SMS, email, calls) attaches to the Person's activity timeline as Events or Tasks.

ClientTether Leads generated through web forms, IVR, or CSV import map to Twenty Persons with a personStage value set to Lead. Lead source attribution, originating campaign ID, and form submission metadata migrate as custom fields on the Person record. We preserve the original lead score (if populated in ClientTether) in a custom field for segmentation in Twenty.

ClientTether Accounts (franchise owner entities, franchisee entities, brand accounts) map to Twenty Companies. The nested hierarchy in ClientTether — brand account, franchise owner account, FBC structure, franchise owner entity — exports as a parent-Company relationship. We build a Company hierarchy map during discovery and create parent-Company links in Twenty for each nesting level, flagging any depth that requires custom object escalation beyond the standard Company model.

ClientTether Pipelines map to Twenty Pipelines with their respective stage names and ordering preserved. Each pipeline becomes a distinct pipeline view in Twenty, and stage values become Opportunity stage picklist options. We configure the stage probabilities to match ClientTether's original values where available from the export.

ClientTether Deals map to Twenty Opportunities. The linked pipeline and stage assign to the Opportunity's pipeline and stageName fields. Close date, amount, probability, and linked Account (Company) migrate directly. Owner assignment resolves by email match against the Twenty User roster. Closed-won and closed-lost reasons map to a custom Opportunity field.

ClientTether Proposals do not have a native Twenty equivalent, so we create a custom Proposal object in Twenty via the /metadata API. Proposal fields (body text, line items, start/end dates, linked Work Order reference) migrate as custom fields on the Proposal record. Rich text content and template formatting may require re-rendering at the destination if the proposal body contains non-standard template elements. The custom Proposal object links to the parent Opportunity via a lookup field.

ClientTether Work Orders map to a custom Work Order object in Twenty created via /metadata. Work Order status, linked franchise owner, linked proposal reference, execution dates, and operational notes migrate as custom fields. The custom Work Order object links to the parent Proposal and the related Company via lookup fields. Any non-standard operational data fields are enumerated during discovery and mapped to additional custom fields on the Work Order object.

ClientTether's franchise infrastructure designer creates nested franchise owner entities, FSO structures, and FBC management records that do not map to standard Twenty CRM objects. We create two custom objects — FranchiseOwner and FSOEntity — via the /metadata API, map the franchise owner name and contact info, and link them to the corresponding Company record via lookup fields. FBC (Franchise Business Consultant) assignments migrate as a multi-select or lookup field on the FranchiseOwner object.

ClientTether Tags used for segmentation (on Contacts, Leads, Accounts, Deals) migrate to Twenty as multi-select picklist fields on the respective objects. Tags used as automation trigger conditions are preserved in a tagName field but flagged for manual rebuild as part of the automation inventory since ClientTether's automation logic is not API-accessible in full.

ClientTether Email Sequences (time-triggered drip campaigns attached to Leads or Contacts) migrate as a sequenceStep custom field on Tasks or Events to preserve step order and timing delays. We do not recreate the sequence as a native automation in Twenty because the cadence logic requires manual rebuild. The sequence content, timing, and enrollment status are documented in the handoff inventory for the customer's admin to reconstruct in Twenty's workflow engine or as a manual follow-up sequence.

ClientTether call logs (inbound and outbound) migrate to Twenty Events with call direction, duration, and disposition preserved in custom fields on the Event record. The linked Contact resolves to the Twenty Person record via email or phone match. Call recordings attached to the ClientTether log do not migrate via API; we document the recording URLs for manual relinking post-migration.

ClientTether Users (unlimited per account) map to Twenty Users by email match. Role assignments in ClientTether map to Twenty workspaceMember role fields. Any User without a matching Twenty User record goes to a reconciliation queue for the customer's admin to provision before record import resumes. Open task assignments migrate by resolving the owner email to the Twenty User record.