Migrate from Orangescrum to monday Work Management

Orangescrum Projects map directly to monday.com Boards. Each Project's name, description, start/end dates, status, budget fields, and owner assignment transfer to the corresponding Board name, description, and metadata columns. We create the board in monday.com before importing any items so that the board structure is established first. Projects linked to Milestones in Orangescrum create parent Groups within the destination Board.

Orangescrum Tasks are the primary work unit and map 1:1 to monday.com Items. Title, description, priority, status, assignee, due date, and custom field values transfer to the corresponding Item name, description, and column values. Status in Orangescrum maps to a monday.com Status column with values matched to the board's column configuration. Priority (low/medium/high/critical) maps to a Labels column or a Priority number column depending on the customer's preferred display.

Orangescrum Subtasks nest under parent Tasks and map to monday.com Subitems. Subtask title, description, status, assignee, and due date transfer to the Subitem. Subitem nesting depth is preserved up to two levels; if Orangescrum subtasks are nested three or more levels deep, we flatten the deepest level into the second-level Subitem and flag the flattening in the reconciliation report.

Orangescrum Sprints have a start/end date, goal, and linked tasks. In monday.com, Sprints are only available with the monday dev add-on. We confirm whether the customer has monday dev licensed before migration. If monday dev is available, Sprints migrate as monday dev Sprints with linked tasks preserved. If monday dev is not in scope, Sprints migrate as monday.com Groups labeled with sprint name, and sprint dates map to Timeline columns on each Group's items. Sprint goal text migrates to a dedicated Group description column.

Orangescrum Backlog holds unassigned user stories not yet in a sprint. We migrate the backlog as a dedicated Group (or multiple Groups if separated by epic/feature) in the destination Board. Backlog item ordering is preserved as item position within the Group. If the destination Board does not use Groups, backlog items land in the first board Group and are labeled with a Backlog Tag column.

Orangescrum Epics and Features are hierarchical containers above Tasks available on Premium and Enterprise. We map them as parent Groupings in the destination Board or as separate Boards within a Folder if the customer prefers a board-per-epic structure. The mapping choice is made during scoping. If monday.com's native Grouping is insufficient for a deep epic hierarchy, we create a Board per Epic and nest Feature boards within an Epic Folder.

Orangescrum Time Logs link hours to a task, a user, and a date with optional billing notes. monday.com has no native time-tracking object. We offer two migration paths: Path A creates a Subitem per Time Log entry on the parent Item with a number column for hours, a date column for the log date, and a text column for user reference. Path B creates a dedicated time-tracking Board with one Item per task and Time Log entries as Subitems linked back to the task board via monday.com's cross-board subitem linking. Path choice is made during scoping. Billable hours flag maps to a Labels column.

Orangescrum Custom Fields on tasks and projects (text, number, date, dropdown, checkbox) map to monday.com Column types with equivalent behavior. Text fields map to Text Column; numbers to Numbers Column; dates to Date Column; dropdowns to Dropdown Column; checkboxes to Checkbox Column. We capture the original field name as the Column name and document the full schema map in the scoping deliverable. If Orangescrum used a field type not supported by monday.com's native column set, we flag it for a custom column configuration or a third-party integration during post-migration setup.

Orangescrum Users (name, email, role, active/inactive status) map to monday.com Team Members. We resolve by email match against the destination monday.com workspace. Active/inactive status maps to the Person column assignment on items — inactive users are migrated as item assignees but their monday.com accounts are created as inactive Pending Members for audit continuity. Role-based permissions in Orangescrum map to monday.com workspace roles (Member, Admin, Viewer) during scoping.

Orangescrum distinguishes between internal Users and external Client contacts. Client records (company name, contact info, billing details) migrate to a dedicated monday.com Clients Board with Items per client and columns for company name, primary contact email, billing contact, and any billing details fields. Client links from Projects migrate as Items linked via the Connect Boards column to the relevant Project Board.

Orangescrum Invoice records include client reference, line items, amounts, status, and date. We migrate invoice metadata — client reference, line item descriptions, total amount, status, and date — as Items in a monday.com Invoices Board with corresponding column values. The rendered PDF files generated within Orangescrum do not migrate. Customers export PDFs manually before cutover or reconstruct them in a dedicated accounting tool post-migration.

Orangescrum Wiki pages contain rich text content linked to Projects with category hierarchies. monday.com has no native wiki object. We migrate wiki pages as Items in a dedicated Docs Board with the page title as Item name, page content as a long-text column, and category hierarchy preserved as a Tags or Dropdown column. Links between wiki pages and Projects are captured as Connect Boards columns linking to the Project Board.