Poll
Question:
Acurate order history is important for my business
Option 1: Yes
votes: 3
Option 2: No
votes: 0
After migrating from 1.17 to 2.0 using the build in migration tools, the original order numbers are not honored.
Any gaps in the old database (due to deleted) orders means all subsequent order numbers shift during migration. Busineses owners normally have a need to consult their order history and would like to keep their historic order numbers the same.
If we are migrating the data, the purpose is to keep the data correct, right?
Otherwise there is not much purpose of migrating data in the first place.
The migration tool is closing gaps with the order numbers, so customer order numbers do not match anymore.
Perhaps an option 'cleanup order numbers' can be introduced for those want to keep their original order number.
as described already here http://forum.virtuemart.net/index.php?topic=94345.msg310292#msg310292
do not mix up number and ID. The ids are new after the migration, yes.
OK an example. The human readable order number 1000 in VM1 becomes order number 960 after the migration in VM2.
It makes reference to pre-migration order numbers impossible after the migration. What you mentioned is that deleted orders cause a gap in the numbers and that VM2 closes this gap to "clean up". Modifying this data makes a migration and business administration unreliable (or impossible), hence my request not to re-number or make the "clean-up" optional. Thanks for your consideration.
Again
ordern_number!=order_id !!!!!
Whatever order id or order number, call it the one in the front end, call it the other in the db table... thats the technical background..the point is..
VM1
(http://virtuemart.net/documentation/User_Manual/figure/img036.png)
is based on a human readable order reference idnumber (not to say id or number) and now these reference numbers change during migration. We don't change the prices of the products using the migraiton tool, why change the reference numbers of the orders? I'm aware that VM2 has different concepts. If you offer a migration for order data, I prefer the details of those orders to remain the same.
I fear that vm1 is showing the order_id as order_number. I have to take a look on it. By the names itself vm2 is migrating ordernumber, look part of the sql is
`o`.`order_number` as `vm1_order_number`, later we use $orderData->order_number = $order['vm1_order_number']; So we map the order_number on the order_number.
2.03j is allowing not to re-write the order numbers which is great, *thanks* for making this possible.
Is in it since some weeks already :-)