Migrate from Textedly to Freshsales

Textedly Subscriber records map to Freshsales Contact. Phone number becomes the Contact's phone field and is used as the dedupe key. First Name, Last Name, Email, City, State, and ZIP map directly to their Freshsales equivalents. We flag any Subscriber with zero delivery history or a suppressed-status indicator as a custom field sms_suppressed__c so your team knows which contacts have carrier delivery risk before sending from Freshsales or an integrated SMS tool.

Textedly's Company Name field on a Subscriber maps to the Account Name on a Freshsales Account record. We create the Account before the Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. If a Subscriber has no Company Name, the Contact remains unlinked to an Account; no orphaned-contact record is created.

Textedly Groups are flat subscriber lists used for targeted campaigns. We preserve group membership as Freshsales Tags on each Contact record. If a Subscriber belongs to multiple Groups, each group name becomes a separate Tag. Flat group structure means no hierarchy mapping is required; the tag list is the direct output.

Textedly free-form tags on Subscribers export as comma-separated values and parse into a tag array per contact. Each tag maps to a Freshsales Tag on the Contact record. Tags used for contact classification carry over directly; no tag normalization is performed unless requested during scoping.

Textedly personalization tokens (Birth Date, Address, Company Name, and any custom fields beyond the standard export template) map to Freshsales custom fields on the Contact module. Freshsales Sprout plan has zero custom fields; Blossom allows 10, Garden allows 100, and Estate allows 300 per module. We confirm the destination plan tier during scoping and provision the required custom fields before import begins. Fields that exceed the plan limit are flagged for admin to promote the plan or drop from the import scope.

Textedly campaign metadata (campaign name, send date, delivery count, MMS media URLs) does not map to a standard Freshsales object because Freshsales has no native campaign record tied to contact-level delivery receipts. We export campaign aggregate stats and attach them to each relevant Contact as a custom text field (e.g., last_sms_campaign__c) or as a Note record. MMS media URLs are preserved as a text list; the media files themselves do not transfer between platforms.

Textedly keywords trigger opt-in flows tied to specific short codes. We export the keyword-to-autoresponder mapping as a structured workflow record with the keyword, associated list, trigger conditions, message body, and delay. Because Freshsales Workflows operate on CRM record triggers rather than inbound SMS keywords, the direct automation logic does not migrate. We deliver a written keyword inventory document so your admin rebuilds the logic in Freshsales Workflows or configures a third-party SMS integration (Twilio, MessageBird) that supports inbound keyword handling.

Textedly auto-responders are triggered by keywords or time-based rules with message bodies and delay intervals. We export each auto-responder as a structured automation record: trigger type, conditions, message body, delay, and any branching logic. Freshsales Workflows use record-created, record-updated, and scheduled triggers with different action types. We deliver a written auto-responder inventory that maps each Textedly flow to a recommended Freshsales Workflow equivalent. Rebuilding is admin work outside the data-migration scope.

Textedly drip sequences are time-based automated message chains. We export step order, delay intervals, and message content as structured workflow data. Freshsales Workflows support scheduled and record-triggered automation but do not use a sequence-step cadence model identical to SMS drip campaigns. We deliver a written drip-sequence inventory documenting the full chain; your admin rebuilds the cadence in Freshsales Workflows or through an integrated sales engagement tool.

Textedly exports unsubscribe as a binary flag (Subscribed or Unsubscribed) with no timestamp. We preserve this flag as a custom field sms_unsubscribe_status__c on the Contact record set to true or false. We also flag the gap: contacts who unsubscribed years ago and those who opted out last week cannot be distinguished in the export. Your Freshsales admin should apply a conservative re-engagement policy for contacts with an unset or old unsubscribe timestamp.

Textedly carriers silently suppress numbers without notifying the account holder, and suppressed numbers receive no delivery confirmation. We identify Subscribers with zero delivery history or no sent-message record and flag them as potentially suppressed before import by setting a custom field sms_suppressed__c to true on the Freshsales Contact. Your team avoids sending to suppressed numbers through Freshsales or any connected SMS tool.

Textedly user accounts with roles and campaign ownership map to Freshsales User records. We export user email, name, and role. Destination role assignment is a manual step requiring your Freshsales admin to map Textedly roles to Freshsales roles (Admin, Standard) during provisioning. OwnerId resolution on imported Contacts requires active Freshsales Users to exist first.