Import instead of retyping
The ISS → FSS importer converts supported sections into InstallerLab's project format, giving you a practical migration starting point.
Move from an Inno Setup script to a visual Windows packaging workflow without throwing the old project away.
InstallerLab v3 is not an Inno Setup clone. It uses its own editable FSS format and can import supported ISS sections, analyze the resulting project, then target the compatible InstallerLab backends.
ISS → FSSSetup EXEMSIBundle / BurnPortableOffice Add-insQGIS PluginsFSS Analyzer
What InstallerLab v3 offers Inno Setup users
Keep the result editable
FSS is plain text. Inspect, version and modify the migrated project directly or through the visual editor.
Analyze before packaging
FSS Analyzer surfaces errors, warnings and compatibility findings before the first migrated build.
Generate MSI without a second project
The same compatible FSS can feed InstallerLab's WiX-based MSI backend.
Use Bundle when prerequisites matter
The WiX Burn backend can chain prerequisite EXE/MSI packages before the main MSI and produce one bootstrapper EXE.
Move beyond a generic Application model
v3 also understands specialized Office Add-in and QGIS Plugin project types and automatically restricts build targets to the formats that apply.
A migration path instead of an all-or-nothing rewrite
| Existing workflow | InstallerLab v3 path |
|---|---|
| Existing .iss script | Import supported sections to FSS |
| Review converted rules | Run FSS Analyzer |
| Direct user setup | Build Setup EXE |
| Windows Installer package | Build MSI |
| Prerequisites + application | Build WiX Burn Bundle |
Where InstallerLab fits
InstallerLab optimizes for
- Visual authoring for common deployment tasks.
- A lightweight editable FSS project as source of truth.
- Multiple outputs from one project.
- Migration from supported ISS sections.
- Project-aware Office Add-in and QGIS Plugin workflows.
- CLI, SBOM, signing and pre-build analysis.
InstallerLab does not claim
- That every Inno Setup feature converts automatically.
- That FSS and ISS are the same language.
- That every enterprise packaging scenario is covered.
- That migration eliminates the need for physical installer testing.
Inno Setup migration FAQ
Can InstallerLab import an .iss file?
Yes, for supported sections and rules. The converted FSS should be reviewed before release.
Does InstallerLab replace Inno Setup syntax with FSS?
The imported project becomes InstallerLab FSS, which is InstallerLab's own declarative project format.
Can the imported project create MSI or Bundle?
Yes when the migrated configuration is compatible with those backends.
Where is the detailed competitor matrix?
The comparison now has its own dedicated page instead of an anchor buried inside the documentation.
Keep your existing installer knowledge, but move to a broader deployment pipeline.
Import supported ISS content, review the FSS, analyze it, then choose the deployment target the project actually supports.