Good morning!
Today is a short one.
We just launched a Migration from Magento 1 to Shopware 6. It was a great and complex project, with a gorgeous customer.
We migrated around 120.000 customer with around 140.000 orders. We (and by we I mean cobby – check them out!) imported and updated 15.000 products from Excel. And everything is running in 16 sales channel. We worked the last weeks and months hard on it and yesterday was the big launch day ? .
Everything took longer than expected. We knew, that the migration will be a beast, but we didn’t expect THAT.
We prepared the import very carefully, because the migration tool is nice, but you need to prepare, set mappings, check the “errors” on Magento side and prepare the data before running the migration. We did all that. It took days and we felt very good.
Updates are important
For a lot of reasons keeping your software up to date is a good thing. The two most important are:
- New features
- (security) bug fixes
But there are some things to consider. If you update your software – in this case Shopware – you need to update all your modules. One thing we didn’t consider was, that the processes we built around 6.4 especially the way to migrate the data might change.
Oh boy were we wrong
We tried a lot, but the import directly to 6.5 didn’t work. So our way was to use the intended way from Magento 1 to Shopware 6.4 and migrate from 6.4 to 6.5. But fiddling out all the problems left and right took a while.
Long story short: We did it!
And what we take out of this:
End with the version you start with
And that means as well: Hurry up, because you don’t want to run on an old version and that means your project must run through fast and not takes months or years.
2 thoughts on “Projects: End with the version you start with”