Migrate from MobiWork to monday CRM

MobiWork customers with a 'Customer' status map to monday CRM Contacts; Prospects without a closed-won deal map to Leads. Status is determined by the MobiWork customer record type. If the record has a closed-won quote or invoice, it routes as Contact. We preserve the original customer ID as a custom column for traceability.

MobiWork Work Orders have no direct CRM equivalent. We map them to monday CRM Deal items on a dedicated Work Orders board, with columns for WO number, description, status, priority, assigned technician, scheduled date, and completion date. The Deal Name maps to the monday CRM item name. Amount is pulled from the linked Quote or Invoice total if present.

MobiWork Quotes map directly to monday CRM Deals on a Quotes board. Quote number, description, line items, total amount, and status become Deal columns. Expiration date becomes a Date column. If a Quote converts to a Work Order in MobiWork, both the Quote (as a closed-won Deal) and the resulting Work Order (as a separate Deal item) are created in monday CRM, linked by a custom relationship column.

MobiWork Invoices map to Deal items on a Billing board, with columns for invoice number, total amount, balance due, payment status, and payment date. The linked customer maps to the monday CRM Contact. We surface invoice payment history as Activity updates on the Contact record so the billing relationship is visible in context.

MobiWork UDFs on Customers, Work Orders, and Invoices become monday CRM column definitions on the respective boards. We read the UDF type from MobiWork (text, number, date, dropdown) and select the closest monday CRM column type. Dropdown UDFs become monday CRM Status or Dropdown columns with the original pick-list values migrated as options.

MobiWork scheduling records — technician assignments, time windows, and dispatch events — are mapped to monday CRM Activity items on a Schedule board, linked to the relevant Work Order Deal and the assigned technician Contact. Note: monday CRM has no native scheduling engine; time windows and routing logic are not preserved and must be rebuilt as board filters or automations post-migration.

MobiWork's Parts & Services Catalog maps to monday CRM Product items on a Products board, with columns for part number, description, unit price, and inventory status. These are then linked to Deal items (Work Orders and Quotes) via monday CRM's Connect Boards column or item linking.

MobiWork's route optimization data — including stop sequences, geo-coordinates, and optimization scores — has no monday CRM equivalent. FlitStack exports the route configuration as a JSON reference. Your monday CRM admin rebuilds the route as board groups or filters using zip-code and region columns, optionally augmented by a third-party routing integration.

MobiWork file attachments on Work Orders and Invoices (photos, signatures, completed forms) re-upload to monday CRM file columns on the respective Deal items. Files are stored in monday CRM's workspace file storage. The original filename and upload timestamp are preserved in the file column metadata.

MobiWork's Crew feature — grouping multiple technicians into a dispatch unit — has no direct monday CRM equivalent. We export crew rosters as a CSV reference. monday CRM groups the technician Contacts into Teams (available on Standard and above) or uses Group by columns on the Schedule board to recreate crew visibility.

MobiWork's activity log entries — notes, call records, email logs — migrate as monday CRM Updates on the linked Contact and Work Order Deal items. Each activity preserves the original timestamp, author, and activity type. FlitStack sequences updates chronologically on the item's Activity timeline.

MobiWork tags attached to customers, work orders, and invoices are extracted and recreated as monday CRM Tags on the matching Contact, Deal, and Invoice items. Tag names are preserved exactly; FlitStack creates any missing tags in the workspace. Because tags are workspace-level, they can be reused across boards, providing consistent labeling and filtering for reporting and automations without redefining them per board.