Migrate from Textline to Twenty CRM

Textline Contact records (name, phone, email, tags, notes) map to Twenty Person records. Custom address book fields (Standard and Pro only) require pre-creation in Twenty's Settings → Data Model before import, as Twenty does not create fields during CSV import. Phone numbers map to the phone field; multiple phone types may require a custom field. Tags migrate as Twenty tags on each Person record.

Textline Departments group phone numbers by location or function. We migrate department names and the associated phone numbers as either a Company record (if each department maps to a business entity) or a custom object (if departments represent internal organizational units). The customer chooses the model during scoping, and the custom object schema is created in Twenty before import.

Textline Conversations (SMS threads tied to a contact's phone number) transform into Twenty activity records. Each message in a thread becomes a Note or Task entry on the associated Person record with the original timestamp, direction (inbound/outbound), and message body preserved. MMS attachments are referenced by URL in the Note body if the destination supports media display. Large conversation histories require per-conversation pagination since Textline has no bulk conversation export endpoint.

Textline Agents map to Twenty workspace Members. We resolve agents by email match and map their department assignments to either a custom Person field (department name) or a lookup to the Company or custom object representing their department. If the destination Twenty instance uses a different email domain, agents must be provisioned before the migration phase so that OwnerId references are satisfied.

Textline Message Templates (canned replies with shortcut codes) are exported as Note records during migration, with the template body and shortcut codes preserved. Twenty has no native template library for SMS, so we document templates in a rebuild inventory for the customer to recreate manually or connect to a third-party SMS integration post-migration.

Textline tags applied to contacts migrate as a flat tag list on the corresponding Twenty Person record. Tag taxonomy and naming conventions are preserved as-is. If a contact has multiple tags, they become multiple Tag records linked to the same Person.

Textline Announcements (bulk outbound messages) are documented as a list of announcement records with recipient counts and message content. Twenty has no native bulk outbound SMS feature, so announcements require a third-party SMS integration post-migration. We deliver the announcement history as a rebuild reference document.

Textline Automations (keyword triggers, scheduled messages, contact-action rules) are documented with their trigger conditions, action sequences, and delay settings. Twenty's workflow builder supports record-triggered and scheduled automations, but Textline automations cannot be migrated programmatically. We deliver a written inventory of every active Automation with its configuration and recommended Twenty Workflow equivalent for the customer's admin to rebuild.

Textline Routes (inbound message routing rules that assign messages to agents or departments based on conditions) are not exposed via the Textline public API and cannot be migrated programmatically. We document the routing logic during discovery so it can be manually recreated in Twenty's workflow builder or assignment rules. This is flagged as a gap in the migration scope and addressed in the rebuild inventory.

Textline provides built-in performance metrics (NPS surveys, CSAT scores, agent statistics) that are aggregated reporting data with no migration target in Twenty CRM's standard objects. We deliver the most recent metric snapshots as a CSV reference file for manual entry into Twenty's reporting if needed, but these do not migrate as structured records.