Migrate from The Service Manager to monday CRM

TSM Contact records map to the Monday People Board. Each contact becomes an Item with Name, Email, Phone, Mobile, and Title stored as separate columns. The TSM organization link resolves to a Monday Company Board item if one exists; otherwise the organization name is stored as a text column.

TSM Organization (Company) records map to a Monday Company Board. Each organization becomes a Board Item with company name, domain, industry, employee count, and annual revenue stored as text, link, and number columns. Phone and address fields map to Monday's Phone and Address column types.

TSM Incidents have no Monday CRM native equivalent. We map incidents to a dedicated Services Board where each incident becomes an Item. Item name carries incident_title. Description, priority (P1–P4 mapped to Monday status labels), status (New / In Progress / Resolved / Closed), assigned_to, createdate, and resolvedate map to dedicated columns. SLA deadline fields become Date columns with conditional formatting logic documented for Monday automation recreation.

TSM Service Requests map to the same Services Board as Incidents using a Request Type column to distinguish them. Request type values (e.g., Password Reset, Access Request) become Monday Status labels. Affected CI (Configuration Item) fields become text or link columns pointing to Assets Board items.

TSM Assets and Configuration Items map to a Monday Assets Board. Each asset becomes an Item with asset name, asset tag, serial number, location, and assigned-to user columns. The assigned_to column links to the relevant People Board item via Monday's people column.

TSM User and Technician records map to Monday workspace members by email match. User display name and role (Resolver Group) are stored as text columns on a Team Board for reference. Inactive TSM users are imported as text names in assignee columns without creating Monday accounts.

TSM activity log entries (notes, comments, work notes on incidents) migrate as Monday Item Updates with original timestamps and author names. Long-form notes may be converted to sub-items with a Note label column to preserve formatting. Original timestamps are preserved in update metadata.

TSM file attachments download from the source and re-upload to Monday Files linked to the corresponding item via the Files column. Each file carries its original filename and upload date. Monday's 500MB per-file limit is checked before migration; files exceeding the limit are flagged for chunked upload or external link reference.

TSM custom fields on Contact objects require new Monday columns on the People Board. We create the column in the correct type (Text, Number, Date, Status, etc.) based on the TSM field data type. Multi-select picklist fields become Monday Status columns with options matching TSM picklist values exactly.

TSM custom fields on Incidents and Service Requests create new columns on the Services Board. Type-aware mapping applies: date fields become Monday Date columns, number fields become Number columns, and picklist fields become Status labels. The full custom field inventory is delivered in the pre-migration plan so columns are created before data insertion.

TSM workflows including assignment rules, SLA escalation timers, and auto-routing logic have no Monday CRM equivalent and are not migrated. We export all TSM workflow definitions as a structured reference document (JSON + human-readable summary) so your Monday admin can rebuild equivalent automations in Monday's automation builder.

TSM Knowledge Base articles are not migrated to Monday natively. We export article titles, body content, and linked KB categories as a document package. You can recreate them in Monday Docs, link them to Services Board items via URL columns, or import them into a separate knowledge-base tool.