Migrate your BigPicture data
Portfolio and project management layer for Jira, delivering Gantt charts, roadmaps, resource management, and risk tracking that Jira does not provide natively.
In its favor
Why people choose BigPicture
The signal that keeps BigPicture on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Jira-native teams gain portfolio-level visibility without abandoning their existing issue tracker, keeping sprints, backlogs, and reporting in one place.
Gantt chart and roadmap capabilities bring timeline-based planning to Jira, replacing the need for standalone tools like Microsoft Project.
Supports agile, classic, and hybrid methodologies simultaneously, accommodating teams with mixed project governance styles.
Enterprise-grade resource management and workload visualisation appeal to PMOs managing cross-functional teams at scale.
Part of the Appfire ecosystem — integrates with other Atlassian Marketplace apps that mid-to-large enterprises already run.
Pricing is opaque and scales per-user with no free or read-only tier, making it costly for organisations with large passive audiences in Jira.
Permissions and role configuration become disproportionately complex as team size grows, with no distinction between active collaborators and read-only viewers at the license level.
Export capabilities cap out at 2,000 tasks per operation, blocking teams that need to export full-programme data in a single pass.
Performance degrades noticeably on large instances, with known latency and timeout issues in certain versions.
Some teams find they outgrow the Jira-centric model and move to standalone PPM platforms with broader reporting and cross-system integration.
Reasons to switch
Why people leave BigPicture
The recurring reasons buyers give for replacing BigPicture. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where BigPicture fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
BigPicture pricing overview
BigPicture uses a per-user pricing model at approximately $7.53/user/month for standard tiers, with custom pricing for Enterprise. No free tier or read-only user discount exists. Cloud and Data Center are separate licensing tracks with different billing structures.
Standard
Tier 1 of 3
~$7.53/user/month (confirmed via Capterra; most pricing available upon request)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on BigPicture's schedule — see our quote-based pricing →
What gets migrated
BigPicture object support
Object-by-object support for BigPicture migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are standard Jira project structures. BigPicture uses them as containers for Boxes and Gantt modules. We migrate them 1:1 as Jira projects with all issue-linkage intact.
Issues (Tasks)
Fully supportedIssues are Jira's atomic work units and carry all BigPicture task data. We migrate them with full field fidelity including custom fields, status, assignee, and fix versions.
Custom Fields
Mapping requiredBigPicture creates its own custom fields for resource and timeline data. We map these to destination equivalents but must validate field types match, especially for date-range and percentage fields.
Boxes
Mapping requiredBoxes are BigPicture's primary portfolio-level containers that hold Jira projects or selected issues. We migrate Box structure and the linked issue sets, though destination PM tools may not have a native Box equivalent.
Gantt Charts
Mapping requiredGantt configurations — including timeline bars, dependencies, and constraints — are stored as BigPicture module data on top of Jira issues. We export to MS Project MPP/XML format for maximum fidelity at migration time.
Roadmaps
Mapping requiredRoadmap views are constructed from Box/project timeline data. We preserve the view structure and issue-to-timeline mapping; the destination roadmap representation may differ.
Resources and Workloads
Mapping requiredResource allocation data — capacity, utilisation, assignment loads — lives in BigPicture modules. We map these to destination resource management fields, which vary significantly by platform.
Risks
Mapping requiredRisks are tracked in a dedicated BigPicture module with custom fields (probability, impact, status). We extract them as structured records and map to destination risk or issue types.
Scope (Work Breakdown Structure)
Mapping requiredScope trees are BigPicture-specific hierarchical structures. We flatten them into Jira issue hierarchies or destination task trees, preserving parent-child relationships.
Teams
Mapping requiredBigPicture teams group members and assign them to work. We map team memberships and assignments to destination user groups or team modules.
Attachments
Fully supportedAttachments on Jira issues are standard Jira attachments. We migrate them through the standard Jira file export path.
Time Entries
Fully supportedLogged work on Jira issues carries through standard Jira export. BigPicture does not store its own time data.
Comments
Fully supportedComments are Jira issue comments. We migrate them with author and timestamp intact.
Labels and Tags
Fully supportedJira labels are standard and map cleanly to destination label/tag fields across PM tools.
Workflows
Mapping requiredJira workflows are Jira-native. BigPicture does not modify workflow logic but may reference workflow states in its timeline views. We migrate workflows as Jira XML and remap state references in the destination.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are standard Jira project structures. BigPicture uses them as containers for Boxes and Gantt modules. We migrate them 1:1 as Jira projects with all issue-linkage intact. |
| Issues (Tasks) | Fully supported | Issues are Jira's atomic work units and carry all BigPicture task data. We migrate them with full field fidelity including custom fields, status, assignee, and fix versions. |
| Custom Fields | Mapping required | BigPicture creates its own custom fields for resource and timeline data. We map these to destination equivalents but must validate field types match, especially for date-range and percentage fields. |
| Boxes | Mapping required | Boxes are BigPicture's primary portfolio-level containers that hold Jira projects or selected issues. We migrate Box structure and the linked issue sets, though destination PM tools may not have a native Box equivalent. |
| Gantt Charts | Mapping required | Gantt configurations — including timeline bars, dependencies, and constraints — are stored as BigPicture module data on top of Jira issues. We export to MS Project MPP/XML format for maximum fidelity at migration time. |
| Roadmaps | Mapping required | Roadmap views are constructed from Box/project timeline data. We preserve the view structure and issue-to-timeline mapping; the destination roadmap representation may differ. |
| Resources and Workloads | Mapping required | Resource allocation data — capacity, utilisation, assignment loads — lives in BigPicture modules. We map these to destination resource management fields, which vary significantly by platform. |
| Risks | Mapping required | Risks are tracked in a dedicated BigPicture module with custom fields (probability, impact, status). We extract them as structured records and map to destination risk or issue types. |
| Scope (Work Breakdown Structure) | Mapping required | Scope trees are BigPicture-specific hierarchical structures. We flatten them into Jira issue hierarchies or destination task trees, preserving parent-child relationships. |
| Teams | Mapping required | BigPicture teams group members and assign them to work. We map team memberships and assignments to destination user groups or team modules. |
| Attachments | Fully supported | Attachments on Jira issues are standard Jira attachments. We migrate them through the standard Jira file export path. |
| Time Entries | Fully supported | Logged work on Jira issues carries through standard Jira export. BigPicture does not store its own time data. |
| Comments | Fully supported | Comments are Jira issue comments. We migrate them with author and timestamp intact. |
| Labels and Tags | Fully supported | Jira labels are standard and map cleanly to destination label/tag fields across PM tools. |
| Workflows | Mapping required | Jira workflows are Jira-native. BigPicture does not modify workflow logic but may reference workflow states in its timeline views. We migrate workflows as Jira XML and remap state references in the destination. |
Gotchas
What to watch for in BigPicture migrations
Issues we've hit on past BigPicture migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Export hard-capped at 2,000 tasks
Jira Index corruption bug in versions 8.21.0–8.25.0
No read-only licensing — every Jira user counts
BigPicture and bigpicture.io are different products
Permissions complexity increases non-linearly with team size
| Severity | Issue |
|---|---|
| High | Export hard-capped at 2,000 tasks |
| High | Jira Index corruption bug in versions 8.21.0–8.25.0 |
| Medium | No read-only licensing — every Jira user counts |
| Medium | BigPicture and bigpicture.io are different products |
| Medium | Permissions complexity increases non-linearly with team size |
Leaving BigPicture?
Where BigPicture customers move next
5 destinations BigPicture can migrate to.
How a BigPicture migration works
Four steps, BigPicture-specific
Connect
Jira REST API uses Atlassian OAuth 2.0 (3LO) or basic auth with API tokens. BigPicture does not have its own standalone API. into BigPicture. Scopes limited to read-only on the data we move.
Map
We translate BigPicture-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate BigPicture quirks before production.
Migrate
Full migration with BigPicture rate-limit handling. Rollback available throughout.
FAQ
BigPicture migration FAQ
Answers to the questions buyers ask most during BigPicture migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your BigPicture migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate BigPicture.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your BigPicture setup and destination — written quote back within a business day.