Migrate from Orangescrum to Microsoft Project

Orangescrum Projects map to a Microsoft Project file or Project Online project site. Each Orangescrum project carries name, description, start/end dates, status, budget fields, and owner assignment. We map these to the Project Summary Task fields (Project Title, Manager, Start Date, Finish Date) and Notes field. Orangescrum Milestones map to Microsoft Project milestone tasks (zero-duration tasks with a milestone marker). If the destination is Project Online, we create a PWA project entry per Orangescrum project.

Orangescrum Tasks are the primary work unit and map directly to Microsoft Project Tasks. We migrate title, description, priority, status, assignees, and due dates. Orangescrum priority values (low, medium, high, urgent) map to Microsoft Project Priority field (text values). Orangescrum task status (open, in progress, completed, on hold) maps to Microsoft Project percent complete and status fields. Due dates become finish dates in Microsoft Project. Orangescrum task dependencies (parent-child through subtasks) are converted to explicit predecessor-successor links in Microsoft Project using Finish-to-Start dependencies as the default.

Orangescrum Subtasks inherit parent project and task context. We map them to Microsoft Project outline levels beneath the parent task. Orangescrum supports subtasks up to two levels of nesting. Microsoft Project supports unlimited outline levels; we preserve the original nesting depth to maintain the work breakdown structure. If the customer used sub-subtasks, these appear as further-indented outline rows in the destination project file.

Orangescrum Time Logs link hours to a task, a user, and include a date and optional billing notes. We aggregate all time log entries per task by summing hours and assign the total to the Microsoft Project Task Work field. If a task has time logged by multiple users, we note the breakdown in the Task Notes field or a custom text field. Actual work versus planned work is not directly migratable unless Orangescrum tracks planned hours separately; we flag this gap during scoping.

Orangescrum Sprints have a start/end date, goal, and linked tasks. Sprints do not have a native Microsoft Project equivalent — sprints are an agile container, not a scheduling construct. We convert active Sprints to summary tasks with a start date and finish date that encloses their member tasks, or to milestone markers at the sprint start. Backlog items without a sprint assignment are listed as unscheduled tasks in a separate task group that the project manager assigns during the first schedule baseline in Microsoft Project.

Orangescrum Users carry name, email, role, and active/inactive status. We map them to Microsoft Project Resources (type Work Resource). The Orangescrum role maps to the Resource Initials or Resource Name field. Standard rate is not set from Orangescrum unless the customer has configured resource billing rates; we flag this as a manual step. Inactive Orangescrum users are imported as resources but can be marked inactive in Microsoft Project. Project Online resource management requires SharePoint user profiles to exist in the tenant.

Orangescrum supports custom fields on tasks, projects, and tickets with text, number, date, dropdown, and checkbox types. Microsoft Project custom fields support text, cost, date, flag, number, and formula variants. We map field names and types explicitly during scoping. Dropdown fields from Orangescrum map to custom picklist fields in Microsoft Project; checkbox fields map to flag fields. Custom fields at the project level map to project-level custom fields (Summary Task fields in Project Online). If the destination is Project Desktop, custom fields require the Custom Fields dialog to be configured manually or via VBA/macros.

Orangescrum Epics and Features are hierarchical containers above Tasks available on Premium and Enterprise tiers. Microsoft Project has no parallel Epic or Feature construct. We map Epics to top-level summary tasks (Phase-level outline rows) with their linked tasks indented beneath. Features map as child summary tasks within the Epic group. If the destination does not use summary task grouping, we flatten Epic-Feature-Task into a task name prefix convention (e.g., [Epic Name] Feature Name: Task Name) for visual grouping in the Gantt view.

Orangescrum generates invoices from time logs and billable entries. Invoice metadata — client reference, line items, amounts, status, and date — migrates to a project-level notes record or an external CSV reference sheet. The rendered PDF files do not migrate. Customers who need invoice copies for accounting or audit purposes must export them manually from Orangescrum before cutover or reconstruct them in a dedicated accounting system. We include an invoice metadata CSV in the migration package for the customer's finance team to import into their accounting tool.

Orangescrum Bug records are a task subtype with severity, reproduction steps, and status fields. We map them to Microsoft Project tasks with the Bug type indicated in the task name prefix (e.g., [BUG] Task Name) or a custom flag field is_bug__c set to Yes. Severity values from Orangescrum map to a custom text or flag field for filtering in the Gantt view. Reproduction steps migrate to the task Notes field. Status resolves against the task's percent complete in Microsoft Project.

Orangescrum Wiki pages contain rich text content linked to Projects under Categories and Sub-Categories. We do not migrate Wiki content as a native object. We export Wiki pages as standalone HTML or Markdown files and include them in the migration package as a reference document archive. If the destination is Project Online, SharePoint pages can be manually recreated using the exported content. The customer decides whether to rebuild wiki content during post-migration setup.