Currently, you can migrate the following data:
Shop features
The following data requires manual assignment during migration:
Order status
For this purpose, a pre-mapping is used to determine the successors to be used in Shopware.
This may require creating the corresponding data in Shopware in advance.
In Magento 2, this concerns additional data that are no longer available in the database and therefore cannot be taken into account during migration. This includes country, currency, and language assignments set in the sales channels.
All attributes are migrated except "manufacturer" and "cost".
Since Magento does not have a separate entity "manufacturer", the data will be taken from the "manufacturer" attribute if it is set.
Magento 1-attributes are migrated to properties when:
These were created by the user (no system attribute)
whose setting "Use filter navigation on search results pages" is set to "Filterable (with results)" or the setting "Use to create configurable product" is set to "Yes
Attributes are adopted as variant properties for variants if
These were created by the user (no system attribute)
The setting "Use to create configurable product" is set to "Yes"
Magento 2-attributes are migrated to properties when:
These were created by the user (no system attribute)
Their setting "Use filter navigation on search result pages" is set to "Filterbar (with results)" or the setting "Catalogue input type for shop owners" is set to "DropDown
Attributes are taken as variant properties for the variants if
These were created by the user (no system attribute)
The setting "Catalogue input type for shop owners" on "DropDown" is
Magento 1 and 2-attributes are migrated as custom fields if:
These were created by the user (no system attribute)
The following product types are migrated:
Simple product
Configurable product
Configurable products in Magento are migrated to the "product container
The Simple-Products attached to the configurable product are migrated as variants
Downloadable product
Stores are migrated to sales channels, which are then assigned languages via shop views. If no shop view is available, the default language from Magento is used.
The product/category media can be retrieved from the Magento database and can be migrated normally. However, since the CMS data is not listed in the database, migration is not possible at this point.
Magento knows cross-selling, up-selling and related products. These are migrated as a single cross-selling group to Shopware 6.
Orders are migrated based on the delivery:
If a delivery exists in Magento, it will be migrated with the status "Delivered" (or what was selected in the pre-mapping)
If there is no delivery in Magento, an order is created with the status "Open" (or what was selected in the pre-mapping)
After you have performed the migration and the data selected in the migration plugin has already been transferred, there are still a few points that require manual review and, if necessary, adjustments.
The sales channels represent the basic interfaces to other program areas, such as the shop frontend.
In Magento, there were Stores and Store Views. For the Stores from your Magento installation, we create, if possible, sales channels in Shopware. We convert the store views into the languages of these sales channels.
Please make sure that the sales channels are correctly positioned and check the settings of the individual sales channels and create additional channels if necessary.
You can find information on this in the documentation under Sales Channels.
The migration creates Magento Stores as separate sales channels in Shopware 6. However, when Shopware 6 is installed, 2 sales channels are already created in the standard system.
If you do not see the migrated data in the frontend, the previously installed sales channel is opened via the standard domain.
To see the migrated data in the frontend, it is necessary to adjust the domain settings of the additionally created sales channels.
Shipping
Since the shipping costs in Shopware 6 are technically different from those in Magento, it is not possible to transfer the data automatically. Among other things, the extensive functions of the Rule Builder are now available to you.
Therefore, it is necessary that you create the shipping costs again.
You can find the shipping costs module under Settings > Commerce > Shipping
Detailed information about the new shipping module can be found in the Docs article Shipping.
Payment methods
Similar to shipping costs, the payment methods are also not compatible with Shopware 6, which prevents automated data transfer.
Please check under Settings > Commerce > Payment methods, the already existing data, and complete any not yet existing payment options.
In the article payment methods you receive all relevant information to manage and create the payment methods in Shopware 6.
Countries
You should check under Settings > Localisation > Countries whether all countries relevant for you are present and active.
You can find out how to add new countries and how to adapt existing ones in the documentation under Countries.
Document configuration
In Magento, documents are created "on the fly" during retrieval. In Shopware 6, they are created during creation and stored in the shop system. A migration of the document templates from Magento is therefore not possible.
You can add your letterhead data, account data, etc. to the documents in Shopware 6 under Settings > Commerce > Documents.
Additional information can be found in the article Documents.
E-Mail Templates
Shopware 6 uses "Twig" as a template engine, so it is not possible to use the previous email templates from Magento. You can access the module via Settings > Content > Email templates.
Under Email templates, you will find the information you need to customise your templates.
There are also hints about the Twig variable format.
Shop pages like the imprint, an about us page or inspiring category pages you create in Shopware 6 in the Shopping Experiences. As this is based on a different technical framework than Magento, it is currently not possible to transfer the data.
Please adapt the shop pages and landing pages to your needs or create new ones. You can find the module under Content > Shopping Experiences.
With Shopware 6, the basic architecture has been completely redesigned, and in this context, Shopware also relies on new technologies. Your old Magento templates can therefore not be migrated.
So that you can get started with Shopware 6 directly, Shopware 6 comes with its own template.
If you want to use your own custom theme, you can use the included template as a basis.
You can find out how to adapt the template accordingly in our developer documentation.
Alternatively, you can browse our Plugin Store for a suitable theme.
After the migration, we generally recommend that you compare the individual functions of your new Shopware 6 instance with those from Magento by calling up the individual functions in both systems, such as the article detail page or completing an order.
