Migrate from Orangescrum to Trello

Each Orangescrum Project becomes a Trello Board. Project name, description, start/end dates, and status migrate to the Board title, description, and optional cover colour. Milestones within a Project map to Lists within the Board; Trello has no native milestone object so milestone due dates become Card due dates with a milestone label. If the customer uses Orangescrum's Program Management module (Premium tier), multiple Programs map to multiple Boards within a Trello Workspace.

Orangescrum Tasks migrate to Trello Cards within the appropriate List. Task title becomes Card title; description migrates as Card description with rich text preserved as markdown. Priority (High/Medium/Low), status, assignee, and due date map to Labels, Member assignment, and Card due date respectively. Tasks with no sprint association land in the project's backlog List by default. Tasks that are subtasks of other tasks become Checklist items under the parent Card.

Orangescrum Subtasks at one nesting level become Trello Checklist items on the parent Card. Subtasks at two nesting levels flatten into Checklist sub-items or are promoted to separate Cards at the customer's discretion during scoping. Orangescrum's subtask title, assignee, and due date are preserved; completion status maps to the Checklist item checked state. Subtask custom fields are not supported in Trello Checklists and are flagged for the customer to add as Card labels or Power-Up data.

Orangescrum custom fields on Tasks map to Trello Custom Fields on Standard and Premium tiers. Text, number, date, and dropdown field types have direct Trello equivalents. Checkbox fields map to a Label with a binary label name. On Trello Free tier (which lacks Custom Fields), we remap all custom fields to Labels with the field name as label prefix and the value as label text. We document the full custom field inventory during scoping so the customer can choose between Free tier with Labels or upgrading to Standard for typed fields.

Orangescrum Sprints have no native Trello equivalent. We map each Sprint to a dedicated List within the project's Board, naming it with the Sprint label and optionally the date range. The Sprint goal migrates as the List description. Active sprints become Lists with a defined set of Cards; completed sprints are archived as closed Lists. Velocity and burndown data from Orangescrum cannot migrate to Trello and is delivered as a written data extract for the customer to store externally. If the customer uses the Scrumban board (Premium), we create a parallel Kanban-style List structure alongside the sprint Lists.

The Orangescrum backlog — unassigned stories and tasks not yet in a sprint — maps to a dedicated Backlog List on the Board. Backlog item ordering is preserved by Card position within the List, giving the team a prioritised backlog to pull from during sprint planning. Story point values from Orangescrum move to Card description or a custom field if the Standard/Premium tier is selected.

Orangescrum Epics and Features (Premium tier) are hierarchical containers above Tasks. Trello has no native Epic or Feature object, but we map Epics to parent Boards within a Trello Workspace and Features to Labels on Cards within those Boards. If the customer does not use Trello Business Class or Enterprise, which allow Board cross-linking, we use a naming convention (Epic Name > Feature Name > Card Title) within a single Board. This is documented explicitly in the scoping deliverable so the admin can decide on the structure.

Orangescrum Users (name, email, role, active/inactive status) migrate to Trello Workspace Members. We map Orangescrum role assignments (Admin, Manager, Member, Client) to Trello's Workspace-level permission model (Workspace Admin, Workspace Normal Member, Workspace Guest). Client contacts from Orangescrum who were assigned to tasks become Trello Board Guests if they need limited access, or Workspace Members if full visibility is required. Inactive Orangescrum users migrate as deactivated Trello members at the customer's election.

Orangescrum Client records (company name, contact info, billing details) have no direct Trello equivalent. We map the Client name to a Label with the prefix 'Client:' and the company name; if the customer needs client-level visibility, we create a Trello Workspace Member record with Guest permissions for each unique Client contact. This decision is made during scoping. We do not migrate billing address, payment terms, or invoice history to Trello as these fields do not exist in the platform.

Orangescrum Bug records are a task subtype with severity, reproduction steps, and status. We map them to Trello Cards within the same Board, applying a 'Bug' Label and a severity Label (Critical/High/Medium/Low). Reproduction steps and additional bug details migrate to the Card description. If the customer plans to integrate with Jira for bug tracking post-migration, we tag Bug cards with a Jira-compatible label naming convention (e.g., 'jira:BUG-XXXX') to simplify the Jira card creation workflow.

Orangescrum Wiki pages with rich text and category hierarchy do not have a native Trello equivalent. We migrate Wiki page content as plain text appended to the Board description or, for pages linked to specific projects, to a designated Card description with a 'Documentation' label. Customers who rely heavily on Orangescrum Wiki should plan to move documentation to Confluence or a similar wiki tool post-migration; we deliver a written index of all Wiki pages with their category hierarchy and content summary for manual reconstruction.

Orangescrum Time Logs — hours, date, user, task link, billing notes — have no Trello equivalent. Trello has no native time tracking, and no standard Power-Up on the Free or Standard tier provides billing-capable time logging. We export Time Logs as a CSV with task reference, user, hours, date, and billable flag, and deliver it to the customer for import into a dedicated time tracking tool (Toggl, Clockify, Harvest, or similar). If the customer has a Premium Trello subscription and uses a compatible time-tracking Power-Up, we can map time log entries to that Power-Up's data format during migration. Time log data is never deleted from the export; it is always preserved.

Orangescrum Invoices generated from time logs and billable entries — line items, totals, status, client reference — have no Trello equivalent. Trello has no billing or financial object. We export Invoice metadata (client name, invoice number, line item totals, status, date) as a CSV and flag it for import into the customer's accounting tool (QuickBooks, Xero, FreshBooks, or similar). Rendered PDF invoices are not migrated as Orangescrum does not expose them via standard export; the customer exports these manually before cutover. We do not generate new invoices in the destination.