Migrate from Textedly to Mailchimp

Textedly Subscribers map to Mailchimp Members. The subscriber's email address becomes the Mailchimp Member identifier; phone number migrates to the phone_number merge field. We parse the Textedly CSV export (Phone, First Name, Last Name, Email, Address, City, State, ZIP, Company Name, Tags, Birth Date) and map each column to a Mailchimp standard field or merge field. Subscribers without a valid email address require phone-to-email reconciliation during scoping; Mailchimp requires an email address for a Member record.

Textedly Groups are flat subscriber lists for targeted campaigns. We export group membership as tag assignments and parse them into Mailchimp Tag records. Multiple Textedly groups per subscriber result in multiple Mailchimp Tags on the same Member. Mailchimp Tags are additive and not mutually exclusive, matching Textedly's group behavior.

Textedly 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 create Mailchimp Tags on the corresponding Member records. No tag hierarchy exists in Textedly, so no hierarchical translation is required at the destination.

Textedly exports subscriber status as binary Subscribed or Unsubscribed with no timestamp. We map Unsubscribed to Mailchimp Member status = unsubscribed. The gap in unsubscribe timing (no date-stamp in Textedly export) means we cannot determine how recently a contact opted out; the customer should account for this when planning re-engagement campaigns. Subscribed subscribers import as Member status = subscribed in the target Mailchimp Audience.

Textedly Keywords trigger auto-responders and opt-in flows tied to specific short codes. We export the keyword-to-autoresponder mapping as structured workflow data: keyword name, trigger condition, message body, delay, and any branching logic. Mailchimp uses customer journey automations triggered by events (signup, purchase, tag applied) rather than keyword-based triggers, so the migration team delivers a written automation inventory mapping each Textedly keyword flow to a Mailchimp Customer Journey equivalent for the admin to configure post-migration.

Textedly drip sequences are time-based automated message chains. We export step order, delay intervals, and message content as structured automation data. Mailchimp Customer Journeys handle multi-step sequences but use email (or optional SMS) as the channel. We deliver a drip campaign map specifying step count, timing, and message content so the customer's Mailchimp admin can rebuild each sequence using Mailchimp's automation builder.

Textedly campaign history includes sent counts, delivery receipts, and response logs. We export campaign metadata and aggregate delivery stats per subscriber as structured reference records. Mailchimp does not recreate Textedly campaigns; instead we surface the historical campaign data as a supplemental report so the customer's team has visibility into past SMS performance after migration. MMS media references preserved as URLs where Textedly exposes them.

Textedly phone numbers and short codes are carrier-assigned and cannot transfer to Mailchimp or any other platform. We export the number metadata (type, assigned date, carrier) as a reference record for the customer's records but do not attempt to transfer the number. If SMS continues in Mailchimp, the customer must provision a new short code or long number through Mailchimp's SMS setup.