Answers.Body: <p>I personally think mucking with the schema here is bound to get you in trouble.  Very easy to miss something.</p>
  
  <p>If you don't have much data in yet, simply start again, and chalk it down to learning/experience.  (Personally I think there should be a 'Start This Way' page in the Commerce docs that  emphasises Data Modelling for product types is where you should begin!).</p>
  
  <p>If you do have a lot of data in, best to export &amp; then re-import your data using e.g. FeedMe - <a href="https://sgroup.com.au/plugins/feedme/getting-started/introduction" rel="nofollow noreferrer">https://sgroup.com.au/plugins/feedme/getting-started/introduction</a></p>
  
  <p>(You will need the Pro version which support Products)</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-22T01:01:17.823Z
Answers.Text: We can easily change entry type of entry and nothing says that it is something bad. Changing product type would be the same.
Answers.UserDisplayName: Piotr Pogorzelski
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-18T23:55:25.517Z
Answers.LastActivityDate: 2017-05-18T23:55:25.517Z
Answers.UserDisplayName: Jeremy Daalder
Answers.Body: <p>Assuming this is because you've got a ton of products already setup?</p>
  
  <p>There are <code>productTypeId</code> columns in other tables you'd want to consider as well. <code>craft_commerce_discount_producttypes</code>, <code>craft_commerce_producttypes_i18n</code>, <code>craft_commerce_producttypes_shippingcategories</code>, <code>craft_commerce_producttypes_taxcategories</code>, <code>craft_commerce_sale_producttypes</code> just from a quick scan of the schema.</p>
  
  <p>As always, make sure you backup your database first and test thoroughly afterwards.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-18T22:14:28.083Z
Answers.LastActivityDate: 2017-05-18T22:14:28.083Z
Answers.UserDisplayName: Brad Bell
Body: <p>At the moment there seems to be no UI / function for changing the product type for an existing product?</p>
  
  <p>I see theres a typeId column in the products table. Would it be as simply to change this? Would this cause any issues elsewhere?</p>
  
Tags: <plugin-craftcommerce>
Title: Changing product type for products in Craft Commerce
ThreadText: # Changing product type for products in Craft Commerce
  
  (Asked by: username_0 on 2017-05-18)
  
  At the moment there seems to be no UI / function for changing the product type for an existing product?
  
  I see theres a typeId column in the products table. Would it be as simply to change this? Would this cause any issues elsewhere?
  
  **Tags:** plugin-craftcommerce
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-05-18. Score: 1
  
  I personally think mucking with the schema here is bound to get you in trouble. Very easy to miss something.
  
  If you don't have much data in yet, simply start again, and chalk it down to learning/experience. (Personally I think there should be a 'Start This Way' page in the Commerce docs that emphasises Data Modelling for product types is where you should begin!).
  
  If you do have a lot of data in, best to export & then re-import your data using e.g. FeedMe - <https://sgroup.com.au/plugins/feedme/getting-started/introduction>
  
  (You will need the Pro version which support Products)
  
  > **Comments:**
  > **username_2**: We can easily change entry type of entry and nothing says that it is something bad. Changing product type would be the same.  
  
  ---
  
  ### Answer by username_3 on 2017-05-18. Score: 0
  
  Assuming this is because you've got a ton of products already setup?
  
  There are `productTypeId` columns in other tables you'd want to consider as well. `craft_commerce_discount_producttypes`, `craft_commerce_producttypes_i18n`, `craft_commerce_producttypes_shippingcategories`, `craft_commerce_producttypes_taxcategories`, `craft_commerce_sale_producttypes` just from a quick scan of the schema.
  
  As always, make sure you backup your database first and test thoroughly afterwards.
  
  
  ---
  
  