Migrate from Textline to HubSpot

Textline contacts map 1:1 to HubSpot Contacts. Name, email, phone, and tags transfer directly. Contacts without emails get an email placeholder and a custom flag so your team can enrich them post-migration. The placeholder follows the format 'no‑email‑[phone]' to ensure uniqueness across the contact list.

HubSpot's model separates companies from contacts. Where a Textline contact has an email domain, we create a HubSpot Company record and associate the Contact via the company association. Contacts without domains get a default 'Unassigned' company. The company name is derived from the domain, stripped of 'www.' and converted to title case for readability.

Textline tags (e.g., VIP, Support, Billing) migrate to a HubSpot contact property. HubSpot's contact property model supports multi-select text or associative arrays — we preserve the exact tag names as imported values. If a tag appears across multiple contacts, it remains a separate option in the multi-select list to avoid duplication.

Textline custom fields (e.g., policy_number, preferred_language, client_tier) are created as HubSpot custom contact properties before migration. Property type is inferred from the field's data format — dates, numbers, and pick-lists are created as matching HubSpot types. For fields with mixed formats, we default to text type to preserve data integrity.

Textline conversation threads become a single HubSpot Note on the Contact record, formatted as a chronological message log. Each message entry shows direction (agent vs. contact), timestamp, and message body. Original agent names are preserved as note attribution. The note also includes a footer with the total message count for quick reference.

Individual SMS messages from a Textline thread are merged into one Note per conversation to keep the HubSpot timeline readable. MMS content (image URLs) is preserved as a link within the note body. Full message-level granularity is available as a JSON blob in a custom property for audit purposes.

Textline departments with distinct phone numbers do not map directly to a HubSpot object. We create a 'Source_Department__c' custom property on the Contact to preserve which department originated each conversation thread, and map agents to HubSpot users by email match.

Textline's integration option 'One deal per conversation' creates HubSpot Deals with the contact pre-linked. The deal name reflects the conversation subject or contact name. Deal stage is set to a configurable default — teams specify the target stage before migration runs.

Textline's option 'One ticket per conversation' creates HubSpot Tickets. The ticket subject maps to the conversation title or contact name, and conversation messages are appended to the ticket as internal notes. Ticket pipeline and stage are set to defaults specified in the migration plan.

Textline keyword Routes, auto-assignment rules, and scheduled-message automations have no native HubSpot equivalent. We export your Textline automation definitions as a written specification so your HubSpot admin can rebuild them in HubSpot Workflows and Sequences post-migration. The specification includes trigger events, condition logic, and action sequences for each automation.

Textline message templates are not a CRM data object and do not migrate automatically. We export the template list (name, body, assigned department) as a CSV and your team recreates them in HubSpot as Snippets or Workflow action templates. Each exported row includes template usage stats to prioritize high‑traffic messages for conversion.