Migrate from Forecast to monday Work Management

Forecast Projects map 1:1 to monday.com Boards. We export the project name, status, start date, end date, description, and owner and land them as a monday.com Board with the board name set to the Forecast project name, status reflected in the primary group header, and start/end dates mapped to the board's date range or as dedicated Date columns. Custom Fields on the Project entity become board-level columns.

Forecast Phases map to monday.com Groups within a Board. Phase name becomes the Group name; phase-level Custom Fields migrate as Group-level columns. We preserve the phase sequence order by arranging groups top-to-bottom in the board. Phases are a mid-level grouping in Forecast, so they do not become separate boards, which would fragment timeline and dependency continuity.

Forecast Tasks map to monday.com Items. The task name becomes the item title, assignees map to the People column, due date maps to the Date column or Timeline span, status maps to a Status column with values matched to the Forecast task status options, and time estimate migrates to a Numbers column. Deeply nested Forecast tasks (grandchild tasks and beyond) are flattened into monday.com items with a Parent Reference column pointing to the parent item, preserving hierarchy for admin review.

Forecast Milestones are target-date objects tied to a Project. We map them to monday.com Items with a Date column capturing the milestone target date, and we optionally enable the Timeline column on the board so milestones appear as pinned dates on the project timeline view. Milestone name becomes the item title and the Status column is set to a milestone-completed or milestone-pending state.

Forecast text Custom Fields on Projects, Phases, Tasks, and Time Registrations map to monday.com Text columns. We preserve the field label as the column name. If the Forecast text field used numeric-only validation, we use a Numbers column instead. The customer confirms field intent during scoping since monday.com's column type cannot be changed post-creation without data loss.

Forecast numeric Custom Fields map to monday.com Numbers columns. We preserve precision and any unit suffix (e.g., hours, percentage) in the column name or as a separate label field. If the numeric field is used for budget tracking, we document it separately for the customer's admin to configure formula columns in monday.com.

Forecast choice Custom Fields map to monday.com Dropdown columns with the same option labels preserved. If the choice field maps to a workflow stage (e.g., not started, in progress, blocked), we use a Status column instead for color-coded visual workflow representation. The customer confirms which during scoping.

Forecast Time Registrations (hours logged against a task, date, billable flag, and optionally a rate) map to monday.com's native time tracking columns. This feature is available on monday.com Pro ($19/seat) and above. The billable flag from Forecast maps to a Checkbox column or a Status label on the time entry. If the customer is on Standard, we flag time tracking as a monday.com Pro dependency and document it in the scope before migration begins.

Forecast Rate Cards define hourly billing rates per role or person and are a core financial feature of Forecast. monday.com has no native rate card management. We export the rate card structure (role, person, hourly rate, currency) and deliver it as a structured CSV and documentation for the customer's admin to recreate in monday.com's Numbers columns, a connected spreadsheet integration, or a dedicated billing tool. This is a manual rebuild step outside the data migration scope.

Forecast Resource Assignments link team members to tasks with an allocated percentage or hours. We extract the assignment records and map them to monday.com People columns on the corresponding Items. Forecast's percentage allocation model does not have a direct monday.com equivalent, so we document the original percentage in a Numbers column (e.g., allocation_pct) for reference. Any assignments without a matching monday.com user email go to a reconciliation queue.

Files attached to Forecast tasks and projects migrate to monday.com Files columns attached to the corresponding Items. We preserve file name, upload date, and file size. Attachments over monday.com's per-seat storage limit (5 GB on Basic, higher on Standard+) are flagged for the customer to provision additional storage or archive before migration.

Forecast task comments map to monday.com Item Updates (formerly Pulse notifications). We preserve the comment author (by email lookup to monday.com user), the comment text, and the original timestamp. Threading is not preserved as monday.com's update feed is linear, not threaded. The most recent updates appear at the top of the item's activity log.