Migrate from Resco – Mobility & Productivity to monday CRM

Resco Contact records sync from the underlying CRM and map 1:1 to Monday.com CRM People items. Name, email, phone, company association, and address fields migrate as typed People columns. Ownership assignment from Resco maps to the Assignee column in Monday.com, with the understanding that Monday.com uses item-level assignment rather than a record-owner security model.

Resco Account records (mirrored from the underlying CRM) map to Monday.com CRM Companies. Company name, domain, industry, address, and annual revenue fields map to the equivalent Company columns. We resolve the parent-company relationship as a Company group or linked Company column on the Contact item.

Resco Work Order records map to items in a Work Order board. Each work order becomes a single item with columns for Work Order number (text), status (status column mapping Resco status values to Monday status groups), assigned technician (person column), scheduled date (date column), location (location column), and associated Contact (-connect board column linking to People). Photos captured in the field migrate as file attachments on the item.

Resco inspection questionnaire definitions are configuration artifacts, not transactional records. Each questionnaire template becomes a separate board or board group. Completed inspection responses become items within that board, linked to the originating Work Order via a board-connect column. Logic branches in the Resco questionnaire must be flattened into column dependencies or separate item groups in Monday.com, as the routing logic does not migrate.

Resco Mobile Auditing records preserve GPS location, timestamp, and user attribution. Each record becomes a location-column item in a Location board linked to the associated Work Order or Contact. The Resco Owner field (set to the tracking user) is preserved as a Person column; we flag during migration that Monday.com location data is item-attributed rather than user-owned for audit purposes, and the customer admin documents the difference for compliance.

Resco Route Plans are optimized sequences generated by the routing engine and are configuration data rather than transactional records. We do not migrate Route Plans as a distinct object. Instead, we migrate the constituent Work Orders in sequence order and deliver a document listing each route plan with its ordered stops so the customer's admin can recreate the grouping in Monday.com as a board group or timeline view.

Woodford-configured custom entities that have a schema mirror in the underlying CRM migrate to Monday.com as custom boards with columns mapped to the entity fields. Any custom entity without a CRM-level mirror requires the customer to define the board structure before migration; we deliver a schema specification document listing each custom entity, its fields, field types, and recommended Monday.com column equivalents for the admin to implement.

Resco documents and photos linked to Work Orders, Inspections, or Contacts migrate as file attachments on the corresponding Monday.com item. Files stored in Resco's external storage integration (Dropbox, Google Drive, OneDrive, SharePoint) are re-linked by migrating the file URL as a text column with the file host reference; the customer must ensure the destination storage permissions allow Monday.com access.

Resco activity records (calls, emails, meetings, tasks) linked to Work Orders or Contacts migrate as Update entries on the corresponding Monday.com item. Each activity becomes a timestamped update with the activity type, notes, and assigned owner. This preserves the audit timeline in Monday.com's collaborative feed rather than as a separate object.