Data migration is not working correctly

Hi there,

I have migrated my magento 1.6x DB with Magento 2.1.3 using UB Data Migration older version, 

May I know what version of our tool you used in the first time? We have an outdated script on Github which we no longer use. 

1. it’s creating additional category named(migrated) and also creating additional website and stores

Yes, that is right. It seems you have used ver2.x of our tool in your first migration. Please note that, our v2.x and v3.x has difference process and this is the root of issue.

The visibility of all configurable product changed to “Not visible” and their child product visibility changed to “catalog, search”, both are incorrect.

This is a strange issue. Our tool doesn’t make any change to your product’s setting on visibility attribute. Kindly re-compare with your products in Magento 1 to see the original setting of such product in M1.

Please let me know if i’m doing any worng.

With our latest tool version 3.0.9, you should consider re-migrating from the ground up in a new fresh Magento 2 instance.
Regards,
Mall.

Hi there,

I have used 2.0.4 pro version for migration earlier.

Yes, so that is the root of the issues you mentioned.

1. During the migration, product url get changed to {{base_url}}.html.html , there is extra “.html” appending in product url

That was because there are some new working rules in Magento 2 regarding URL rewrite. To fix that, you can run the following SQL in your Magento 2 database:
//Before running SQL below, please make sure the product’s attribute with code = ‘request_path’ has attribute_id = 120 in your Magento 2’s database.
 

UPDATE catalog_product_entity_varchar SET value = REPLACE(value, '.html', '') WHERE attribute_id = 120;
UPDATE url_rewrite SET request_path = REPLACE(request_path, '.html.html', '.html') WHERE entity_type = 'product';

Once done, please clean Magento 2 cache.
 

Case 1:- If i migrate the magento 1.6x in fresh magento 2.x,
               a) How can i migrate the core_config_data from magento 1.6x to fresh magento 2.x

It’s pity our tool does not support to migrate such data portion at the moment.

Case 2:-  I mentioned in my previous question that i have migrated my data using 2.0.4 pro version, now i need to update the data in existing M2 DB from Magento 1.6x version.
               a) In this case can i use the migration tool ? If i use the migration tool to migrate the data, this create’s the additional category and website.
               b) I have migrated the data, now i want delta migration again, so which is the best way to migrate the data again in existing M2 DB?              

Do you have a backup of your Magento 2 instance with database migrated using our tool ver 2.0.4? If yes, you should do steps as follows:

• Revert Magento2 instance to the first instance with ver.2.0.4 of our tool
• Do reset data migration in ver2.0.4 of our tool.
• Once done, upgrade our migration tool to the latest ver3.0.9.
• Start data migration again with ver3.0.4 of our tool (you should select Merge Default Website option in step #2 of our tool)

And then, you will get the latest data from your Magento1’s database in Magento 2.
Regards,
Mall.
 
 
 

Hi there,

I reset the old migrated data and run migration using latest version 3.0.9, still have the visibility issue, all product have blank visibility and blank status.

So, seem your attributes (visibility and status) has special settings (maybe some settings is not standard as Magento default) in Magento1’s database. I need a closer look to detect the root of that issue. Kindly provide some information as followings:

• Admin credentials of your Magento 2 instance.
• SSH credentials and web root path of your magento 2 instance.
• phpMyadmin credentials of your Magento 1 and Magento 2 databases. (this helps me quick check your databases)

I will check further and reply you more later.
Regards,
Mall.

Hi there,

PHP Error[8]: Trying to get property of non-object
in file /var/www/html/trident-m2_copy3/pub/ub-tool/protected/controllers/Step5Controller.php at line 810
#0 /var/www/html/trident-m2_copy3/pub/ub-tool/protected/controllers/Step5Controller.php(504): Step5Controller->_migrateCatalogProductOptions()

Seem you have deleted some product’s options after the first migration with our tool? Let’s try do steps as followings:
-- Run below SQL statement in your Magento 2 database:

Delete From ub_migrate_map_step_5_product_option Where entity_name = 'catalog_product_option' AND m2_id NOT IN (Select option_id From catalog_product_option);

-- Once done, let’s clean the cache files of our tool by run cli command: rm -r pub/ub-tool/protected/runtime/cache
-- And then, re-run the data migration in the step #5: php -f bin/ubdatamigration run --step=5
And tell me know how it goes.
Regards,
Mall.

Hi Stephen,
This is a strange issue, other users have been migrating their databases successfully, without the log-in issue as you mentioned. Could you please check again if the credentials are correct? 
If the issue still persists, kindly provide us the following info:

• Specific user’s credentials that has the log-in issue and your M1 url (we also need this account to verify if such user can login M1 site successfully or not)
• Your site credentials as per our instruction on our reply #5 here. 

Meanwhile, please help to confirm if other issues we provided workarounds above have been resolved? 
Sincerely,
Ubertheme team
 

Hi there,

I’m running the update mode but the number of products not get increased, why so ? 

How did you run with that task? What cli command you are using? Is your new added products has new categories added?
Regards,
Mall.

Hi there,

php -f bin/ubdatamigration run --step=4 --mode=update
php -f bin/ubdatamigration run --step=5 --mode=update

So, do you have get finished status after run with that cli commands? Did you do reindex your data after run delta migration?
Regards,
Mall.

Hi there,

yes, still showing the old data, not showing the new order/product 

That is strange, kindly provide me the admin credentials, ssh credentials and web root folder path of your Magento 2. I will check further and reply you more later.
Regards,
Mall.

Hi there,

Processing in step #8…PHP Error[8]: unserialize(): Error at offset 0 of 331 bytes
in file /var/www/html/trident-m2/pub/ub-tool/protected/models/UBMigrate.php at line 333
#0 /var/www/html/trident-m2/pub/ub-tool/protected/models/UBMigrate.php(333): unserialize(

Kindly provide me the admin credentials, ssh credentials and web root folder path of your Magento 2. I will check further and reply you more later.
Regards,
Mall.

Hi there,

Message: CDbCommand failed to execute the SQL statement: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column ‘lastname’ at row 1. 

You should view this screenshots:
Magento ver.2.1.7 database: http://i.prntscr.com/0zAvAPizRMWxFUkIYfJ_ig.png
Magento ver.2.1.8 database: http://i.prntscr.com/Pj2h-sMiTdmkrWuHghL1Tg.png
So, to solve the issue as you mentioned in the step #7 in ver.3.1.0 of our tool, you should upgrade Magento core to ver2.1.8 or ver.2.1.9
Regards,
Mall.