Migrate from Textline to Odoo CRM

Textline Contacts in the Address Book map to Odoo res.partner records. The primary phone number becomes the partner's phone and mobile fields; email maps directly. Tags on Textline Contacts migrate as res.partner.category records linked via res.partner.category.rel. We use the contact's phone number as the deduplication key during import to prevent duplicate partner records in Odoo.

Textline conversations are SMS threads tied to a contact's phone number. We migrate each message as a mail.message record linked to the resolved res.partner via the partner's phone number lookup. Message direction (inbound/outbound), timestamp, body content, and agent attribution transfer. MMS attachments migrate as ir.attachment records linked to the message where URLs remain accessible. This phase requires per-conversation pagination and can extend extraction time significantly for accounts with long message histories.

Textline Departments group phone lines by location or function. We map each Department to an Odoo crm.team record with the department's phone numbers preserved as a custom field on the team. The team lead maps from the department's primary agent assignment. Teams without a clear Odoo equivalent are mapped to a custom char field on res.partner to preserve the source grouping.

Textline Agents map to Odoo res.users. We match agents by email address. Each agent's department assignment in Textline maps to the corresponding crm.team membership in Odoo. Permissions and custom roles in Textline are documented for manual replication in Odoo's access rights configuration (Settings > Users > Access Rights). Active agents without matching Odoo users are held in a reconciliation queue for admin provisioning before record import.

Textline custom fields on Contacts (Standard and Pro plans only) map to Odoo custom fields on res.partner. We pre-create the destination fields with matching types (char, selection, date, etc.) via Odoo's settings or direct SQL during the schema phase. Custom field values migrate as literal values against the new field names. If the Textline account is on Essentials, no custom fields exist to migrate.

Textline canned reply templates export with their shortcut codes and body content. We deliver these as a CSV inventory of template names and bodies. Odoo mail.template requires manual creation in Settings > Technical > Email > Templates because template configuration includes WYSIWYG body building, signature placement, and recipient model scoping that cannot be fully automated across platforms.

Tags applied to Textline Contacts migrate as res.partner.category records. Tag names and taxonomy structure (hierarchical if applicable) are preserved as-is. We create the categories in Odoo before importing contacts and resolve the many-to-many relationship via res.partner.category.rel during the contact import phase.

Textline Announcements are bulk outbound messages sent to contact lists. We export the announcement body, send timestamp, and contact list membership. In Odoo, Announcements map to mail.mass_mailing records, which require the customer to configure the mailing list (mailing.list) and select a compatible email template. The sending mechanism must be replicated in Odoo because the actual send is a platform action rather than a stored record.

MMS attachments within Textline conversations are referenced by URL in message records. We preserve attachment URLs and migrate them as ir.attachment records in Odoo linked to the corresponding mail.message via ir.attachments.res.model and res_id. File re-download and re-hosting depends on whether the attachment URLs remain accessible post-migration from Textline; URLs that expire or require authentication may need manual re-upload by the customer's team.

Textline Routes assign inbound messages to agents or departments based on routing rules. Routes are not exposed via the Textline public API, so they cannot be migrated programmatically. During discovery we document the routing logic (keyword triggers, time-based rules, department assignments) and deliver a written inventory of Routes with recommended equivalents in Odoo's CRM Team assignment rules or Server Actions. The customer's admin recreates these manually post-migration.

Textline Automations trigger on keywords, time, or contact actions. The automation rules (trigger conditions, action steps, delay logic) are documented during discovery and delivered as a written Odoo Automated Actions and Server Actions inventory. Odoo's base.automation model handles scheduled and event-triggered automations, but the trigger conditions and action set differ from Textline's builder model. Admin rebuild is required; we do not migrate automation logic as executable code.

Textline provides aggregated performance metrics including NPS scores, CSAT surveys, and agent statistics. These are reporting aggregates stored outside the contact record and have no migration target in Odoo CRM's standard data model. We note the existence of these reports in the discovery output and recommend exporting them as PDF or CSV from Textline for archival purposes.