Why is the store code changing from {code} to {code_storeId} while migrating from m1 to m2? how can we keep it as is?
9 answers
Hi there,
Why is the store code changing from {code} to {code_storeId} while migrating from m1 to m2?
That was because your M2 database has a store view with the same M1’s store view code.
You can edit the store view code in M2 to differentiate with store view codes in M1 before you do data migration with our module.
Regards,
Mall.
Before migrating M2 has store code 0 and 1
M1 store codes are: 0,5,6,7
So the only common store code is: 0
But migrating creates store code: 1,2,3 (in stead of 5,6,7)
Can you please assist in solving this issue?
Best regards
Nardus
Hi Nardus,
Can you please assist in solving this issue?
The values you mentioned are Store view IDs, not the store code.
That is a normal working rule of our module. The ‘Keep original IDs’ for Stores isn’t support in our module yet.
As you can see, M2 always has default stores, thus such process in our tool is aimed at avoiding the IDs conflict issues.
Regards,
Mall.
We bought the Pro version we got the same problem.
Your migration tool should include these options.
The fact that magento2 has already its own id’s already doesn’t mean you can not update it.
Can you adjust your scripts and send us a complete adjusted module where we can keep:
1-website ids
2-store ids
3-categories ids
Hi there,
It’s a pity that upon the current workflow of our migration tool, it’s not possible to keep the ids of the data objects you mentioned.
There might be unexpected complex issues when trying to keep the original IDs of those objects. If you still insist on this option, please consider using our paid customization service, we will consider a workaround for your specific case.
Thanks for your understanding.
PS. Since our team is off during the weekend, our apology for a certain delay in responding to you.
Regards,
Ubertheme team
Thanks for your message.
Am sorry but, we expected a little more support from you for 300 euro. all what we get is instructions and buggy code.
Nevertheless, we changed your code in step2 and step4 to get Website,Store,Category ids match with m1.
Thank you anyway but i advise you to edit your code for future clients.
Good bye
Hi there,
We’re sorry for replying to you this late as we’ve just been back from our weekend.
As mentioned in our previous reply, unexpected complex issues might arise when trying to keep the original IDs of those objects. Anyway, please move forward with the process at your end.
If you have any further questions, please let us know.
Regards,
Ubertheme team
+1 to dominidesign
Store codes are the things that MUST NOT be changed.
It could be a lot of application business logic that depends on this constants.
Website codes are prefixed with ‘_migrated’
Default website code remains unchanged (base)
I believe you take it as major issue and fix asap.
thanks
Hi there,
I believe you take it as major issue and fix asap.
So, you can edit the related data objects to remove the suffix you mentioned in the backend of your M2 site after the data migration with our migration tool.
In case you need further helps, please submit a new ticket, I will follow up with you then.
Regards,
Mall.
