Migrate your Orangescrum data

Projects carry name, description, start/end dates, status, budget fields, and owner assignment. We migrate them 1:1 and preserve parent-child relationships to Milestones.

Tasks are the primary work unit in Orangescrum. We migrate title, description, priority, status, assignees, due dates, and custom field values. Subtask nesting depth is preserved up to two levels.

Subtasks inherit parent project and task context. We map them into the destination as nested tasks or sub-issues depending on the target system schema.

Orangescrum supports custom fields on tasks, projects, and tickets. Field types include text, number, date, dropdown, and checkbox. We map field names and types explicitly during scoping because destination systems often use different field type semantics.

Time entries link to a task, a user, and include hours, date, and optional billing notes. When the destination is a CRM or invoicing tool, we map hours to billable time entries. When migrating out of Orangescrum, we export all logged hours as a time-entry CSV alongside the task hierarchy.

Users carry name, email, role, and active/inactive status. We map them to the destination's user records and preserve role-based permissions where the target supports role mapping.

Orangescrum distinguishes between internal users and external Client contacts. Client records include company name, contact info, and billing details. We migrate Client records separately from Team Members and map them to the destination's account or contact object.

Sprints exist only on Agile-enabled projects. Each Sprint has a start/end date, goal, and linked tasks. The backlog holds unassigned stories. We preserve sprint association and backlog ordering, but note that not all destination PM tools have a separate backlog concept.

Epics and Features are hierarchical containers above Tasks, available on Premium and Enterprise tiers. We map them as parent groupings in the destination. If the target does not have a parallel Epic/Feature concept, we flatten them into parent Projects or Projects with custom labels.

Orangescrum generates invoices from time logs and billable entries. Invoice records include line items, totals, status, and client reference. We migrate invoice metadata (amount, status, client link) but not the rendered PDF unless explicitly requested.

Kanban view is a presentation layer on top of Tasks. We migrate the underlying task data; column positions and board layouts are derived from task status in most destination systems.

Orangescrum includes a Wiki with Categories and Sub-Categories. Wiki pages contain rich text content and can be linked to Projects. We migrate pages as text blobs with metadata, preserving category hierarchy.

Bug records are a task subtype with severity, reproduction steps, and status fields. We map them to the destination's issue or task object and preserve severity as a custom field or tag.