Switching from Xporter
Exportelier offers guided migration, not Xporter compatibility. It recognizes a limited set of common Xporter-style placeholder shapes in order to explain or suggest safe rewrites, but it never executes Xporter functions, filters, JQL or scripts.
Choose the target mode
| Migration goal | Recommended mode |
|---|---|
Keep an existing branded .docx, including native headers, footers, page numbers, styles and section setup | Word Template Mode |
| Maintain one layout that exports to PDF, Markdown and DOCX | Visual designer |
| Preserve scripting or arbitrary expressions | No direct target — redesign with safe bindings and fixed constructs |
Construct map
| Xporter-style intent | Exportelier equivalent |
|---|---|
Scalar placeholders such as ${Key} or ${Summary} | Canonical paths such as ${issue.key} and ${issue.summary} |
| Repeated issue collections | ${#each collection as item}…${/each} in Word mode, or a purpose-built designer component |
| Presence checks | ${#if path}…${#else}…${/if} in Word mode |
| Date, number, user or duration formatting | The fixed, named Word formatters |
| JQL inside a template | Select issues through the export context instead |
| Function calls, JavaScript, Groovy, Velocity or FreeMarker | No execution — rewrite with safe tokens or precomputed Jira fields |
| PDF-only layout or signing behaviour | Designer PDF projection and PDF export settings |
The exact scanner classifications, recognized aliases and unsupported constructs are documented in Xporter syntax: what works. The canonical grammar and bindings live in Word Template Mode and the token reference.
Check a template before rebuilding
Upload the .docx in the template editor's Word tab. Every upload runs the migration scanner and produces a compatibility report that groups each finding into one of four classes:
supported-as-isauto-convertibleunsupported-but-explainableunsafe-not-supported
Auto-convertible findings come with a copyable replacement token. The scanner is advisory: a clean report does not replace package security validation, binding validation, or a real export test with representative data.