Attributes error….

Hi there, 

Attributes error…
SQLSTATE[HY000]: General error: 1364 Field ‘group_id’ doesn’t have a default value.

That is a strange issue. When you got that issue? Please provide us more detailed information about that issue. We will get back to you then and help you out.
 
Regards,
Ubertheme team

Hi there,

Message: Mage2SalesQuoteItem: Original Custom Price is too long (maximum is 12 characters).

That occurred because your M1 database had at least one data record which had bad data in the value of ‘sales_flat_quote_item.original_custom_price‘ field. 

To handle that case, you can try with these steps:

1. Open the PHP file at: pub/ub-tool/protected/controllers/Step7Controller.php
and find the code line:

'row_total_incl_tax', 'base_row_total_incl_tax', 'qty', 'tax_amount', 'base_tax_amount')) AND strlen(trim($val)) > 12) {

and replace it with: 

'row_total_incl_tax', 'base_row_total_incl_tax', 'qty', 'tax_amount', 'base_tax_amount', 'original_custom_price')) AND strlen(trim($val)) > 12) {

Please note that there are two lines in that PHP file you need to update as above.

2. Once done, you continue with the data migration in step #7.

Regards,
Mall.

Hi there,

Migration missing many Tier Prices… How we can do?? 
 
[Processing][run] Step #8 migration completed with 0 CatalogProductEntityTierPrice items;

That is strange. Could reset step #8 and re-perform data migration in this step?

Regards,
Mall.

Hi there,

Already done, same result.

So, it seems that your database had special cases. Please provide me information about your instance:

• URL and admin credentials of your M2 instance
• SSH credentials of your M2 instance
• Let me know the path to the M2 folder

I will help to check further and get back to you then.
PS. Please make sure you mark your reply private or simply switch this ticket to the private mode, then it’s safe to share your site info here. Only you and our technical team can access it. 
Regards,
Mall.

Hi there,
I have checked in your instance and I saw that:
Our migration tool detects that your M1 has a total of 753 tier prices: https://prnt.sc/v75jzj
and in the migration log of our migration tool at path: pub/ub-tool/protected/runtime/ub_data_migration.log
I saw that our migration tool helps to migrate all of 753 tier prices in your M1 to M2: http://prntscr.com/v75soq

[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:35 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:35 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:35 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:36 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:36 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:36 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 100 CatalogProductEntityTierPrice items;
2020/10/24 11:36:37 [info] [ub_data_migration]
[Processing][run] Step #8 migration completed with 53 CatalogProductEntityTierPrice items;

Please recheck again at your end.
Regards,
Mall.

Hi there,

 can u please help with customer login?

Please recheck your settings in M2 and make sure that the migrated customers belong to the current default website in your M2 instance.
Regards,
Mall.

Hi there,

1 exception(s):
Exception #0 (Magento\Framework\Exception\RuntimeException): Type Error occurred when creating object: Magento\Eav\Model\Entity\Attribute\Source\Config

I debugged your instance and saw that issue related to a bad setting of the custom customer attribute code ‘mailchimp_store_view’.
 
It had the `frontend_input = select’, but it had missing value of the ‘souce_model’. You can learn more about it via the following result in your M2 database:

MariaDB [mtbcckdveh]> Select attribute_code, frontend_input, source_model, is_user_defined From eav_attribute Where attribute_code In (‘mailchimp_store_view’);
+———————-+—————-+————--+—————--+
| attribute_code | frontend_input | source_model | is_user_defined |
+———————-+—————-+————--+—————--+
| mailchimp_store_view | select | NULL | 1 |
+———————-+—————-+————--+—————--+
1 row in set (0.001 sec)
MariaDB [mtbcckdveh]>

To solve that issue, you can change the ‘frontend_input’ of that attribute from ‘select‘ to ‘text‘. You can run the following SQL query in your M2 to change:

Update eav_attribute Set 'frontend_input' = 'text' Where attribute_code = 'mailchimp_store_view';

And then, you check the issue you mentioned again.

Regards,
Mall.
 

Hi there,
Our team has just noticed that you submitted a dispute on Paypal regarding the migration issue. 
As explained to you via your other ticket here, our users also run across different issues (you can check at random via this helpdesk on those issues). That said, we want to clarify the fact that: 

• There might be unexpected issues during the migration process (most of the issues associated with the database issue itself, not our module)
• And our team did help our users resolve all those issues successfully. 

So, please move forward with the migration. If you get any issue, please pause at the point of time and provide us the detail of the issue, we will work closely to help you out. 
PS1. We’d like to offer you 60 Days Money Back Guarantee (instead of our standard 7 Days Money Back Guarantee), so you’re completely safe to move forward with our module. 
PS2. Please help to withdraw the claim via Paypal. If we could not help you complete the migration within the scope of data that we noted on our product page, then you can have the full purchase returned. 
Regards,
Ubertheme team 

Hi there, 

Hi, ok but we need to solve this ( i hope ) last bug… User migrated can’t login! How to fix this?

Please help to check and provide us the following info:

1. Make sure you check and log in with corrected Customer credentials?
2. Make sure the migrated customers belong to the current default website in the M2 instance (the instance that you are testing)
3. Please us know your M1 version?
4. And let us know the Customer’s password encryption was performed by which algorithms in your M1? This algorithm is applied automatically to all customers in M1 or not?

We will follow up on your case once knowing further details above. 
PS. We could not provide instant or near real-time response, however, we will try our best to reply as soon as possible. 
Regards,
Ubertheme team

Hi there,

4: How can i know this info?

You can check it in the string value of some customer’s passwords in your M1 database. You can run the following SQL query in your M1 database to look for that information: 

SELECT * FROM `customer_entity_varchar` WHERE `attribute_id` IN (SELECT `attribute_id` FROM `eav_attribute` WHERE `attribute_code` = 'password_hash');

3: 1.9.4.5

So, I guess that the customer’s passwords in your M1 database encryption was by the SHA256 algorithm. Please try with the steps below at your end:

1. Open the PHP file at: pub/ub-tool/protected/controllers/Step6Controller.php
and find the code lines:

if ($table == 'customer_entity_varchar' AND $attributeCode1 == 'password_hash') {
    $customer2->$attributeCode1 .= ":0"; // In Magento2: 0 is HASH_VERSION_MD5
}

and replace it with:

if ($table == 'customer_entity_varchar' AND $attributeCode1 == 'password_hash') {
    $customer2->$attributeCode1 .= ":1";
}

2. Next, run the following SQL query in your M2 database:

UPDATE `ub_migrate_map_step_6` SET `offset` = 0 Where entity_name = 'customer_entity';

3. And then you run the delta migration in step #6 by running the CLI command:

php -f bin/ubdatamigration run --step=6;

Once done, reindex the data and check the login function with some migrated customer credentials in M2.
 
And let me how it goes then.
 
Regards,
Mall.
 
 

Hi there,

now saving customer gives me this error:
 The store view is not in the associated website.

That is a strange issue. Did you change any websites, stores, store views in the Store management after the first migration?

Did you reindex the data successfully after you finished the data migration in all steps of our module?
 
And did that issue happen with some customers or all migrated customers?
 
I saw you hadn’t checked to migrate all Store views: https://prnt.sc/vee5nj. This may relate to the issue you mentioned.
 
Regards,
Mall.
 

Hi there,

[Processing][run] in step #7: ……………………………………………………………………………………………………………………………………………………………………………………….PHP Error[8]: Trying to get property ‘attributes’ of non-object

You can try these steps:

1. Run the SQL queries below in your M2 database:

DELETE FROM ub_migrate_map_step_7 WHERE entity_name = 'salesrule' AND m2_id NOT IN (Select rule_id From salesrule);
DELETE FROM ub_migrate_map_step_7 WHERE entity_name = 'salesrule_coupon' AND m2_id NOT IN (Select coupon_id From salesrule_coupon);
DELETE FROM ub_migrate_map_step_7_order_item WHERE entity_name = 'sales_flat_order_item' AND m2_id NOT IN (Select item_id From sales_order_item);
DELETE FROM ub_migrate_map_step_7_order_address WHERE entity_name = 'sales_flat_order_address' AND m2_id NOT IN (Select entity_id From sales_order_address);
DELETE FROM ub_migrate_map_step_7_quote WHERE (entity_name = 'sales_flat_quote' OR entity_name = 'sales_flat_quote_active') AND m2_id NOT IN (Select entity_id From quote);
DELETE FROM ub_migrate_map_step_7_quote_item WHERE entity_name = 'sales_flat_quote_item' AND m2_id NOT IN (Select item_id From quote_item);
DELETE FROM ub_migrate_map_step_7_quote_address WHERE entity_name = 'sales_flat_quote_address' AND m2_id NOT IN (Select address_id From quote_address);

2. And then, you run the command to clean the cache of our module:
rm -rf pub/ub-tool/protected/runtime/cache/
3. Once done, continue with the data migration in step #7 as normal. 

Regards,
Mall.

Hi there,

To resolve this conflict, you can either change the value of the URL Key field (located in the Search Engine Optimization section) to a unique value, or change the Request Path fields in all locations listed below:
…

That issue occurred because your database had some duplicated values of URL Key on categories and associated products. And it came from the original settings of URL Key on categories and associated products in your M1 database.

And that caused the issues as you see with new working rules of M2 when M2 regenerated URL rewrites for the category and associated products.
 
To solve that issue, you have to edit the value of the URL Key on related categories and products as suggested by Magento.

Alternatively, you can try these steps:

1. Run the CLI command provided by our migration tool:

php -f bin/ubdatamigration fixduplicateurl

2. And then, you check the issue you mentioned again.
 
Regards,
Mall.
 

Hi there,

If I try to move category i get this error:
 No such entity with id =XX

Please try to solve that issue with the workaround suggested in this post.
And let me know how it goes then.
Regards,
Mall.

Hi there,

The issues you mentioned on the categories are strange. Actually, they related to Magento’s functions. 

Also, I saw that you used a third-party extension to re-generate URL rewrites in your reply #27. It may affect the category’s data in M2.

Please try steps below to rerun data migration in step #4 of our migration tool. But, please note that all your changes on migrated categories in M2 will be overridden with category’s data in M1 after you run the following steps:

1. Run the SQL query below in your M2 database:

UPDATE `ub_migrate_map_step_4` SET `offset` = 0 Where entity_name = 'catalog_category_entity';

2. And then, you run data migration in step #4 using the CLI command:

php -f bin/ubdatamigration run --step=4

3. After you finished step #4, check the issues you mentioned again.
And let me know how it goes.
 
Regards,
Mall.
 

Hi there,

I can’t see new product inserted on frontend…I have check all, reindex, cache…we still no see new products…this is happen after migration.

Please check at your end again and make sure that:

• You did set the migrated root category as the Root Category of the current default Store in current default website in your M2 instance.
• Your products are in stocks and visible in the frontend.
• You have reindexed the data successfully.

Regards,
Mall.

Hi there,

But I can’t see new products. Can u please help?

Please try these steps:
1. Run the following SQL query in your M2 database:

UPDATE `ub_migrate_map_step_5` SET `offset` = 0 Where entity_name = 'catalog_product_entity';

2. You run data migration in step #5 using the CLI command:

php -f bin/ubdatamigration run --step=5;

3. And then, reindex the data and check the issue you mentioned again.

Regards,
Mall.