Migrate from WeTrack to monday Work Management

WeTrack Projects (the top-level event delivery container) map directly to monday.com Boards. The Project name becomes the Board name, Project dates map to the Board's Date column, and Project status (Active, On Hold, Completed) maps to a Board-level Status column. If the customer uses WeTrack's Planning module to manage multiple event phases within a Project, those phases become monday.com Groups within the Board.

WeTrack Tasks map to monday.com Items. Standard task fields (name, description, start date, due date, assignee, status, RAG indicator) map to equivalent monday.com columns. The parent Project reference resolves to the Board ID during import. We flag any Tasks that reference an archived or deleted Project for customer review before migration.

WeTrack Subtasks map to monday.com Subitems attached to the parent Item (migrated Task). The auto-sync date behaviour from WeTrack (where parent task dates cascade to subtasks) has no native equivalent in monday.com; we document this dependency and recommend a specific monday.com automation setup (Date column referencing parent Item dates) as the replacement during the rebuild handoff.

WeTrack Risk Registers with Inherent Likelihood (1-5 scale) and Inherent Impact (1-5 scale) map to a set of monday.com custom columns: a Status column (RAG status: Red, Amber, Green), a Number column (Inherent Likelihood), a Number column (Inherent Impact), and a Text column (Risk Owner). Residual Likelihood and Impact fields map similarly if the customer uses them. Risk Register items become Board Items on a dedicated risk board linked to the parent Project Board via a Connect Boards column.

WeTrack's RAG status (Red, Amber, Green) cascades from parent Tasks to Subtasks on a configurable schedule. monday.com has no native RAG cascade rule; we map RAG values to a Status column with Red/Amber/Green labels and document the recommended monday.com automation: when Item status changes to a given value, update Subitem status to match. This automation rebuild is documented in the handoff package.

WeTrack's Sustainability module tracks ESG indicators (carbon footprint, waste reduction, diversity metrics, etc.) as records with flexible property sets. ESG metrics with simple numeric values (e.g., tonnage CO2, percentage renewable energy) map to monday.com Number columns on the Project Board. Complex or unstructured ESG records with multiple property types require monday.com Custom Objects, which are available from the Enterprise tier ($23/user/mo). We confirm the destination tier during scoping and design the ESG schema accordingly.

WeTrack Incident Reports map to Items on a dedicated monday.com Incident Board. The incident type (safety, operational, reputational) maps to a Status or Label column; severity maps to a Number or Status column; description and resolution notes map to Text columns. If the customer used WeTrack's flexible property sets for incident records, we map those to a combination of monday.com custom columns and flag any that require Custom Objects. Attachments on incident records migrate as monday.com file attachments.

WeTrack Job Categories restrict valid task-assignment values to prevent data entry errors. These map to monday.com Labels columns (multi-select) or Dropdown columns (single-select) on the relevant Board, depending on whether tasks in WeTrack could belong to multiple categories simultaneously. We flag any Job Categories that have no direct equivalent label in monday.com for manual reassignment.

WeTrack attachments of all types (documents, images, PDFs) migrate to monday.com file attachments on the parent Item (Task) or Subitem. We map file name, file type, uploaded-by user, and upload timestamp. Actual file content migrates if the files are provided as part of the structured export; if only file references exist in WeTrack, we document the missing assets for the customer to re-upload manually post-migration.

WeTrack custom fields on Projects map to monday.com custom columns. Standard field types (text, number, date, checkbox) map directly to equivalent monday.com column types. WeTrack custom fields that use picklist or multi-select behaviour map to monday.com Dropdown or Labels columns. Custom fields that do not have a direct monday.com equivalent (e.g., complex address objects, currency with custom formatting) are flagged for the customer to either simplify or recreate manually after migration.

Same mapping logic as Project custom fields applies to Task-level custom fields. We cross-reference the full export against the live WeTrack UI during discovery to identify any custom fields that appear in the UI but are absent from the standard export, mapping those as supplemental key-value records in a Text column and flagging them for review.

WeTrack user accounts and task owners map to monday.com team members. We resolve owners by email match against the monday.com workspace user list. Any WeTrack user without a matching monday.com account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive WeTrack users are mapped as inactive monday.com guests or deactivated depending on the customer's preference.