Migrate from Textedly to Microsoft Dynamics 365 Sales

Textedly Subscribers map to Dynamics 365 Contacts. Phone number is the primary identifier and maps to Contact's MobilePhone field. First Name, Last Name, Email, Company Name, Address, City, State, ZIP, and Birth Date map to their standard Dynamics 365 Contact fields. We validate phone number formatting (US 10-digit) before insert and flag any number that fails validation for manual review. The Contact's status (active vs unsubscribed) carries over from Textedly's binary flag with the caveat that no unsubscribe timestamp is available in the export.

If the customer uses Textedly to capture prospect-level contacts (opt-ins who have not yet been contacted by sales), we create a Lead record alongside or instead of Contact. The decision between Lead-only, Contact-only, or mixed intake is made during scoping based on the customer's sales process maturity. Lead captures phone as Telephone, first name, last name, email, and address fields identically to the Contact mapping.

Textedly Groups are flat segmentation lists with no hierarchy. We preserve group membership as a custom multi-select picklist field called textingly_group__c on the Contact record. Each group the Subscriber belonged to becomes a picklist value. If a Subscriber was in multiple Groups, all values appear in the multi-select field. The customer can convert this to a Dynamics 365 Marketing segment post-migration.

Textedly Tags are free-form comma-separated labels on Subscribers. We parse them into an array and populate a custom multi-select picklist field called textingly_tags__c on Contact. Tags like VIP, DO_NOT_CALL, or referral_source map as individual picklist values. If a Subscriber had more than 10 unique tags, the overflow maps to a secondary text field textingly_tags_extra__c.

Keyword-to-autoresponder mappings in Textedly (e.g., keyword TEXTDEAL to trigger auto-response with discount code) do not migrate as automation code. We export each active keyword flow as a structured record: keyword, associated short code, trigger condition, response message body, and delay. This becomes a written inventory document the customer's admin uses to rebuild equivalent flows in Power Automate or Microsoft Dynamics 365 Sales Playbooks.

Drip sequences in Textedly (time-based automated message chains) export as structured workflow data: sequence name, step order, delay intervals between steps, and message content per step. Branching or conditional drip logic (e.g., if no reply, skip to step 3) is noted in the inventory document with a recommended Power Automate implementation note. Complex branching drip logic may require a Microsoft Dynamics 365 Sales partner or Power Automate consultant for accurate rebuild.

Textedly Campaign records (campaign name, send date, total sent, delivery rate, response rate) migrate as Dynamics 365 Campaign records. The aggregate stats (delivery rate, response rate) populate custom fields on the Campaign record (textingly_delivery_rate__c, textingly_response_rate__c). Each Subscriber who received a message in that campaign becomes a CampaignMember on the Dynamics Campaign record, linked by Contact. Individual message engagement (opens, clicks, replies) is not available in the standard Textedly export and is noted as a data gap.

Textedly Subscribers flagged or suppressed by carriers (zero delivery history or suspiciously low engagement) are identified during pre-migration audit. We flag them in Dynamics 365 by setting a custom field textingly_suppression_flag__c to true and textingly_suppression_reason__c to the probable cause (zero_delivery, carrier_flag, or manual_block). These Contacts are created but marked Do Not Contact; the customer's admin reviews them before activating any SMS integration in Dynamics.

Textedly personalization tokens (first name, email, location, custom fields) feed from the Subscriber record. Standard tokens (FirstName, LastName, Email, City, State) map to the equivalent Contact fields. Any custom personalization fields created in Textedly (beyond the standard template fields) map to custom Contact fields that we pre-create in Dynamics 365 before migration.

Textedly Users with roles (Admin, Manager, User) export as a reference list. We map them to Dynamics 365 Users by email match. Note that Textedly role permissions do not have a direct Dynamics 365 equivalent; we document the role assignments as a written mapping so the customer's admin can provision equivalent security roles in Dynamics 365 post-migration.