Migration guide · JasperReports source
What happens when you import a JRXML report?
Open Reports reads JasperReports XML source and creates an editable JSON draft. Import gives you a starting point for migration; it does not guarantee the same output or behavior.
Open Reports does not execute or load compiled `.jasper` files. Its native editable report definition is JSON. Import a `.jrxml` file or folder, then save or export the resulting JSON definitions.
Read each import status
- Converted: a source feature was mapped to an Open Reports component or behavior.
- Needs review: an approximation or semantic difference may need a manual correction.
- Unsupported: the source feature does not currently have an equivalent conversion.
Use the import report to locate each item. Rebind datasets and parameters in the host environment; database connection credentials and query execution are not copied as trusted live connections.
Common review areas
Expression languages, variable evaluation and reset rules, complex subreports, data-source behavior, fonts, linked images, pagination, and renderer-specific details can affect parity. The importer may convert some common forms, but every report's diagnostics and output are the evidence for that report.
Migration checklist
- Choose a representative JRXML and collect its referenced assets and a safe sample data set.
- Import the JRXML and any related report files; inspect every diagnostic.
- Rebind parameters, datasets, image paths, fonts, and any child reports.
- Render the same input in JasperReports and Open Reports.
- Compare page size, orientation, margins, repeated bands, page breaks, text, totals, fonts, images, and printer output as applicable.
- Keep the existing Jasper workflow until the report meets your own acceptance criteria.
The project documents both successful synthetic comparisons and remaining gaps. A result for one sample is not proof of parity for another JRXML file. See the migration evidence and limitations.