Migrate from Textedly to Zoho CRM

Textedly Subscribers map directly to Zoho CRM Contacts with the phone number as the primary field and first name, last name, email, address, city, state, ZIP, company name, birth date, and tags as standard or custom fields. We use the subscriber phone number as the dedupe key during import. If the customer's Textedly setup associates multiple contacts with the same phone number, we flag this during scoping for the customer to clarify before import to avoid duplicate Contact records.

Textedly exports subscribers as Subscribed or Unsubscribed with no timestamp. We map the binary status to Zoho CRM's HasOptedOutOfEmail field and flag the absence of an unsubscribe date as a known limitation in the migration record. The destination admin should account for this gap when designing re-engagement workflows: contacts marked unsubscribed in Textedly will be suppressed in Zoho but without the date needed to apply time-based re-permission logic.

Textedly silently suppresses or flags phone numbers without user notification. Subscribers with zero delivery history or no message activity in the export are flagged as potentially suppressed before import. We mark these records in a custom suppression_status__c field rather than importing them as active Contacts, so the destination does not inherit invalid numbers and the compliance risk is visible to the Zoho admin for review.

Textedly Groups are flat lists that segment subscribers for targeted campaigns. We export group membership as a list of group names per subscriber and map each group to a Zoho CRM Tag. Tags are applied to the Contact record at import time. No group hierarchy exists in Textedly, so no parent-child mapping is required. The customer chooses during scoping whether to create Tags as Zoho native Tags or as a multi-select picklist field for use in Workflow conditions.

Textedly free-form tags export as a comma-separated field in the subscriber CSV. We parse the tag array and map each unique tag to a Zoho CRM multi-select picklist option on the Contact layout. If the customer uses tags for content classification rather than contact segmentation, we alternatively map to Zoho Topics with TopicAssignment records linked to Contact.

Textedly Keywords trigger opt-in flows and are tied to specific short codes. We export the keyword-to-autoresponder mapping as a structured workflow record documenting the keyword, associated list, trigger condition, and message content. Keywords do not migrate as active automation in Zoho. The inventory document is delivered to the customer with each keyword mapped to a Zoho Workflow rule trigger and the recommended Zoho Flow or Blueprint equivalent for the admin to configure post-migration.

Textedly Auto-Responders are triggered by keywords or time-based rules with message bodies and delays. We export step order, delay intervals, conditions, and message content as a structured automation inventory. Complex branching logic is flagged for manual review. Zoho Workflows handle time-based and field-update triggers natively; multi-step branching with conditional paths requires Zoho Flow or Blueprint, which the admin rebuilds using our documented map as the specification.

Textedly drip sequences are time-based automated message chains. We export step order, delay intervals, and message content as a structured workflow data file. Nested or conditional logic (branching on subscriber tag, opt-in source, or message response) is flagged as requiring Zoho Flow for rebuild because Zoho CRM native Workflows do not support multi-step drip cadence logic. The automation inventory is delivered as a written handoff document with each step mapped to a Zoho Flow trigger and action.

Textedly Campaign records aggregate sent messages, delivery receipts, and response logs. We export campaign metadata (name, type, status, start/end dates) and aggregate delivery statistics per subscriber as structured records. MMS media URLs preserved in Textedly export migrate as attachment URLs in the Zoho CRM Campaign record. Campaign member activity (opens, clicks, responses) migrates as Campaign Member Status records linked to the corresponding Contact.

Textedly personalization tokens (first name, email, location, and custom fields) feed into message templates at send time. We export the subscriber fields that are used for personalization as standard or custom Contact fields in Zoho CRM. During scoping we confirm which fields are personalization tokens versus purely data fields and ensure the Contact layout includes them with the appropriate field types. Zoho CRM's 300-field-per-module limit applies; we audit field counts during schema design to avoid violations.

Textedly users are assigned roles and can own campaigns or contacts. We export user accounts and role assignments from Textedly, but Zoho CRM maps roles differently. An explicit role-mapping step is required during scoping: Textedly roles are mapped to Zoho CRM profiles and roles, and the admin configures Zoho user records to match. The migration does not provision Zoho Users automatically; the admin creates Zoho user accounts before migration so Owner lookups can be resolved during import.

Textedly Webforms capture new subscribers and are tied to specific keyword flows. We export form field configurations and associated keyword associations as a structured record. Form hosting URLs are platform-specific and non-transferable. The inventory document maps each Textedly webform to Zoho Webforms or a Zoho Landing Page equivalent for the admin to configure in the destination. Form-submitted subscriber data that exists in Textedly migrates as standard Contact records with the webform source captured in a custom field.