Nitro Porter is the only multi-platform community migration tool.

Every community deserves the best software for its mission while preserving its unique history. Nitro Porter's goal is 1-hour no-code data migrations for any community with accessible data.

Community history is vitally important. Platform lock-in stifles competition in the software ecosystem. When everyone owns their own data and can freely choose their platform, everyone wins.

Data is first converted to an intermediary "porter format," reducing the number of code 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.

Nitro Porter packages allow anyone with basic programming skills to add any community software (commercial or free) as source or target. Nitro Porter uses the GNU AGPL 3.0 license to ensure it remains freely available to all.

• User Guide — requirements & install steps.
• Migration Guide — plan a community migration.
• Sources & Targets — support details.
• Start a Discussion — share how it went!

• Contribute — data, requests, & fixes.
• Changelog — latest fixes & updates.
• Roadmap — informal goals.
• History — how we got here.

...and MORE!

All sources & targets support migrating:

• users & roles
• discussions (or threads)
• posts (or comments)
• categories (or subforums, channels, etc.)

Beyond that, each supports different types of data depending on feature availability, extension choice, and maturity of the source/target package. These include things like badges, reactions, bookmarks, and polls.

Both the source and target must support a data type for it to transfer!

Nitro Porter never transfers permissions. It's not safe to do so automatically due to variations in how platforms implement them. You will always need to reassign permissions after a migration.

Passwords are generally hashed, which means no system can "decrypt" or "convert" them. However, if both the source and target platform support the same hashing algorithm, they should transfer seamlessly. Alternatively, the target system could add support for the source hashing algorithm and convert password hashes as users login next (see Garden/Password). This is beyond the scope of what any migration tool can do in isolation, but we're happy to answer questions about the process should you wish to build that functionality.

Don't see your software? Start a discussion to request it and keep an eye on our informal roadmap. We're happy to add a new Source for any software, provided it is not bespoke. For a new Target, we typically require support from the vendor.

Currently, nearly all data sources and targets are based on MySQL-compatible databases. Other storage formats (e.g. mbox, MSSQL, API) require pre-conversion to a MySQL database. The 3.0 rewrite of Nitro Porter¹ was built with native support for those alternate formats in mind and it will continue to expand.