Migrate from Textedly to HighLevel

Textedly Subscriber records map to GoHighLevel Contact records. Phone number is the primary identifier and maps to the GHL Contact phone field. First Name, Last Name, Email, Address, City, State, ZIP, and Company Name map to standard Contact fields. Birth Date maps to a Contact custom field (date type). Tag values from Textedly are parsed from the comma-separated export field and applied as GHL tags on each Contact. We flag any Subscriber with zero delivery history as potentially carrier-suppressed and mark the Contact with a suppression flag custom field rather than excluding it from migration.

Textedly Groups segment subscribers for targeted campaigns. We preserve group membership as GHL tags on each Contact record. A Subscriber assigned to three Textedly Groups receives three corresponding tags in GoHighLevel. No group hierarchy exists in Textedly (groups are flat lists), so no parent-child resolution is required. If the customer uses Groups as audience segments for specific campaigns, we document the segment-to-tag mapping for campaign rebuild reference.

Free-form tags applied to Textedly Subscribers export as comma-separated values. We parse the tag array and apply each tag individually to the corresponding GHL Contact. GHL tags are case-sensitive and can be used in Workflow triggers, Smart List filters, and contact segmentation. We do not modify tag names during migration; customer-created tags are preserved verbatim.

Textedly keyword-to-autoresponder mappings are exported as structured rule documents containing the keyword text, associated short code, trigger type (keyword opt-in vs out), and the auto-responder message body. Keywords do not migrate as active automations because GoHighLevel Workflows use a different trigger model (event-based vs keyword-based). We deliver a written keyword inventory with each keyword, its associated message, and the recommended GoHighLevel Workflow trigger configuration for the customer's admin to rebuild.

Textedly auto-responders export as automation rules with conditions (keyword-triggered or time-delay), message body content, and delay intervals. Branching or conditional logic is documented as a rule tree. GoHighLevel Workflows use a different builder paradigm with triggers, conditions, and actions structured differently. We export the auto-responder content, step order, and conditional logic as a written automation map and do not implement the workflows in GHL during migration.

Textedly drip sequences export as step-ordered message chains with time delays between each step. MMS references are preserved as media URLs. We export step order, delay intervals, message content, and any conditional branching as a structured document. GoHighLevel Workflows handle multi-step sequences with Wait actions and conditional branches, but the configuration must be rebuilt by the customer's admin. We do not migrate drip sequences as active automations.

Textedly campaigns aggregate sent messages, delivery receipts, and response logs. We export campaign metadata (name, send date, total recipients, delivery rate, response rate) as a structured audit record and store it in a GHL Contact custom field or as a note attachment on the contact for reporting reference. GHL does not have a native campaign aggregation object in the same way Textedly does; reporting across campaigns is handled through GHL's pipeline and reporting tools post-migration.

Textedly user accounts with roles export with name, email, and role assignment. We map user email as the GHL User identifier. Role mapping is documented as a role-equivalence table (Textedly role to GHL role or permission set) for the customer's admin to apply during GHL team setup. If the same email exists in both systems, we match by email; new users require manual provisioning in GHL before migration.