You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Delta can work effectively only against live/online store. Some of our clients are concerned that the tool installs additional tables and triggers on their stores M1. Thus the safest way is to do main migration from a server's copy (staging server) of the store. This, in turn, makes impossible for Delta to catch new records that came to live store during Data migration.
The solution is described in the next steps.
Merchant sends his current DB dump of M1 store to a developer
The developer migrates the first DB dump to M2 store
The developer makes customization asked by merchant to M2 store
Since item 3 takes some time to implement, for this period new records (customers, orders, etc.) most likely appeared on live M1 store
Merchant sends his second DB dump of M1 store to a developer
The developer by the Data Migration Tool compare the first and the second DB copies of M1 to find the new records (customers, orders, etc.)
The new Delta records are migrated to Magento 2 DB
In the #316 users created a custom script with a similar approach ⚠️ Step number 6 can take a lot of time with big DB. This can be a major drawback of the whole feature
The text was updated successfully, but these errors were encountered:
Right now Delta can work effectively only against live/online store. Some of our clients are concerned that the tool installs additional tables and triggers on their stores M1. Thus the safest way is to do main migration from a server's copy (staging server) of the store. This, in turn, makes impossible for Delta to catch new records that came to live store during Data migration.
The solution is described in the next steps.
In the #316 users created a custom script with a similar approach
⚠️ Step number 6 can take a lot of time with big DB. This can be a major drawback of the whole feature
The text was updated successfully, but these errors were encountered: