Hello,
I’m sorry that you are experiencing this problem.
If you have decided to migrate all balances and transations, then it is possible that the old custom SQL balances and the new CPT balances may not match.
This will happen if, during migration, a transaction cannot be created as a CPT for some reason. Typically this will happen if the migration task cannot create the transaction because it can’t auto-create the associated currency. In any case, if any such error occurs, then the admins will be notified by email with details about the error. You can then go and see what the problem was, and maybe create the transaction manually. A good idea is to first create all currencies manually, and then let the migration task migrate the transactions. This will ensure that such errors will not occur. If you let the migration task auto-create the currencies, then things can go wrong in some cases.
If you have decided to migrate only the balances, then all the new balances should be equal to the old ones. You can revert the migration, and once it is fully reverted, you can retry by migrating only the balances.
The market_not_enumerable error indicates, again, that there is a problem with the currency associated with the market. Please check your market by visiting /wp-admin/post.php?post=5104&action=edit and re-assign the currencies to the market.
My recommendation is that you:
1. revert the migration
2. create manually all the currencies that the old system was using
3. rerun the migration (either transactions or balances only)
4. if you get any errors in the admins’ emails, then address them
5. check your markets and ensure that the correct currencies are assigned
If you choose to migrate the balances only, then it is almost certain that there won’t be any problems with balances, but the old transaction history will not be shown. In any case, pay attention to any migration-related emails.
Hope this helps.
with regards