DataSet
represents an entity, for example a database table. Each DataSelection
represents an orderly group of DataSets
. For more Information take a look at the articles on dataSelection and dataSet:mr
, but the user can also create custom ones. In Shopware 6 there are also default salutations like mr
and the user can also create custom ones. So the salutation mr
from Shopware 5 must be mapped to Shopware 6 mr
. In this default case the mapping can be achieved automatically, but customized salutations will most likely have to be mapped manually. The premapping will be written into the mapping table to associate the old identifier with the new one.Reader
objects to read the data from the source system. For the shopware55
profile we have the api
gateway, which communicates via http/s with the source system, and the local
gateway, which communicates directly with the source system's database. Thus both systems must be on the same server for successfully using the local
gateway.ShopwareApiGateway
you have to download the Shopware Connector plugin for your Shopware 5. For more details have a look at the Gateway and reader.Reader
objects is transferred to Converter
objects that put the data in a format Shopware 6 is able to work with. Simultaneously entries in the underlying mapping table are inserted to map the old identifiers to the new ones for future migrations (Have a look at the MappingService
for that). The mapping is saved for the current connection. Converted data will be removed after the migration, the mapping will stay persistent. Also a checksum is saved to the mapping to identify and skip the same source data (data has not been changed since last migration). You can find out more about them here:Writer
objects will receive the converted data and write it to Shopware 6. There is no special magic here and you don't need to worry about error handling because the migration assistant takes care of it. To learn more about them take a look at writers.local
gateway will copy and rename the files directly in the local filesystem. For more Details you can look at Media processing.DataSelections
)DataSet
in every selected DataSelection
(mapping is used to store / use the identifiers from the source system.) 4.1 The corresponding Reader
reads the data 4.2 The corresponding Converter
converts the dataDataSet
in every selected DataSelection
5.1 The corresponding Writer
writes the dataswag_migration_media_file
table will be downloaded / copied 6.2 Files are assigned to media objects in Shopware 6Run
/ MigrationRun
and will be saved to let the users know about any errors that occurred (in form of a detailed history).DataSelection
. It is also possible to create a new profile, in case a migration from a different shop / source system is sought.