Migrate from Textedly to Salesforce Sales Cloud

Textedly Subscribers map to Salesforce Contact. The Phone field carries the primary mobile number. First Name, Last Name, Email, Address, City, State, ZIP, Company Name, Birth Date, and Tags migrate to their equivalent Salesforce fields or custom fields. We validate each phone number for US 10-digit format before import; numbers with invalid formats are flagged in a reconciliation report. Subscribers with zero delivery history or no sent messages are flagged as potentially suppressed by carriers and documented separately so the customer can decide whether to import them as inactive contacts.

Subscribers that the customer identifies as prospective rather than existing customers map to Salesforce Lead. This is a scoping decision made before migration: if Textedly was used primarily for marketing opt-in lists rather than existing customer communication, Leads are the appropriate destination. Phone, FirstName, LastName, Email, and custom fields map identically to the Contact path. We require explicit customer direction on the Lead-versus-Contact split because Textedly does not distinguish between prospect and customer subscribers.

Textedly Groups are flat lists that segment subscribers for targeted campaigns. Group membership maps to a Salesforce custom multi-select picklist field (e.g., Textedly_Groups__c) on Contact, or to Campaign membership if the customer prefers a CRM-native segmentation model. The customer chooses the strategy during scoping. Groups are flat in Textedly — no group hierarchy exists, so no parent-child relationship mapping is required.

Textedly tags are free-form comma-separated labels on each subscriber record. We parse them into an array and map them to a Salesforce multi-select picklist custom field (e.g., Textedly_Tags__c) on Contact or Lead. If the customer uses more than 500 distinct tags, multi-select picklist may hit the field length limit; in that case we recommend Salesforce Topics with TopicAssignment records as the alternative mapping strategy.

Textedly Keywords trigger opt-in flows and are tied to specific short codes. Keywords cannot migrate as functional automation. We export each keyword-to-autoresponder mapping as a structured documentation record: keyword text, associated short code, triggered message body, and any time-based delay. The customer's Salesforce admin uses this documentation to rebuild equivalent logic in Salesforce Flow or a third-party SMS tool. Short codes are carrier-assigned and non-transferable; a new short code or 10DLC number is required from the SMS provider selected post-migration.

Textedly Auto-Responders are message chains triggered by keywords or time-based rules. We export the full chain structure: trigger condition, step order, message body per step, delay intervals, and any branching logic. Complex branching auto-responders map to a recommended Salesforce Flow equivalent (e.g., Decision element with time-based path). We do not implement the Flow — we document it for the customer's admin or a Salesforce partner to build post-migration.

Textedly drip sequences are time-based automated message chains with step order, delay intervals, and message content. We export the sequence as a structured data file: step number, delay (hours or days after previous step), message body, and conditional branching rules. Nested or conditional drip logic that references subscriber field values is flagged for manual review. The destination for rebuilding is Salesforce Flow (Scheduled Path) or the customer's chosen SMS engagement tool.

Textedly personalization tokens (first name, email, location, and any custom fields) are inserted at send time and reference the subscriber record. We export the contact fields that feed personalization and map them to equivalent Salesforce standard or custom fields on Contact. If Textedly has custom fields beyond the standard template (Phone, First Name, Last Name, Email, Address, City, State, ZIP, Company Name, Tags, Birth Date), we create matching custom fields on the Salesforce Contact or Lead object before import.

Textedly Campaigns aggregate sent messages, delivery receipts, and response logs. Campaign metadata (name, send date, total recipients, delivery count, response count) migrates as Salesforce Campaign records. Individual delivery and response logs migrate as CampaignMember activity records linked to the parent Campaign and each Contact or Lead. MMS media URLs from Textedly are preserved as text references in a custom field on Campaign. Detailed per-subscriber engagement history (open timestamps, click tracking) is not available in Textedly exports and is noted as a data gap.

Textedly exports subscriber status as a binary Subscribed or Unsubscribed flag with no date stamp. We preserve this flag in Salesforce as HasOptedOutOfEmail (the standard email opt-out field) and a custom Textedly_Subscribed__c boolean for the SMS opt-in status specifically. The lack of an unsubscribe timestamp is a known limitation: the destination cannot distinguish a recent opt-out from a historical one. We flag this so the customer's admin can set a conservative re-engagement policy (e.g., only re-engage via SMS if a fresh opt-in is collected post-migration).

Textedly Users are assigned roles and may own campaigns or contacts. We export user accounts (name, email, role) and match them by email against the Salesforce destination org's User table. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. Role assignments (Admin, Manager, User in Textedly) have no direct Salesforce equivalent and are documented for manual role mapping.

Textedly Webforms capture new subscribers and are tied to specific keyword flows. We export form field configurations and the associated keyword association as a documentation record. Form hosting URLs are platform-specific and non-transferable. We recommend Salesforce Web-to-Lead, Experience Cloud forms, or a third-party form tool as the replacement webform layer. The documentation includes the original form field names and their associated Salesforce Contact field mappings.

Phone numbers and short codes are carrier-assigned and non-transferable between platforms. We export number metadata (type, assigned date, carrier) as a reference document, but no number transfers from Textedly to Salesforce. Post-migration, the customer selects a new SMS provider (Twilio, SMS Magic, Salesmsg, or another) that provisions new 10DLC numbers or short codes. The Textedly number metadata document is passed to the new provider for routing reference.

Text-to-Pay transactions are processed via Stripe and live in Stripe's system, not Textedly's. Invoice history, payment status, and transaction records are not accessible via Textedly export. We do not attempt to migrate payment data. The customer must export payment history directly from Stripe if records are required in Salesforce, or accept that payment history remains in Stripe with a reference to the Salesforce Contact record.