Can I import client Excel files without editing them first?
You can start from the workbook you receive, then choose sheet, header row, mapping and cleanup options before import.
Import a client backlog handover into Jira
Client backlog handovers rarely arrive as perfect CSV files. Excel to Jira Importer helps teams turn real Excel handovers into reviewed Jira issues with mapping, cleanup, hierarchy support and validation before import.
The problem
Client spreadsheets often include business requirements, notes and assumptions, estimates, priorities, due dates, acceptance criteria, hierarchy or grouping, status or ownership columns.
Before Jira import, the team needs to decide what becomes a summary, what becomes a description, what maps to fields and what should be cleaned up.
The solution
Use a repeatable handover workflow:
- Upload the client workbook
- Choose the relevant sheet
- Map columns to Jira fields
- Build issue descriptions from client notes
- Clean values like dates, priorities or labels
- Validate rows
- Import selected items
Example workflow
Client column: Requirement / Business value / Notes / Priority / Epic
Jira result: Summary, description, priority, parent or epic and other mapped fields, based on your Jira configuration.
Turn client Excel handovers into Jira issues
Use mapping, cleanup and validation before selected rows become Jira issues.
Early launch offer: help with your first Excel-to-Jira import
Trying a new Jira import app is easier when the first real file works. During the early launch period, we help trial users prepare their first Excel-to-Jira import by email. Send a sanitized workbook, column list or screenshots, and we will help you choose the right worksheet, header row, field mapping, cleanup rules and validation approach before you import.
- choosing the right import structure
- mapping Excel columns to Jira fields
- preparing Description Builder setup
- cleaning messy values before validation
- checking hierarchy and parent-child setup
- understanding validation errors before import
No video call is required. You stay in control of the import, and nothing changes in Jira until you review and confirm it in the app. Please avoid sending confidential customer data unless your organization allows it. A small anonymized sample is usually enough.
Get help with your first import
Email: support.jira@mederak.app
Related resources
- Create Jira issues from Excel rows
- Import Jira hierarchy from Excel
- Admin approval notes
- Security notes
FAQ
Can I combine multiple columns into the Jira description?
Yes. Description Builder can combine client notes, acceptance criteria and business context into one Jira Description.
Can I preserve backlog hierarchy?
Yes, when the workbook contains usable hierarchy data and the Jira project supports the resulting relationships.
Can I skip rows that are not ready?
Yes. Import selected rows only after validation.
Can I save a mapping for the next client handover?
Yes. Saved setup can help with similar files that return later.