Rustyll makes it easy to migrate from other static site generators. Use the rustyll migrate command to automate the conversion process.

Available Migrators

Rustyll can migrate from these static site generators:

• Jekyll - Ruby-based static site generator
• Hugo - Go-based static site generator
• Zola - Rust-based static site generator
• Eleventy - JavaScript-based static site generator
• Gatsby - React-based static site framework
• Docsy - Hugo documentation theme
• mdBook - Rust-based documentation tool
• MkDocs - Python-based documentation generator
• GitBook - JavaScript-based documentation platform
• Slate - API documentation generator
• Pelican - Python-based static site generator
• Nanoc - Ruby-based static site generator
• Middleman - Ruby-based static site generator
• Assemble - Node.js static site generator
• Bridgetown - Ruby-based static site generator
• Cobalt - Rust-based static site generator
• Fresh - Deno-based web framework
• Harp - Node.js static site generator
• Jigsaw - PHP-based static site generator
• Metalsmith - Node.js static site generator
• Nikola - Python-based static site generator
• Octopress - Jekyll-based blogging framework

Using the Migration Command

The basic syntax for migrating is:

rustyll migrate --from <generator> --source /path/to/source --destination /path/to/destination

For example, to migrate from Jekyll:

rustyll migrate --from jekyll --source ./my-jekyll-site --destination ./my-rustyll-site

Run rustyll migrate --help for all available options.

Common Migration Process

While each generator has its own specific migration steps (detailed in the individual guides), the general process is:

1. Install Rustyll: cargo install rustyll
2. Back up your existing site
3. Run the migration command
4. Review the migration report
5. Test the migrated site
6. Fix any issues (consult the specific migration guide)
7. Deploy your new Rustyll site

Migration Success Rate

Migration success depends on how closely your source site follows standard patterns. Sites with:

• Standard directory structures
• Common templating patterns
• Typical content formats

…will migrate more smoothly than highly customized sites with custom plugins or non-standard configurations.