I have quite a few questions….

Background: We have two production Magento websites. One is running on Magento 1.9.x and the other is running on Magento 2.2.x. Being that support for Magento 1.9 is coming to an end likely sometime next year we have future plans to attempt to venture into the Magento Multi-Site world but it’s an unknown area for us.
Thoughts: I’m aware that your extension handles Migration of M1 -> M2 and also provides the ability to Delta migrate to keep new orders in sync. From a previous question I’ve also found that it’s possible to migrate a M1 Default Site -> M2 w/ an already existing store attached as default. I know that we essentially do want to migrate our M1 into our existing M2 without affecting the current M2. From a previous question I asked I found that it is possible to do that with some setting “Merge Default” not checked or something like that.
Questions:

Previously we were recommended on our last question to essentially set up a new server to do the migration on. And essentially copy our current M2 site onto it then perform the M1 -> M2 multi-site migration. The part that confuses me here is how do we go about keeping the copied M2 site in sync with the current production M2 site in terms of it’s data.
It doesn’t seem like your extension does M2 -> M2 syncing?
Essentially how would we go about keeping the what would become the new multi-site server with both sites on it in-sync with their production M1 and M2 counterparts?

2 answers

Profile photo of ubdev Staff 34600.00 $tone December 19, 2018
Public

Hi Holden Monroe,
We’d like to answer your questions below: 

it’s possible to migrate a M1 Default Site -> M2 w/ an already existing store attached as default. I know that we essentially do want to migrate our M1 into our existing M2 without affecting the current M2.

Yes, you can migrate your Magento 1 db to your live Magento 2 database directly. However, please make sure you strictly follow all steps in our Readme.html that comes packed with your download package to minimize unexpected issues.
In case you select the Merge Default Website option, there might be issues if your M1 db has bad data section. You can make a clone of your current Magento 2 site to proceed a testing migration though.

From a previous question I asked I found that it is possible to do that with some setting “Merge Default” not checked or something like that.

If you enable the Merge default websites option in Step 2, all data which belongs to your M1 default website, default store, default store view will be migrated automatically and merged into the data of the default website, default store, default store view in your existing M2 instance.
If you do not select the ‘Merge Default Websites’ option, then your M1 data will be ported into M2 in a separated website.

And essentially copy our current M2 site onto it then perform the M1 -> M2 multi-site migration. The part that confuses me here is how do we go about keeping the copied M2 site in sync with the current production M2 site in terms of it’s data. It doesn’t seem like your extension does M2 -> M2 syncing?

It’s pity that our migration helps you migrate data from M1 to M2 only. M2 to M2 sync is not available though.
Hope that helps.
Regards,
Ubertheme team

#1
Profile photo of ubdev Staff 34600.00 $tone December 19, 2018
Public

Hi Holden Monroe,
We’d like to add one more note that if you enable the Merge Default Website, it will not be possible to use the Keep Original IDs setting. You can refer to this blog post to learn more about the Keep Original IDs setting. 
Regards,
Ubertheme team

#2

Please login or Register to Submit Answer

Written By

Comments