prosembler / nitro-porter
The only multi-platform community migration tool. Free your community!
Requires
- php: >=8.3
- ext-gd: *
- ext-json: *
- ext-pdo: *
- ext-zlib: *
- adhocore/cli: ^1
- illuminate/database: ^11
- monolog/monolog: ^3
- nadar/quill-delta-parser: ^3
- s9e/text-formatter: 2.15.*
- staudenmeir/laravel-cte: ^1
Requires (Dev)
This package is auto-updated.
Last update: 2026-08-05 15:54:03 UTC
README
Nitro Porter is the only multi-platform community migration tool. Its goal is fast no-code migrations for any community with accessible data.
Every community deserves the agency to choose the best software for its mission while preserving its history. All proprietary software has a finite lifespan and lock-in stifles competition, which leads to stagnation. When we own our data and can freely choose betweeen platforms, everyone wins.
Get Started
Working through a migration often takes weeks, not hours! Set reasonable expectations and be patient.
- User Guide â requirements & install steps.
- Migration Guide â plan a community migration.
- Sources & Targets â support details.
We greatly appreciate feedback! However, we check in periodically as our schedule allows, not daily.
What Can It Do?
Migrate a community from a supported Source to a supported Target as comprehensively as possible.
Supported Targets (where you're going) â 4 total ðĨ
Supported Sources (what you're using now) â 37 total ðĪ
...and MORE!
Don't see your software? Start a discussion to request it and check our informal roadmap.
What gets migrated, exactly? ðĨ
All sources & targets support migrating:
- users & roles
- discussions (or threads) & posts (or comments)
- categories (or subforums, channels, etc.)
Beyond that, each package as different support based on feature availability, extension choice, and maturity of the package. These include things like badges, reactions, bookmarks, & polls. Both source and target must support a data type for it to transfer. Read more about how data is transferred.
Project Info
How does it work? ðĪ
Data is first converted to an intermediary "porter schema," reducing the number of data paths from #sources x #targets to #sources + #targets.
The result is repeatable results in a single multi-tool rather than myriad low-quality, single-purpose tools.
Why not use 1-off migration tools? ðŠī
Data migrations typically require either time & skill (you are a programmer) or capital (you are a for-profit company). Nitro Porter aims to become increasingly accessible to everyone else by making both migrations & extensibility simple. Software tools should not be assumed disposible just because they don't have a 30% profit margin to exploit.
Can't AI do this? ðŋ
No.
Will you do it for me? ð
We encourage you to work through using the tool and ask us questions. Feedback on how the tool works for you (or doesn't) is very valuable! However, if you prefer to outsource, contact migrations@prosembler.com for a cost estimate.
How can I learn more or help? ðïļ
- Contribute â data, requests, & fixes.
- Changelog â latest fixes & updates.
- Roadmap â informal goals.
Where did this come from? ð
Vanilla Porter was created in 2010 at Vanilla Forums as a single-script multi-source export tool, abandoned by 2020. Nitro Porter 3.0 was a rewrite1 that preserved compatibility with existing sources while reimagining the framework. In 2026, the Open Social Fund, a fund established by NLnet, sponspored major development work in the 5.0 release. More history on our website.
Footnotes
-
ð Forked 27 Sep 2021 in memory of Kyle âĐ






















