Migrate Attributes Set and Attributes from Magneto 1
Forum rules
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
-
- Posts: 40
- Joined: 12 Jul 2018, 19:57
Migrate Attributes Set and Attributes from Magneto 1
Hi there;
Laravel: 5.6
Aimeos: 2018.4
PHP: 7.2
Env: Linux
We are starting to migrate a Magento store to aimeos store, we have a lot of attributes set and attributes in magento that we want to have in aimeos, so I have a couple of questions:
Laravel: 5.6
Aimeos: 2018.4
PHP: 7.2
Env: Linux
We are starting to migrate a Magento store to aimeos store, we have a lot of attributes set and attributes in magento that we want to have in aimeos, so I have a couple of questions:
- What is the best way to have them in the database ? as a attributes or as a product properties? those terms are a little confused for us, and at the moment we don't have clear the way to do this import.
- Do you have a proper way to migrate from magento 1 to aimeos ?
--
Jorge A Ramirez
System Engineer
PHP Developer
Jorge A Ramirez
System Engineer
PHP Developer
Re: Migrate Attributes Set and Attributes from Magneto 1
The difference between attributes and properties is rather easy:
- Attributes can be shared between products and build facets for filtering
- Properties are not shared and are only available for one product
Examples:
- "size" is an attribute because the attribute values are used by all clothing products
- "isbn" is a property because it's only relevant for one book
There might be grey areas where it's not so clear if you should use attributes or properties. Then, prefer properties over attributes if you don't need it to build facets for performance reasons. Attributes are referenced in the mshop_product_list table and so are media, texts, prices, etc. If you have millions of entries in the lists table an only thousands in the mshop_product_property table, then your performance might be lower than in could be due to MySQL selecting sometimes the wrong index.
There's no automatic migration script from Magento 1 yet even if we would like to have it. Maybe you could publish yours if you are done. We can help you to get it right but first we need some more information. How are attribute sets stored in Magento? Attributes itself should be in the EAV structure, aren't they?
- Attributes can be shared between products and build facets for filtering
- Properties are not shared and are only available for one product
Examples:
- "size" is an attribute because the attribute values are used by all clothing products
- "isbn" is a property because it's only relevant for one book
There might be grey areas where it's not so clear if you should use attributes or properties. Then, prefer properties over attributes if you don't need it to build facets for performance reasons. Attributes are referenced in the mshop_product_list table and so are media, texts, prices, etc. If you have millions of entries in the lists table an only thousands in the mshop_product_property table, then your performance might be lower than in could be due to MySQL selecting sometimes the wrong index.
There's no automatic migration script from Magento 1 yet even if we would like to have it. Maybe you could publish yours if you are done. We can help you to get it right but first we need some more information. How are attribute sets stored in Magento? Attributes itself should be in the EAV structure, aren't they?
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
-
- Posts: 1
- Joined: 24 Jul 2018, 21:33
Re: Migrate Attributes Set and Attributes from Magneto 1
Yes, Magento uses EAV structure. The attribute sets are stored into 1 table, then you have the groups in another and then another table where each attribute is assigned to the specific group and attribute set. As of publishing scripts, given our schedule those will be crude and not really usable i believe. I will have that in mind though if there is such an opportunity.How are attribute sets stored in Magento? Attributes itself should be in the EAV structure, aren't they?