Answers.Body: <p>There is a good plugin called FeedMe that can help with imports. We used it migrating a pretty large EE site without issue. If you can spit out a XML, RSS, ATOM or JSON feed, it should be able to import it.</p>
  
  <p><a href="https://github.com/engram-design/FeedMe" rel="nofollow noreferrer">FeedMe Plugin</a></p>
  
  <p>I am not sure if it is Craft 3 ready yet, though.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-01T22:02:48.783Z
Answers.Text: Thanks for the feedback. FeedMe is indeed an awesome plug, but I just touched base with the creator on Twitter and it seems that it's not working with V3. Bummer. I'm open to any other suggestions...
Answers.UserDisplayName: RyanDW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-26T23:35:41.947Z
Answers.LastActivityDate: 2017-04-26T23:35:41.947Z
Answers.UserDisplayName: AbbeyDesign
Body: <p>I currently have a website that's been built using a static site generator (SSG; in this case, <a href="https://gohugo.io" rel="nofollow noreferrer">Hugo</a>). The site has about 10 sections, each with 40-50 markdown files. As is the case with most content built out using an SSG, the content files are all well structured and include embedded metadata (via YAML front matter) at the top of each content <code>.md</code> file. </p>
  
  <p>The front matter is very well structured and includes the following fields across all article files:</p>
  
  <ol>
  <li><code>title:</code></li>
  <li><code>subtitle:</code>  </li>
  <li><code>description:</code></li>
  <li><code>tags:</code></li>
  <li><code>categories:</code></li>
  </ol>
  
  <p>There is also a staff/person content type with the usual fields:</p>
  
  <ol>
  <li><code>name_first:</code></li>
  <li><code>name_last:</code></li>
  <li><code>job_title:</code></li>
  <li><code>reports_to:</code>
  Etc...</li>
  </ol>
  
  <p>With Hugo (or just some clever BASH scripting), I can easily template these into a CSV (or multiple CSVs), JSON, etc. I know there are obvious differences between flat files/serialized data and an RDBMS, but I'm wondering if there is a clever way for me to make all of this content easily importable for Craft CMS 3, which our company is hoping to use for a major replatforming in about 3-4 months.</p>
  
  <p>The entire site actually has close to 650 pages, but I figure I can start structuring them in markdown with YAML first to avoid a prolonged copy-and-paste nightmare. (Our current "CMS" is <em>not</em> a CMS by any means and doesn't contains any metadata.) I can parse the content out as very clean HTML, plain text, etc.</p>
  
  <p>Any thoughts, first steps, suggestions, etc would be <em>extremely</em> appreciated. Thanks!</p>
  
Tags: <database><migration><import><conversion>
Title: Going from a static site generator (Jekyll or Hugo) to Craft CMS; Export/migrations options?
ThreadText: # Going from a static site generator (Jekyll or Hugo) to Craft CMS; Export/migrations options?
  
  (Asked by: username_0 on 2017-04-26)
  
  I currently have a website that's been built using a static site generator (SSG; in this case, [Hugo](https://gohugo.io)). The site has about 10 sections, each with 40-50 markdown files. As is the case with most content built out using an SSG, the content files are all well structured and include embedded metadata (via YAML front matter) at the top of each content `.md` file.
  
  The front matter is very well structured and includes the following fields across all article files:
  
  1. `title:`
  2. `subtitle:`
  3. `description:`
  4. `tags:`
  5. `categories:`
  
  There is also a staff/person content type with the usual fields:
  
  1. `name_first:`
  2. `name_last:`
  3. `job_title:`
  4. `reports_to:`
     Etc...
  
  With Hugo (or just some clever BASH scripting), I can easily template these into a CSV (or multiple CSVs), JSON, etc. I know there are obvious differences between flat files/serialized data and an RDBMS, but I'm wondering if there is a clever way for me to make all of this content easily importable for Craft CMS 3, which our company is hoping to use for a major replatforming in about 3-4 months.
  
  The entire site actually has close to 650 pages, but I figure I can start structuring them in markdown with YAML first to avoid a prolonged copy-and-paste nightmare. (Our current "CMS" is *not* a CMS by any means and doesn't contains any metadata.) I can parse the content out as very clean HTML, plain text, etc.
  
  Any thoughts, first steps, suggestions, etc would be *extremely* appreciated. Thanks!
  
  **Tags:** database, migration, import, conversion
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-04-26. Score: 3
  
  There is a good plugin called FeedMe that can help with imports. We used it migrating a pretty large EE site without issue. If you can spit out a XML, RSS, ATOM or JSON feed, it should be able to import it.
  
  [FeedMe Plugin](https://github.com/engram-design/FeedMe)
  
  I am not sure if it is Craft 3 ready yet, though.
  
  > **Comments:**
  > **username_0**: Thanks for the feedback. FeedMe is indeed an awesome plug, but I just touched base with the creator on Twitter and it seems that it's not working with V3. Bummer. I'm open to any other suggestions...  
  
  ---
  
  