Migrate from Intervals to monday Work Management

Intervals Clients are the top-level organizational unit and map to monday.com Workspaces. Each Client becomes a separate Workspace with the Client name as the Workspace name and the Client status (active/inactive) preserved. If the customer's Intervals account has multiple active Clients, we create one monday.com Workspace per Client to maintain the separation of client-facing work. Workspace-level permissions replace Intervals' access-level roles (admin, member) but require manual configuration in monday.com Settings post-migration.

Intervals Projects belong to Clients and carry budget, start/end dates, and status. Each Project maps to a monday.com Board within the corresponding Workspace. We preserve the project-to-client ownership by placing each Board inside the Workspace created for its parent Client. Budget amounts and start/end dates transfer to custom number and date columns on the Board since monday.com does not have native per-project budget fields. Project status (active, on hold, completed) maps to a status column on the Board.

Intervals Milestones are date-driven checkpoints within a Project with optional comments. monday.com has no native Milestone object, so we replicate milestone behavior using date columns, timeline columns, or automation triggers. Target dates migrate to date or timeline columns with milestone name preserved as the column label. If the customer uses milestone-to-task linkage (milestones grouping multiple tasks), we document the linkage in a milestone-referencing custom column and advise on rebuilding via monday.com automation triggers at cutover. Milestone comments map to Board-level updates or Updates columns.

Intervals Tasks belong to Projects and optionally to Milestones. Each Task maps to a monday.com Item within the corresponding Board. Task status (pending, in progress, completed) maps to a status column. Estimated hours and actual hours migrate to number columns. Assignees (People) map to monday.com People columns by resolving the Intervals person email against the monday.com workspace member list. Task-to-Milestone linkage is preserved by assigning the same timeline or date value to the Item that corresponds to its milestone target date.

Intervals Task-level comments are threaded text entries attached to Tasks. monday.com stores comments natively on Items via the Updates column. We migrate Intervals Task comments as monday.com Item updates, preserving the comment author (mapped to the corresponding monday.com workspace member) and the original timestamp. Threaded replies preserve their parent comment order.

Intervals Milestone comments are threaded entries tied to Milestones. Since monday.com has no dedicated milestone object, we migrate Milestone comments as Board-level Updates or as comments on a designated date Item representing the milestone checkpoint. The milestone name and target date are preserved alongside the comment history for audit purposes.

Intervals Project Notes are standalone text entries scoped to a Project but not tied to Tasks or Milestones. We migrate Project Notes to the Board description field or to a dedicated text column on the Board. If the customer has many Project Notes, we recommend a Document column linking to a Google Docs or shared drive file containing the full note history.

Intervals custom activity fields are user-defined properties attached to time entries and are not visible in standard CSV exports — they appear only via the API. We enumerate all active custom activity fields during the discovery phase by querying the Intervals API, then map each to a corresponding monday.com custom column. monday.com supports 30+ column types including text, number, date, dropdown, checkbox, and rating. We match the Intervals field type to the nearest monday.com column type during mapping. If the destination Board does not yet exist, we create custom columns before importing time entry data.

Intervals Time Entries are the primary data object recording hours, date, task association, and billable status. We migrate time entries as time-tracking data in monday.com's Time Tracking column (available on Pro plan and above at $24/seat/mo) or as structured number columns with a date context for historical billing history. Each time entry is linked to its parent Task Item via the time tracking association. Billable status migrates as a checkbox column. Chronological ordering is preserved by setting the date value to the original Intervals timestamp. Time entries without a parent Task are stored as standalone time records on the Project Board.

Intervals People are user accounts with timesheet permissions and roles (admin, member). We migrate People as monday.com Workspace members, preserving their name and email address. Active/Inactive status from Intervals maps to the member's invited/active status in monday.com. Access-level roles (admin, member) are noted in a custom text field on each member record for the customer's admin to map to monday.com Workspace roles post-migration since monday.com's permission model is structured differently (Workspace owners vs members vs guests).

Intervals Documents are attachments stored within Tasks or Projects, but the platform explicitly states that documents cannot be bulk exported — only individually downloaded. We do not migrate documents programmatically because no bulk retrieval mechanism exists. We flag this as a manual-step gap during scoping: we document every document URL (organized by Project and Task) in a checklist for the customer's team to download manually before or after migration. monday.com supports file attachments via Google Drive, Dropbox, and OneDrive integrations, but the source files must be available.

Intervals Per-task and per-project budget tracking (budget amount vs. logged hours) is a core billing feature. monday.com does not have a native budget tracking field. We migrate budget amounts as number columns and advise the customer on rebuilding budget-vs-actual calculations using monday.com's formula column capabilities or a third-party integration (e.g., a Google Sheets sync). The budget-to-actual burn rate calculation is not automated in monday.com without additional configuration.