Migrate from BigPicture to monday Work Management

Jira projects map to monday.com boards. Each Jira project becomes a board in monday.com, preserving the project key as a board name prefix. We map Jira project roles (lead, member) to monday.com board owners and subscribers. If BigPicture programmes span multiple Jira projects, we group the resulting monday.com boards under a single workspace to replicate the programme-level view.

Jira issues migrate to monday.com items with all standard fields (summary, description, status, priority, assignee, reporter, fix version) mapped to equivalent monday.com columns. Jira issue key is preserved as a text field for cross-reference. Subtasks migrate as monday.com subitems attached to the parent item. Jira labels map to monday.com tags.

BigPicture programme Boxes have no native monday.com equivalent. We create a top-level monday.com board representing the programme, with the linked Jira projects represented as separate boards linked via the Integrations (Zapier/Make) or mirrored items. Alternatively, we use monday.com board groups for programme-level grouping and preserve the Box name and description in a programme document board for admin reference.

BigPicture Gantt configurations — including start date, end date, duration, dependency types (Finish-to-Start, Start-to-Start, etc.), and constraints — are exported from BigPicture's MS Project MPP/XML export. We re-create these as monday.com timeline columns and dependency links between items. Complex dependency chains with multiple dependency types require manual validation in monday.com post-migration because monday.com's dependency column supports only Finish-to-Start by default.

BigPicture resource allocations (capacity, utilisation, assignment load per team member) map to monday.com workload columns on Business plan. On Standard plan and above, we create a separate capacity board with person-based columns tracking estimated hours per item against available capacity. BigPicture's capacity overrides and allocation percentages become number columns on the capacity board.

BigPicture risk module records — probability, impact, status, owner, mitigation plan — migrate as monday.com items with custom status columns representing risk state (Open, Mitigating, Closed) and label columns for probability (Low, Medium, High) and impact (Low, Medium, High). We map BigPicture's risk ID to a text column for cross-reference.

BigPicture scope trees represent hierarchical work breakdown structures. We flatten them into monday.com groups (top-level WBS nodes) with items representing lower-level work packages and subitems for granular tasks. Parent-child relationships are preserved via the monday.com subitem model and a parent reference text column.

BigPicture team structures (members, team leads, assigned work) map to monday.com teams. We resolve each BigPicture team member by email against the monday.com workspace users and assign the team membership. Team-level permissions in BigPicture map to monday.com board permission levels (full, limited, view-only) per team.

BigPicture creates Jira custom fields for risk probability, impact scores, timeline percentages, and resource percentages. We map these to monday.com number columns with appropriate formatting (percentage display, currency, date). Date-range custom fields map to monday.com date columns with date range enabled. We validate field type compatibility during board schema design and flag any unsupported field types for customer admin review.

Jira issue attachments migrate as monday.com file attachments on the corresponding item. We extract attachments from Jira's file API and upload them to monday.com via the GraphQL file upload endpoint. Attachment file size limits in monday.com (up to 250MB per file on Business plan) apply; files exceeding this threshold are flagged for alternative storage (SharePoint, Google Drive) with links documented.

Jira issue comments migrate as monday.com updates on the corresponding item. Author, timestamp, and comment body are preserved. Rich-text comments are converted to monday.com's update format. Jira internal comments (visible to agents only) are noted in a separate column and flagged for customer admin to decide on visibility in monday.com.

Jira work logged entries migrate to monday.com time tracking on the corresponding item. Worklog author, duration, and date are preserved. Jira's time tracking format (e.g., 3h 30m) is converted to decimal hours for monday.com's time tracking column. If the customer uses BigPicture's enhanced time tracking, those entries also map to the same column.

Jira workflow states map to monday.com status column values. We extract the Jira workflow XML, identify all active status values, and create monday.com status options that mirror the workflow state labels. Jira workflow transitions have no monday.com equivalent; we deliver a written map of each Jira workflow state and its recommended status column mapping for the customer's admin to implement in monday.com's workflow builder.