Migrate from Textedly to Twenty CRM

Textedly Subscriber records map to Twenty CRM Contact records. The subscriber phone number becomes the Contact phone field, first name and last name map to standard name fields, and email maps to the email field where present. We deduplicate on phone number during import. Any Subscriber with an empty phone field is flagged for manual review because Twenty requires a phone value for SMS-capable contact records.

Textedly's binary subscribe status maps to a custom field sms_subscription_status__c on the Contact record. We preserve the flag value but note that Textedly exports no unsubscribe timestamp, so we cannot distinguish recent opt-outs from historical ones. The destination re-engagement logic should account for this gap by applying a conservative re-permission workflow for contacts with an old unsubscribe date.

Textedly Groups map to Twenty CRM Tags applied directly to Contact records. Group membership is flat in Textedly with no hierarchy, so each group name becomes a tag value on the contact. We parse the group list from the CSV export and apply all tags during contact import. If a contact belongs to multiple groups, all group names become tag values on the single contact record.

Textedly Tags export as comma-separated values in the CSV subscriber export. We parse the tag array and apply each tag to the corresponding Twenty CRM Contact record. Tags that represent subscriber segments (e.g., VIP, churned, high-value) become search filters and list views in Twenty. Tags that represent behavioral attributes (e.g., opened_last_30_days) migrate as-is but should be reviewed post-migration for relevance in the CRM context.

Keywords in Textedly trigger opt-in flows and are tied to short codes. We export keyword-to-autoresponder mappings as structured records in a custom migration document. The keyword name, associated autoresponder message, and trigger conditions map to a keyword_reference custom field on the Contact for audit, and the full mapping table is included in the workflow rebuild handoff document. Short codes themselves do not migrate since they are carrier-assigned and non-transferable.

Auto-responders in Textedly are triggered by keywords or time-based rules. We export step order, delay intervals, message content, and conditional branching logic as structured workflow data in a JSON and CSV format. Complex branching logic that exceeds the mapping export capability is flagged for manual review. The customer's admin uses this inventory to rebuild flows in Twenty or an integrated SMS tool like Twilio.

Drip sequences export with step order, delay intervals, message content, and step type (time-triggered, event-triggered, or conditional). Nested or conditional drip logic maps to the destination workflow model on a best-effort basis. We document the full sequence in the handoff package with a step-by-step description, timing, and content for the admin to rebuild in Twenty's workflow builder or a connected automation platform.

Campaign metadata and aggregate delivery statistics per subscriber export from Textedly and load into a custom SMS_Campaign_History__c object in Twenty. The object stores campaign name, send date, message count, delivery status, and MMS flag. Individual message logs export as related records. This preserves the campaign audit trail without creating live campaigns in Twenty, which would require separate rebuild.

Textedly personalization tokens (first name, email, location, and any custom fields defined by the user) map to named custom fields on the Twenty CRM Contact object. We match the field names and data types during schema design, creating the fields before import. Address components (city, state, ZIP) map to the standard address compound field on Contact where possible.

Textedly users with assigned roles map to Twenty CRM WorkspaceMembers. We export user accounts, email addresses, and role assignments. The role-mapping step requires manual review because Textedly's permission model differs from Twenty's WorkspaceMember access levels. We flag any user without a matching Twenty account for admin provisioning before migration.

Phone numbers and short codes are carrier-assigned and non-transferable between platforms. We export number metadata (type, assigned date, short code identifier) as a reference CSV for the customer's records but do not transfer the numbers themselves. The customer provisions new SMS-capable numbers in Twenty or their preferred SMS provider (Twilio, MessageBird) post-migration.