Answers.Body: <p>You're looking for the answer to a complicated problem. :)</p>
  
  <p>What you're thinking of I would describe as "content migrations" or "content model syncing".</p>
  
  <p>There is currently nothing in Craft out-of-the-box that will do what you're looking for, although we've got some ideas on how we'd like to approach the sharing/syncing of content between environments/installations in the long term.</p>
  
  <p>If you need something before then, you'll have to write a plugin that rolls its own solution.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-04T15:56:24.850Z
Answers.Text: @BradBell are there any recommended plugins that do this now (2017)?
Answers.UserDisplayName: ricricucit
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-21T14:21:05.163Z
Answers.Text: I really think addressing this in the core of Craft would truly separate it head and shoulders from other CMSs. My hope is that this is addressed sooner than later and is a high priority for the Pixel and Tonic team. Just my two cents.
Answers.UserDisplayName: Wes Rice
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-21T15:07:11.890Z
Answers.Text: @Brad We are not worried about the user content per se. I assume you are calling it a 'contents migration' because of the nature of craft, and how all fields, elements, etc are both structural (i.e. change the schema) as well as content (i.e. add records to `craft_elements`, `craft_fields`, etc.)?
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-21T18:06:33.777Z
Answers.Text: @DouglasMcDonald Exactly.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-21T03:18:27.350Z
Answers.LastActivityDate: 2014-10-21T03:18:27.350Z
Answers.UserDisplayName: Brad Bell
Body: <p>Let's say we add a section or other elements (field, category, tags, assets, etc) in the CP on our dev servers and want to roll that change out to a stage or production environment, is there a way to capture the changes we've made through the CP as a migration, or is there some other recommended way to reverse engineer that into a migration?</p>
  
  <p>I have checked out the documentation on creating <a href="http://buildwithcraft.com/docs/plugins/migrations" rel="nofollow noreferrer">plugin migrations</a> and a couple of questions <a href="https://craftcms.stackexchange.com/questions/1079/migrating-a-whole-website-between-craft-instances">here</a> and <a href="https://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev">here</a>, but nothing addressing creating a migration for the craft DB itself.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-21T17:51:44.310Z
Comments.Text: Already answered here:
  http://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev/14148#14148
Comments.UserDisplayName: jlcharette
Tags: <database><migration>
Title: How to create a migration for the main Craft DB?
ThreadText: # How to create a migration for the main Craft DB?
  
  (Asked by: username_0 on 2014-10-21)
  
  Let's say we add a section or other elements (field, category, tags, assets, etc) in the CP on our dev servers and want to roll that change out to a stage or production environment, is there a way to capture the changes we've made through the CP as a migration, or is there some other recommended way to reverse engineer that into a migration?
  
  I have checked out the documentation on creating [plugin migrations](http://buildwithcraft.com/docs/plugins/migrations) and a couple of questions [here](https://craftcms.stackexchange.com/questions/1079/migrating-a-whole-website-between-craft-instances) and [here](https://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev), but nothing addressing creating a migration for the craft DB itself.
  
  **Tags:** database, migration
  
  > **Comments:**
  > **username_1**: Already answered here: http://craftcms.stackexchange.com/questions/10/whats-the-best-practice-for-handling-data-migration-and-organization-across-dev/14148#14148  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2014-10-21. Score: 3
  
  You're looking for the answer to a complicated problem. :)
  
  What you're thinking of I would describe as "content migrations" or "content model syncing".
  
  There is currently nothing in Craft out-of-the-box that will do what you're looking for, although we've got some ideas on how we'd like to approach the sharing/syncing of content between environments/installations in the long term.
  
  If you need something before then, you'll have to write a plugin that rolls its own solution.
  
  > **Comments:**
  > **username_4**: I really think addressing this in the core of Craft would truly separate it head and shoulders from other CMSs. My hope is that this is addressed sooner than later and is a high priority for the Pixel and Tonic team. Just my two cents.  
  > **username_0**: @username_2 We are not worried about the user content per se. I assume you are calling it a 'contents migration' because of the nature of craft, and how all fields, elements, etc are both structural (i.e. change the schema) as well as content (i.e. add records to `craft_elements`, `craft_fields`, etc.)?  
  > **username_2**: @username_0 Exactly.  
  > **username_3**: @username_2 are there any recommended plugins that do this now (2017)?  
  
  ---
  
  