Appendix 1
Migrating to Hugo

Now that you know how Hugo works, you’re probably thinking, “OK, how can I move my existing content to Hugo?” In a perfect world, you’d simply put your content in Hugo’s content directory as Markdown files and everything would just work. However, we don’t live in a perfect world, and it often ends up being a little more nuanced than that.

Depending on how your content is organized and what additions or plugins you’ve added to your existing system, the migration could take anywhere from a few hours to a few months to complete.

In this chapter, you’ll review the migration process at a high level, which will help you plan and map out what you need for your own migration plan.