Migrate from Textline to monday CRM

Textline Contacts (name, phone, email, notes, tags) map to Monday.com CRM Items in the Contacts board. The phone number becomes a Phone column; email becomes an Email column; tags migrate as a Tags column or flat text field depending on Monday.com column availability. Custom address book fields from Textline Standard and Pro tiers map to Monday.com column types (text, number, date, dropdown) configured before migration. Contacts without a matching Monday.com User as owner are assigned to a default owner for reconciliation.

Textline Conversations migrate as Items in a dedicated Activity board linked to the Contact Item via a Connect Boards column or subitem structure. Each message in the thread becomes an entry with direction (inbound/outbound), timestamp, content, and agent attribution. The per-conversation export limitation in Textline's API requires chunked extraction; we batch by date range and map each thread to the correct Contact Item using the phone number as the dedupe key.

Textline Departments (grouping phone lines by location or function) map to Monday.com Groups within the CRM board. If departments represent distinct business units, we create separate boards with a master Contacts board linked via Connect Boards. The department-to-agent assignment migrates as an ownership or column assignment in Monday.com.

Textline Agents map to Monday.com Users by email match. We extract agent names and their department assignments. Permission levels and custom roles in Textline have no direct Monday.com equivalent; we document the permission matrix for the customer's admin to reconfigure in Monday.com Workspace settings.

Textline canned reply templates (body text and shortcut codes) export as template text. Monday.com does not have a native template library for CRM contacts; templates may be stored as a separate board with pre-written text or recreated as Monday.com Autoflows or Textline-compatible snippets. We preserve the template body and shortcut codes in the migration deliverable for manual placement.

Tags applied to Textline Contacts migrate as Tags column values in Monday.com CRM Items. Tag taxonomy and naming conventions are preserved as-is. If the destination board does not support the Tags column type, tags migrate as a text column with comma-separated values for manual cleanup.

Textline Announcements (bulk outbound messages) and their associated contact lists are exported as Items in a dedicated Broadcasts board. The original contact list is stored as a subitems list or linked Items in the Contacts board. The broadcast sending mechanism must be replicated using Monday.com Automations or a third-party SMS integration post-migration.

Textline Automations (keyword triggers, scheduled messages, contact-action triggers) are documented with their trigger conditions, delay settings, and actions. Monday.com Autoflows use a different trigger-action model scoped per board. We deliver a written automation inventory with Monday.com equivalents so the customer's admin can rebuild. Automations do not migrate as code.

Textline Routes (inbound message routing rules) are not exposed via the public API and cannot be migrated programmatically. We document the routing logic during discovery by interviewing the customer and reviewing the Routes configuration in Textline. Routing is recreated manually in Monday.com using Assign To rules, Autoflows, or team-based board permissions post-migration.

Textline phone numbers assigned to Departments are preserved as text values in the Contact Item or in a separate Phone Numbers board linked to Contacts. The phone-number-to-department assignment is stored as a Department column on the Contact Item. MMS attachment URLs are preserved where accessible and re-hosted or linked in the destination as appropriate.