Migrate from Textedly to Nutshell

Textedly Subscribers map to Nutshell People. The standard Textedly export fields — Phone, First Name, Last Name, Email, Address, City, State, ZIP, Company Name, Tags, and Birth Date — map to Nutshell Person fields directly. Phone number format is preserved as the primary contact field. We use phone as the dedupe key and append additional records where duplicates are detected. Any subscriber record with zero delivery history is flagged in a separate reconciliation file before import so your team can decide whether to include it.

Textedly Groups segment subscribers for targeted campaigns. Groups with company affiliation map to Nutshell Account records that we create alongside the Person import using the Company Name field. Groups used purely for messaging segmentation (not organizational) map to Nutshell Tags on the Person record. We document the full group list during scoping so the customer chooses the mapping strategy before import begins.

Textedly tags export as comma-separated values in the subscriber CSV. We parse them into an array and map them to Nutshell custom fields if the customer requires structured segmentation, or to Nutshell Tags if loose categorization is acceptable. Multi-value custom fields in Nutshell support up to 500 values per field. If the customer has more than 500 distinct tags, we recommend a Nutshell custom field with a delimited text format reviewed post-migration.

Textedly keywords trigger opt-in flows and are tied to short codes. We export the complete keyword-to-autoresponder mapping as a structured workflow inventory document. Multiple keywords pointing to the same list are reconciled in the document with recommended Nutshell group assignments. Keywords themselves cannot migrate because they are tied to Textedly's short code carrier agreement; the inventory document provides the trigger conditions and message content your admin uses to rebuild in Nutshell or via Zapier.

Auto-responders are keyword-triggered or time-based message flows in Textedly. We export step order, delay intervals, and message body content as a structured automation document. Complex branching logic is documented as a decision tree for manual rebuild. Auto-responders do not migrate as live automation — Nutshell's native automation layer does not have a direct keyword-trigger equivalent, so the recommended path is Zapier integration or a custom workflow documented at the handoff meeting.

Textedly drip sequences are time-based automated message chains. We export step order, delay intervals, message content, and conditional branching as a structured workflow document. Nutshell does not have a native drip campaign builder; the recommended replacement is a Zapier workflow connecting to an email or SMS tool, or a manual sequence managed by the sales team. We deliver the drip sequence documentation at handoff so the admin can reconstruct the cadence in their chosen tool.

Textedly campaign records aggregate sent messages, delivery receipts, and response logs. We export campaign metadata (name, send date, recipient count, delivery rate, response rate) as structured reference data. This data does not map to a live Nutshell object because Nutshell campaigns are CRM-level tracking rather than SMS blast tracking, but the export serves as an audit record for compliance and historical reporting.

Textedly personalization tokens (first name, email, location, and any custom fields) feed dynamic message content at send time. The underlying contact data that powers personalization exports from Textedly as standard subscriber fields. We map these directly to Nutshell Person fields. Any custom personalization fields unique to the customer's Textedly setup are created as custom fields on Nutshell Person before migration so dynamic content is supported in downstream tools.