Skip to content
Foundation Docs

Import from BigPicture

BigPicture users can migrate their existing boxes, scopes, and custom hierarchies into Foundation in a single guided flow. Use this when leaving BigPicture for Foundation without losing the structural work your team has already done.

You’ll need a BigPicture API token for a user who can read the boxes you want to migrate.

Start the wizard

Section titled “Start the wizard”
  1. Open Foundation Home and click Import in the header.
  2. Choose Import from BigPicture.
  3. Follow the five-step wizard.

The five steps

Section titled “The five steps”
  1. Connect — select your cloud region and paste a BigPicture API token. Foundation validates it before moving on.
  2. Select boxes — Foundation lists your boxes with item counts. Tick the ones you want to bring over. One box becomes one Foundation lens by default.
  3. Configure — for each box, decide what to import:
    • Scope and tasks (required).
    • Custom hierarchy — BigPicture’s parent-child relationships map to Foundation tree rows.
    • Saved views — column configurations.
    • Permissions where possible.
  4. Progress — the import runs as an async job with per-box progress.
  5. Complete — review the summary with links to each new lens.

What converts cleanly

Section titled “What converts cleanly”
  • Scope items — Jira issues stay linked by their key.
  • Custom items — BigPicture’s non-Jira items become Foundation Flex Items that you can later promote to real Jira issues with Copy to Jira.
  • Gantt-friendly fields — start date, due date, and dependencies transfer when present.
  • Box-level templates — standard agile box templates map to Foundation’s Agile Hierarchy preset shape.

What doesn’t transfer

Section titled “What doesn’t transfer”
  • BigPicture Risks and Resources modules (out of scope for Foundation MVP).
  • Box-specific permission schemes that don’t match Atlassian users or groups.
  • Baselines beyond the current snapshot (Foundation preserves the active baseline only).

Anything skipped is called out in the final summary.

After the import

Section titled “After the import”
  • Open each new lens and check dates, dependencies, and assignees against the source.
  • Re-run or adjust the generated Sync Agents to match how the team plans to refresh the lens.
  • Set up sharing so the original box members keep their access.
Section titled “Related”