Preserve useful project structure
Supported ISS sections become InstallerLab FSS so existing work can be the starting point.
Import an Inno Setup .iss script and continue in InstallerLab FSS.
Already have an Inno Setup project? InstallerLab v3 keeps the ISS → FSS importer for supported sections, letting existing installer work become a lightweight editable project instead of forcing a manual rewrite.
.iss inputISS → FSSEditable outputFSS AnalyzerSetup EXEMSIBundle
Why import instead of starting again?
Move into a visual workflow
After import, the FSS can be edited through project panels or directly as text.
Keep a lightweight project file
FSS remains the durable project definition rather than generated build-state.
Analyze before building
Run FSS Analyzer after migration to surface errors, warnings and compatibility findings.
Target compatible package formats
The migrated FSS can participate in Setup EXE, MSI, Bundle and other supported workflows.
Migration stays inspectable
The result is plain text that can be reviewed, versioned and corrected before release.
ISS and FSS are not the same format
The importer translates only the sections and rules InstallerLab supports. Review and test the generated FSS before relying on it for release packaging.
| Before | Importer | After |
|---|---|---|
| Inno Setup .iss | Convert supported sections | InstallerLab .fss |
| Script-first authoring | Migration step | Visual editor + editable FSS |
| Existing rules | Translate supported content | Review, analyze and build |
A practical migration workflow
1. Import
Select the existing ISS script and convert supported content into FSS.
2. Review
Inspect paths, files, registry, shortcuts and other migrated rules.
3. Analyze
Use FSS Analyzer before packaging.
4. Build and test
Generate a compatible target and validate install/uninstall on a clean Windows environment.
ISS → FSS importer FAQ
Does InstallerLab import every Inno Setup feature?
No. Unsupported or tool-specific behavior may need manual adaptation.
Does the imported project stay editable?
Yes. The output is an InstallerLab FSS text project.
Can I create a Bundle after importing?
Yes when the resulting FSS contains configuration supported by that build target.
Where can I compare InstallerLab with Inno Setup and other products?
Use the new dedicated comparison page.
Bring the old project forward instead of throwing it away.
Use the importer as a migration starting point, keep the project in FSS, then build with InstallerLab v3.