Migrate from The Service Program to monday CRM

TSP Customers map directly to Monday CRM Contacts. The TSP customer name splits into first name and last name where available; single-string names map to the Full Name field. TSP stores one primary email and one primary phone per customer — both migrate as text columns on the Contact Item. Multi-site customers collapse to one Contact record with sites handled in the separate Sites board.

TSP Sites have a 1:N relationship with Customers — each Customer can have N sites. Monday CRM Contacts are flat records, so Sites migrate to a custom Sites board. Each Site becomes an Item; Monday relations link it to the parent Contact. Site name, address, city, state, and zip map to text columns. Site-specific contacts (a technician name per site) become text fields on the Site Item.

Monday CRM has no native work-order object. Every TSP Work Order becomes an Item in a custom Work Orders board. TSP work order number maps to the Item name. TSP status codes (Open, Scheduled, Completed, Invoiced) map to Monday Status column values. Technician assignment uses a Person column. The customer reference stores the TSP customer ID as a text field for linking. Line items (materials, labor) migrate as Monday sub-items with description and amount columns.

TSP work orders carry line items (service description, quantity, unit cost, total). Each line item becomes a Monday sub-item attached to its parent Work Order Item. Sub-item fields: description (text), quantity (number), unit cost (number), total (number). Sub-items preserve the per-line breakdown that TSP stores inside the work order — this is the closest Monday equivalent to TSP's multi-line work order structure.

TSP invoices are QuickBooks financial records. Monday CRM has no native accounting module. Invoices migrate as read-only Items in a separate Invoices board — invoice number, date, amount, status, and related work order number stored as text and number columns. For true accounting, customers keep QuickBooks and optionally rebuild the Monday–QuickBooks integration post-migration.

TSP technician names stored per work order (technician assigned to a job) map to a Monday Person column on the Work Orders board. Monday's Person column assigns a workspace member to an Item. If TSP technicians are not Monday workspace users, their names import as text and are flagged for admin to assign as Person values once user accounts are created.

TSP route planning generates ordered stop sequences with time windows per technician. Monday has no native geospatial route optimizer. We create a Routes board where each route is an Item, stops are sub-items with a Timeline column for the time window, technician is a Person column, and customer address is a text column. Actual route optimization requires a third-party routing tool re-connected post-migration.

TSP is a QuickBooks add-on — customer and invoice records carry QuickBooks internal IDs (ListID, EditSequence). These IDs migrate as text fields on the Monday Contact Item for reference and for re-establishing the QuickBooks integration after migration. Without these IDs, the Monday–QuickBooks integration must be rebuilt from scratch rather than synced.

TSP allows per-customer and per-site custom fields for industry-specific data. Monday CRM has no field-typing engine for custom data — TSP custom fields migrate as Monday text columns. Pick-list and date custom fields convert to Monday text or date columns respectively. We validate all custom field names and values during the mapping phase to avoid data truncation.

TSP work order notes and activity logs (internal comments, dispatch notes) migrate as Monday Updates on the Work Order Item. Updates preserve the original timestamp and author name where available. Monday Updates are the functional equivalent of TSP's per-work-order activity log.