Turn messy project spreadsheets into Jira & ADO-ready backlogs.
BacklogForge helps teams convert rough stakeholder sheets into structured epics, stories, tasks, acceptance criteria, and import-ready files — without requiring a Jira plugin, OAuth setup, or data upload in Core Mode.
The painful middle step is the product.
Stakeholders send rough spreadsheets. Delivery tools need clean work items. BacklogForge focuses on the tedious transformation between the two.
Messy intake
Project names, notes, owners, priorities, dates, and half-formed requirements arrive in spreadsheet form.
Structured backlog
BacklogForge reshapes the input into epics, stories, tasks, and acceptance criteria drafts.
Validated export
Review warnings, map fields, then download Jira or Azure DevOps-ready CSV/XLSX output.
From spreadsheet to backlog in five steps.
A simple workflow designed to avoid enterprise setup friction.
Upload or paste
Start with CSV, XLSX, or pasted table data.
Map fields
Connect source columns to Jira or ADO fields.
Choose structure
Epic → Story, story-only, task list, or bug list.
Preview & validate
Catch missing required fields and risky formatting.
Export
Download import-ready output for review and upload.
AI-first, but privacy-clear.
Use local-only Core Mode for sensitive data. Turn on Assist Mode only when richer AI generation is worth external processing through your own approved provider.
Zero-egress backlog conversion
Runs in the browser. Your raw spreadsheet data does not need to leave your machine.
- ✓Field mapping and validation
- ✓Jira/ADO output templates
- ✓Template-based acceptance criteria shells
- ✓No plugin, OAuth, or account required for local use
Bring your own LLM
Optional AI generation using a provider account and API key controlled by the user.
- !Selected data is sent to your chosen AI provider
- ✓Richer epics, stories, subtasks, and acceptance criteria
- ✓Session-only key handling planned for first release
- ✓Core Mode remains available when egress is not allowed
Founder pricing we are testing.
Early pricing is intentionally simple. Founder access helps validate demand before this becomes a heavier product.
Founder
- ✓Core Mode access
- ✓Jira starter export
- ✓Founder feedback channel
Pro
- ✓Jira + Azure DevOps templates
- ✓Saved local mappings
- ✓Optional BYO-LLM Assist
Consultant
- ✓Use across client projects
- ✓Reusable config templates
- ✓Priority template requests
Built to catch the ugly stuff before import.
BacklogForge should not just generate a pretty file. It should warn users about the issues that make imports fail or create low-quality tickets.
Common questions
Is BacklogForge a Jira or Azure DevOps plugin?
No. The first version is designed as a lightweight pre-import tool. That means no marketplace install, no OAuth, and no direct access to your Jira or ADO instance.
Does my data leave my machine?
In Core Mode, the goal is browser-local processing so raw spreadsheet data does not need to leave your machine. Assist Mode is different: if enabled, selected data is sent to the AI provider you choose and control.
Will it automatically create perfect tickets?
No. BacklogForge creates structured drafts and import files for review. Human judgment still matters, especially for business rules, technical design, and final acceptance criteria.
Who is this for?
Business analysts, product owners, TPMs, agile consultants, Jira/ADO consultants, small dev agencies, and engineering managers who regularly turn messy planning input into delivery-system work items.
Request Founder Access
We are validating BacklogForge with early users who regularly convert planning spreadsheets into Jira or Azure DevOps work items. Join the founder list to see the demo and help shape the first release.