Migrate from Orangescrum to Asana

Orangescrum Projects map directly to Asana Projects with name, description, start/end dates, and owner preserved. Milestone relationships map to Asana Milestones where the target workspace has Milestones enabled, or to parent tasks with a Milestone tag where not. Project-level budget fields from Orangescrum migrate to Asana Custom Fields as number or currency fields and are recreated during scoping.

Orangescrum Tasks map 1:1 to Asana Tasks with title, description, priority, status, assignee, due date, and custom field values preserved. Orangescrum task status values map to Asana section membership or custom status fields depending on the target workspace configuration. Subtask nesting depth is preserved up to two levels per the source platform's constraint.

Orangescrum Subtasks inherit parent project and task context. We map them as Asana Subtasks (the subtask field on a parent task) with title, status, and assignee preserved. Parent project and task context is maintained through the Asana task hierarchy. Nesting beyond two levels flattens to the second level; we document this constraint during discovery so the customer can decide on a flattening strategy.

Orangescrum Sprint records (available on Agile-enabled projects) have start/end dates, goal text, and linked tasks. Asana has no formal sprint object; we map sprint name to a Sprint custom field on tasks, assign the sprint's start and end dates as task Start Date and Due Date in Asana Timeline view, and link all tasks to the same timeline range. The sprint goal migrates as a task note on the first task in the sprint or as a project-level description tag. We document sprint assignments during discovery so the customer can choose whether to use Asana's Timeline view or My Tasks for sprint planning.

Orangescrum Backlog holds stories not yet assigned to a sprint. Asana has no native backlog concept. We create a dedicated Backlog project in Asana and migrate backlog stories as tasks within it, preserving ordering by task position or a custom sort field. Backlog priority and story points migrate as custom fields. The customer decides whether to keep a separate backlog project or distribute stories across sprint projects post-migration.

Orangescrum Custom Fields (text, number, date, dropdown, checkbox) on tasks, projects, and tickets do not export their schema definition in a transferable format. We map field names and types explicitly during scoping, recreate the destination field schema in Asana using Asana's Custom Field types (text, enum, number, date, people), and migrate values field-by-field during data load. This is explicit mapping work rather than an automated schema transfer.

Orangescrum Time Log entries link to a task, a user, and include hours, date, and optional billing notes. Asana has no native time log object; we migrate hours as structured task data. If the customer's Asana workspace has the Asana Time Tracking integration enabled, time logs map to that integration's logged hours. Otherwise, we store hours in a Time Logged custom field (number type) and the billing note as a task comment or note. Billable hours attached to invoice line items migrate alongside invoice metadata.

Orangescrum Users (name, email, role, active/inactive status) map to Asana Users resolved by email match. Role-based permissions from Orangescrum do not have a direct Asana equivalent; we map Orangescrum roles to Asana Teams and document the mapping for the customer's admin to configure team-level permissions post-migration. Inactive Orangescrum users migrate as inactive Asana guests or members at the customer's discretion.

Orangescrum distinguishes internal Team Members from external Client contacts. Client records include company name, contact info, and billing details. We migrate Clients as Asana Project members (for project collaboration) and optionally as Contacts in a CRM system where the customer maintains one. The split depends on how the customer uses Clients in Orangescrum; we confirm during discovery whether Clients are project stakeholders or billing contacts.

Orangescrum invoices generate from time logs and billable entries with line items, totals, status, and client reference. Asana has no native billing module. We migrate invoice metadata — client, line items, amounts, status, and date — as structured task data in a dedicated Invoice Log Asana project, or as custom fields on tasks linked to the relevant project. Orangescrum renders invoices as PDFs that are not exportable in a transferable format; we flag this and recommend a pre-cutover PDF export from Orangescrum for accounting purposes.

Orangescrum Epics and Features (Premium and Enterprise tiers) are hierarchical containers above Tasks. Asana has no Epic object; we map Epics to Asana Portfolios (Enterprise) or to parent tasks with an Epic tag, and Features to sub-tasks or custom field groupings. If the target workspace is on an Asana tier without Portfolios, we use project groupings and custom fields to preserve the hierarchy. We confirm the Asana edition during discovery.

Orangescrum Wiki pages have Categories, Sub-Categories, rich text content, and project links. Asana has no wiki module. We migrate wiki pages as Asana tasks with [Wiki] prefixed to the title, rich text preserved in the task description, and category hierarchy mapped to a custom field or naming convention. Project-linked wiki pages become tasks within the relevant project. Content volume is scoped during discovery; large wiki volumes add to migration time because of content review and formatting reconciliation.