Migrate from Textedly to Pipedrive

Textedly Subscribers map to Pipedrive Contacts. Phone is the primary matching key and populates the phone field on the Contact record. First Name, Last Name, Email, Address, City, State, ZIP, and Birth Date migrate to their corresponding Contact fields. The Textedly subscription status (Subscribed or Unsubscribed) populates a custom field sms_subscription_status__c; active subscribers import as normal, and unsubscribed contacts are flagged with status and a note that the unsubscribe timestamp is not available from Textedly's export.

Textedly Groups are flat lists that segment subscribers for targeted campaigns. We map group membership to tags on each Contact record during migration. Each group name becomes a Pipedrive tag. For example, if a Textedly subscriber belongs to groups VIP and SMS-Opted-In, the Contact in Pipedrive receives tags VIP and SMS-Opted-In. There is no group hierarchy in Textedly, so no nested structure mapping is required.

Free-form tags applied to Textedly subscribers (distinct from group membership) export as comma-separated values and parse into an array. We map each tag to a Pipedrive tag on the Contact record. If a tag name already exists in Pipedrive from a Group mapping, it is merged rather than duplicated.

Textedly Keywords trigger opt-in flows and are tied to short codes. We export keyword-to-autoresponder mappings as structured workflow records: keyword text, associated short code, triggered message body, and any delay or conditional logic. Keywords are not migrated as active automations because Pipedrive does not have a keyword-triggered SMS opt-in model. We deliver a written inventory document listing each keyword, its trigger conditions, message content, and recommended Pipedrive Automation equivalent for the admin to rebuild.

Auto-responders in Textedly are triggered by keyword or time-based rules with specific message bodies and delays. We export the trigger type, conditions, message content, and delay interval as structured automation data. Branching or conditional logic is documented with a flowchart description. Pipedrive's Automation feature does not replicate Textedly's SMS-triggered autoresponders; the admin rebuilds these as CRM-contextual triggers (deal stage changes, contact field updates, activity logging). We deliver a written auto-responder inventory with recommended Pipedrive equivalents.

Drip sequences are time-based automated message chains with step order, delay intervals, and message content. We export step order, delay intervals, and message body text as structured workflow data. Nested or conditional drip logic is documented with step-by-step conditions. These do not migrate as active sequences because Pipedrive does not have an SMS drip cadence feature. The inventory document maps each sequence to a Pipedrive Automation with CRM-based triggers (time delays, deal movements) as the equivalent logic.

Textedly personalization tokens (first name, email, location, and any custom fields) feed into message content at send time. We export the contact field values and map them to corresponding Pipedrive standard fields or create custom fields (e.g., custom_text or custom_date fields) for non-standard Textedly personalization fields. Custom field types are inferred from the data format during extraction.

Textedly campaigns aggregate sent messages, delivery receipts, and response logs. We export campaign metadata (campaign name, start date, end date, total sent, total delivered, total opted out) as structured records. Campaign summary statistics migrate as a Note attached to each affected Contact with the campaign name, date, and outcome. MMS media references (URLs) are preserved as text notes if the media was referenced in campaign logs.

Textedly subscribers may have a Company Name field. If multiple subscribers share the same company name, we create a single Pipedrive Organization and link all matching Contacts to it via the Organization ID lookup. This requires a deduplication step where we normalize company name strings (trimming whitespace, standardizing capitalization) before grouping. If the Textedly subscriber list has no company name field populated, we skip Organization creation and contacts import as standalone records.

Textedly users with assigned roles and campaign ownership export with their role assignments. We map Textedly user email to Pipedrive User by email match. Role assignments (admin, manager, member) are documented but Pipedrive's permission model differs; we note the mapping discrepancy in the handoff document so the admin assigns Pipedrive roles post-migration. Users without a matching Pipedrive account enter a reconciliation queue for manual provisioning.

Textedly subscribers with zero delivery history, carrier-flagged numbers, or silently suppressed status are flagged during pre-migration audit. These records import into Pipedrive with a custom field sms_suppression_status__c = suppressed and a note explaining the flag reason. They are not excluded from import but are marked so the Pipedrive admin can suppress outbound SMS sends via an integration or manual list hygiene before activating a Textline or Twilio integration in Pipedrive.