Migrate from BigPicture to Trello

Each Jira project in BigPicture becomes a Trello Board within the customer's Workspace. If multiple Jira projects share a Box in BigPicture, they map to separate Trello Boards; the Box-level grouping is documented in a written Workspace structure inventory for the customer to apply in Trello manually post-migration. Board descriptions carry the original Jira project key as a reference field.

Jira issues are the atomic data unit and migrate 1:1 to Trello Cards. The Jira issue Summary maps to Card name; Description maps to Card description (preserved as plain text or Markdown depending on source formatting); Status maps to a Trello List (created per Jira status category). Assignee maps to a Trello Member lookup by email. The Jira issue key is preserved in a Card custom field for cross-reference. Custom fields on the Jira issue carry through as Trello custom fields (requires Premium Power-Up on Standard tier).

BigPicture Boxes are top-level portfolio containers that hold multiple Jira projects. There is no direct Trello equivalent. We document the Box-to-project membership in a written structure inventory, split the Box contents into their constituent Trello Boards, and flag which Boards belong to the same original Box so the customer can optionally use Trello Workspace tags or a naming convention to preserve the grouping.

BigPicture Gantt data — including start/end dates, duration, dependencies (finish-to-start, start-to-start), constraints, and critical path — is stored as BigPicture module data on top of Jira issues. We export to MS Project MPP/XML format (BigPicture's supported export format) preserving all dependency links, then map to Trello using a Timeline Power-Up or documented manual re-entry. Jira issue start and end dates carry forward as Card due dates where available; BigPicture-specific timeline fields (Baseline Start, Baseline Finish, Constraint Date) are preserved in the MS Project file and flagged in the export summary.

BigPicture Roadmap views are constructed from Box and project timeline data. We preserve the roadmap view structure and issue-to-timeline mapping as a written inventory with Jira issue keys, timeline positions, and milestones. The roadmap itself does not have a native Trello equivalent; we recommend the customer rebuild using Trello Calendar Power-Up (mapping card due dates to calendar events) or a third-party roadmap tool linked back to the Trello boards.

BigPicture Scope trees are hierarchical WBS structures attached to Jira issues. We flatten them into Trello Card checklists, preserving parent-child relationships as checklist item indentation levels. Each WBS level beyond the top task becomes a checklist entry. Items that cross card boundaries are documented with cross-references so the customer can recreate the full WBS view in Trello or a linked tool. Large Scope trees may exceed Trello's 500-checklist-item-per-card limit; we flag these records for manual splitting.

BigPicture Risks are tracked with probability, impact, status, owner, and mitigation fields. We map these to Trello Cards with a custom fields Power-Up: probability as a number or select field, impact as a select field, status as a label colour, owner as a Member assignment, and mitigation as a Card description section. Risk Register structure (the list of all risks) is preserved as a dedicated Trello Board with one Card per risk.

BigPicture resource allocation data — capacity, utilisation, and member workload — has no direct Trello equivalent on Standard or Free tiers. We preserve the allocation data as a written resource inventory (CSV export) with member names, project assignments, and utilisation percentages. On Premium tiers, the Trello Workload Power-Up provides a basic capacity view. The customer decides during scoping whether to use the Power-Up or maintain resource planning in a separate spreadsheet.

BigPicture teams group members and assign them to work packages. We extract team membership and assignment records and map them to Trello Workspace Members by email match. Any BigPicture team without a matching Trello member goes to a reconciliation queue. Trello's Workspace-level permissions (Admin, Normal, Observer) do not map directly to BigPicture roles; we document the role-to-permission mapping for the customer to configure post-migration.

Jira issue attachments are standard Jira files accessible via the Jira REST API. We download and re-upload attachments to the corresponding Trello Card. Attachment filenames and timestamps are preserved. Large binary attachments (>10 MB) may be blocked by Trello's file size limits; we flag these individually and recommend an alternative storage reference (link to Jira Cloud, Google Drive, or Confluence).

Jira labels map directly to Trello Labels. Label names and colours carry through. If the BigPicture migration includes label-based categorisation for Risks, Scope items, or milestones, we preserve the label taxonomy in a written inventory so the customer can recreate it in Trello with consistent colour coding.

Jira issue comments migrate as Trello Card Comments with author name, timestamp, and comment body preserved. Author is mapped to the corresponding Trello member where an email match exists; otherwise the original Jira author name is retained as plain text.