Migrate from Textline to HighLevel

Textline Contacts in the Address Book map to GoHighLevel Contacts. Standard fields (name, phone, email, notes) migrate directly. Custom address book fields (available on Standard and Pro tiers) map to GoHighLevel Contact custom fields that we pre-create before import. Tags applied to Contacts migrate as GoHighLevel tags on each record. We dedupe by phone number as the primary key and by email as a secondary match. If the source account is on Essentials, only standard fields exist and custom field migration is skipped.

Textline Conversations per phone number map to GoHighLevel Contact SMS records. Each conversation thread becomes a chronological series of inbound and outbound SMS entries on the Contact's timeline with timestamp, direction, and content preserved. MMS attachments with accessible URLs migrate as media references on the message record. Large conversation histories require pagination across individual per-conversation exports (Textline's API does not expose a bulk conversation export), so this phase takes longer than standard CRM pulls and we batch records in 50-conversation chunks with exponential backoff.

Textline Departments group phone lines by location or business function. The phone number-to-department assignment migrates as a mapping record in our migration inventory. GoHighLevel's LC Phone system assigns numbers to locations and sub-accounts; we document the Textline department structure so it can be manually replicated as GoHighLevel Locations or sub-accounts. The routing logic within Routes is not exposed via the Textline API and must be recreated manually.

Textline Agents are resolved by email match to GoHighLevel User records. We extract every Agent email referenced in conversation history and contact assignments, then match against the destination GoHighLevel User table. Agents without a matching GoHighLevel User go to a reconciliation queue for the customer's admin to provision before the contact and conversation import resumes. Permissions and custom roles in Textline do not migrate; we document the permission matrix for manual recreation in GoHighLevel.

Textline canned reply templates migrate as GoHighLevel SMS Templates. We export template body text and any shortcut codes used in the template. The customer's admin assigns shortcut codes in GoHighLevel's template library after migration. Templates referencing contact merge fields are flagged so the merge field syntax can be updated to GoHighLevel format during the template rebuild.

Textline custom address book fields (Standard and Pro tiers only) map to GoHighLevel Contact custom fields. We export field names, data types (text, dropdown, date), and values. Field types are recreated in GoHighLevel before import. Multi-select dropdown fields in Textline map to GoHighLevel multi-select picklist fields. If the source account is on Essentials, no custom fields exist and this mapping is skipped.

Tags applied to Textline Contacts migrate as GoHighLevel tags on each Contact record. Tag taxonomy and naming conventions are preserved as-is. No tag hierarchy exists in either platform, so there are no parent-child relationships to resolve.

Textline Announcements are bulk outbound messages sent to contact lists. We export announcement history, audience size, and message content as a written inventory. GoHighLevel does not have a direct Announcement object; bulk outbound SMS is handled via Workflows with contact filter conditions. We document each Announcement so it can be recreated as a GoHighLevel Workflow with the same audience criteria and message content.