Migrate your Textedly data

Subscribers are the primary object. We export all standard fields: Phone, First Name, Last Name, Email, Address, City, State, ZIP, Company Name, Tags, and Birth Date. The full list including subscribed and unsubscribed statuses is available via CSV export. We map the contact status field to the destination's equivalent opt-in flag.

Groups segment subscribers for targeted campaigns. We preserve group membership as tags on each contact record during migration. No group hierarchy exists in Textedly — groups are flat lists.

Tags are free-form labels applied to subscribers. They export as a comma-separated field in the CSV. We parse them into an array and map them to the destination's tagging schema.

Keywords trigger opt-in flows and are tied to short codes. We export keyword-to-autoresponder mappings as workflow records. Multiple keywords pointing to the same list must be reconciled if the destination uses a different short code model.

Auto-responders are triggered by keywords or time-based rules. We export them as automation rules with conditions, message bodies, and delays. Complex branching logic may require manual review at the destination.

Drip sequences are time-based automated message chains. We export step order, delay intervals, and message content as structured workflow data. Nested or conditional drip logic maps to the destination's equivalent automation builder.

Personalization tokens (first name, email, location, and custom fields) are inserted at send time. We export the contact fields that feed personalization and map them to the destination's available merge field syntax.

Campaigns aggregate sent messages, delivery receipts, and response logs. We export campaign metadata and aggregate delivery stats per subscriber. MMS media references are preserved as URLs where Textedly hosts them.

Users are assigned roles and can be owners of campaigns or contacts. We export user accounts and role assignments, but destination platforms map roles differently — an explicit role-mapping step is required.

Phone numbers and short codes are carrier-assigned and non-transferable. They do not migrate between platforms. We export number metadata (type, assigned date) as a reference record but do not transfer the numbers themselves.

Webforms capture new subscribers and are tied to specific keyword flows. We export form field configurations and the associated keyword association, though form hosting URLs are platform-specific and need rebuilding at the destination.

Text-to-Pay transactions are Stripe-integrated and live within Stripe's system. Historical payment records, invoice history, and payment status data are not accessible via Textedly export and must be pulled directly from Stripe.

Analytics include delivery timestamps, open/click activity, and subscriber growth metrics. We export available reporting data as structured records. Advanced attribution or cohort analysis requires the destination's own reporting tools.