Migrate from TaskRay to monday Work Management

Each TaskRay Project becomes a monday.com Board. We extract the Project Name, description, start and end dates, custom fields, and any Chatter threads or file attachments (as board-level pinned items or documents). Board structure in monday.com is created first so that all child Groups and Items have a valid parent Board reference during import. Folder grouping in monday.com Workspace maps to the customer's organizational convention (by team, client, or portfolio).

TaskRay Sub-Projects map to Groups inside their parent Board. Sub-Projects carry the same field structure as top-level Projects (custom fields, Task Groups, and Tasks) but roll up to the parent Project. We preserve the Sub-Project-to-Project parentage as a Group name prefix or as a Connect Boards column linking to the primary Board. Sub-Projects with nested Sub-Projects are flattened: the deepest child is promoted one level and the customer is warned that original nesting depth will be reduced.

TaskRay Task Groups map to Groups inside a Board, typically representing phases or thematic sections of a project plan. We preserve the Task Group-to-Project parent linkage by placing each Group inside the Board created from its parent Project. Task Group ordering within the Project is preserved as Group sequence order in monday.com.

TaskRay Tasks become monday.com Items within the appropriate Group. Task fields (Name, description, assignee, due date, priority, blocked/locked state, repeating flag) map to Item column values. Assignee resolution routes through email match against monday.com Workspace members. Due date maps to the Date column; priority maps to the Status or Numbers column using a configured priority label set. Blocked and locked states from TaskRay's custom fields map to a Status label or a dedicated checkbox column.

TaskRay Milestones are a distinct Task record type marked with a milestone flag. In monday.com we recreate them as Items with a dedicated Status label (e.g., 'Milestone') or as Items with a Date column value and a checkbox or label column distinguishing them from standard tasks. The milestone diamond-marker semantics are represented as a visual convention using Status labels rather than a native milestone object — there is no structural milestone object in monday.com equivalent to TaskRay's Plan View diamond icon.

TaskRay Checklist containers with Checklist Items map to monday.com Subitems on each Item. Each Checklist Item (with its completion state and ordering) becomes a Subitem. We preserve the checklist completion status as the Subitem's status or checkbox column value. Note: monday.com Subitems do not appear in individual users' My Day or personal to-do list views — only the parent Item surfaces in those views. This is a documented limitation of the pair. Customers relying on checklist items as individual assignable work units should be warned to restructure those items as standalone Items instead of Subitems.

TaskRay task dependencies (predecessor and successor links) map to monday.com's Dependency column, available on Pro and Enterprise plans. We extract predecessor references during export, match them to destination Item IDs, and populate the Dependency column at import time. Note that monday.com's Dependency column only supports blocking-type dependencies (Item A must be complete before Item B starts) rather than TaskRay's more granular finish-to-start, start-to-start, finish-to-finish dependency types. The pair-specific scope covers blocking dependencies only.

TaskRay Template Projects are migratable as standard Salesforce records via the Bulk API. However, the Template Migration feature (gated to Premium tier on source) must be identified during scoping. Templates migrate as Board copies in monday.com, but the Template configuration — including default Task Group structure, default fields, and Template-cloning settings — requires manual rebuild in monday.com using the Board Template feature. We deliver a written template inventory with recommended monday.com Board Template equivalents.

TaskRay Resources (individual users assigned to tasks) map to monday.com Workspace members by email match. We extract all distinct resource email addresses from Task assignee fields and cross-reference against the monday.com destination Workspace member list. Any TaskRay Resource without a matching monday.com user is placed in a reconciliation queue for the customer's admin to provision before task import begins. Roles (placeholder task owners without a specific user) are not migratable as Role objects in monday.com — we flag them as Items needing manual reassignment.

TaskRay files stored on Salesforce ContentDocumentLink are downloaded via the Salesforce API and re-uploaded to monday.com as Item file attachments. Each file is linked to the destination Item that corresponds to its source Task. File names, sizes, and upload dates are preserved. Very large files (exceeding monday.com's storage limits per plan) are flagged for the customer to store externally and link via URL column.

TaskRay's Field Trickler propagates Account and Opportunity lookups from Project to Task automatically. In monday.com there is no equivalent automatic lookup propagation. We extract the Account Name and Opportunity Name from TaskRay during export and write them as text columns on the corresponding Items. For customers needing true relational links, we create Connect Boards columns that reference separate Account and Project Boards, but this requires building the Account Board structure first. We document the lookup reconstruction strategy during scoping and apply it as post-import configuration.

TaskRay Basic Dashboards and Reports are Salesforce report records migratable via the Salesforce API, but custom report types and dashboard widgets do not transfer directly to monday.com's Dashboard feature. We extract the report and dashboard metadata (names, filters, chart types) as a written inventory. monday.com Dashboards are rebuilt manually using the Dashboard builder, and we provide the mapping from each source report to a recommended monday.com widget configuration. This is not a data migration — it is a rebuild scope documented for the customer's monday.com admin.