Migrate from Textedly to Odoo CRM

Textedly Subscribers map to Odoo CRM Contacts with Phone (mobile) as the primary identifier. The following Textedly fields map directly: First Name, Last Name, Email, Address, City, State, ZIP, Birth Date. We map Phone to the Contact's mobile phone field and use it as the dedupe key during import to prevent duplicate contacts. Tags from Textedly (derived from Groups) are preserved as Odoo Tags attached to each Contact record. Any Textedly custom personalization fields export as values we map to Odoo custom contact fields created before migration.

Textedly's Company Name field on a Subscriber record does not represent a full company entity — it is a free-text field. We evaluate the data quality during scoping: if the Company Name field is populated consistently across the subscriber list, we create Odoo Account records for each unique company name and link the corresponding Contacts. If the field is sparsely populated or contains informal names, we skip Account creation and import Contacts as standalone records. The customer decides the strategy during scoping based on data quality analysis.

Textedly Groups segment subscribers for targeted campaigns. We export group membership and convert each group to an Odoo Tag attached to the corresponding Contact. Textedly does not support group hierarchy — groups are flat lists — so the mapping is direct. Tags in Odoo are used for segmentation in the CRM pipeline view and in mass mailing filters. The customer specifies whether group names should be prefixed or cleaned during import.

Textedly Keywords trigger opt-in flows and are tied to short codes. We export keyword-to-autoresponder mappings as structured automation records with the keyword, trigger condition, and associated message body. Keywords in Textedly are short-code-bound and cannot be transferred to Odoo (phone numbers and short codes do not migrate). We document the keyword configuration in the automation rebuild guide so the customer's Odoo admin can recreate the opt-in logic using Odoo Automated Actions triggered on Contact creation with the appropriate filter conditions.

Textedly Auto-Responders are time-based or keyword-triggered message chains attached to specific keywords or subscriber actions. We export the message body, delay interval, and trigger condition as structured automation data. Odoo Mail Templates provide the message body and merge field substitution (using {{object.field}} syntax). Automated Actions in Odoo can trigger a Send Email action or a Create Activity action based on record conditions. Complex branching auto-responders with conditional logic do not map directly; we document the full step sequence in the automation handoff so the admin rebuilds the flow using Odoo Automated Actions and Mail Templates.

Textedly Drip Campaigns are time-based automated message chains sent to subscribers over a defined interval. We export the campaign step order, delay between messages, message content, and audience filter. Odoo does not have a native SMS drip campaign object; the equivalent is a combination of Mass Mailings (sent via the configured outgoing mail server or integrated SMS gateway) and Scheduled Automated Actions that trigger each step. We document the complete drip sequence in the automation rebuild guide with step numbers, delays, and message content, enabling the admin to rebuild using Odoo Mass Mailings and Automated Actions.

Textedly MMS messages attach images and media referenced by URLs. We preserve MMS media URLs as a custom Text field on the Contact record (e.g., last_mms_url__c). Odoo does not have a native MMS storage object in the CRM module. If the customer uses an Odoo-integrated SMS gateway (Twilio, MessageBird, or similar), media URLs can be passed as variables in the SMS send action. We note this in the technical notes and recommend a post-migration review of media attachment handling.

Textedly exports subscriber status as a binary flag with no timestamp. We map the status to a custom boolean field on the Contact record (e.g., sms_unsubscribed__c) set to True for unsubscribed contacts and False for active subscribers. We flag the absence of an unsubscribe timestamp as a limitation: Odoo mailing lists respect the opt-out flag for email sends, but the date of opt-out is not available from the source export, which affects re-engagement campaign targeting. We recommend the admin document any contacts with recent opt-outs manually if that date is commercially significant.

Textedly personalization tokens (First Name, Last Name, Email, Company, City, State, Birth Date, and any custom fields) are stored per subscriber and inserted at message send time. We export the field values and create equivalent custom fields on the Odoo CRM Contact model before migration. Custom field API names follow Odoo's naming convention (snake_case). These fields are then available for use in Odoo Mail Templates using the {{object.field_name}} merge field syntax. Birth Date maps to a Date field on Contact.

Textedly Campaigns aggregate sent messages, delivery receipts, and response logs. Odoo CRM does not have a native SMS campaign object with delivery statistics. We export campaign metadata (name, send date, total sent, delivered count, response count) and aggregate delivery statistics per subscriber, then write these as custom fields on each Contact record (e.g., last_sms_sent_date__c, sms_campaign_count__c). Campaign-level delivery reports are documented as a written inventory for the customer's admin to reference for historical reporting.

Textedly Users with campaign and contact ownership map to Odoo User records by email match. We export user name, email, and role. Role semantics differ between platforms: Textedly roles are campaign-level (owner, admin, member), while Odoo User access rights are app-scoped (CRM User, Sales User, Admin). We create a role-mapping table during scoping and flag any Textedly role that has no direct Odoo equivalent. The customer's Odoo admin provisions Users before the production migration phase.

Textedly allows custom personalization fields per subscriber beyond the standard set. We export all active custom field names, data types, and values from the subscriber export. Before migration, we create matching custom fields on the Odoo CRM Contact model using Odoo Studio (for in-app configuration) or via XML data migration for enterprise-grade deployment. Field types are mapped: text to Char, number to Float or Integer, date to Date. The customer's Odoo admin validates field creation before the production phase.

Textedly Message Templates (saved outbound message bodies used across campaigns) map to Odoo Mail Templates. We export template name and body content including any personalization token placeholders. In Odoo, Mail Templates use the Jinja-style {{object.field}} syntax for merge fields; we convert Textedly's token format to Odoo's format during the transform step. Templates are assigned to the corresponding Mass Mailing configuration or Automated Action for use in drip campaign rebuilds.