Customer migrated but some fields missing data

Hi there,
Regarding your question: 

But after migration some fields from customer_address_entity table are showing as ‘unknown’ 

That was because your customers had missing values of that attributes and our tool automatically filled with ‘unknown’ string as default value (Because that attributes are required values in Magento2)

and because of this no customer is able to login to frontend. 

No, I don’t think that associates with login function of your customer credentials. Kindly verify the customer credentials again, and make sure such customer can log in successfully in Magento 1 as well.
Also, to login with migrated customer credentials, you must set customer’s website as default website in Magento 2 after completing migration (if you have not selected the option “Merge default website” in step 2 settings of our tool)
Regards,
Mall.
 
 
 

Hi there,

We already have those values in Magento 1 database for each customer, but after migration “unknown” appeared..

Please provide me the following info, I will debug further: 

• Admin credentials of your Magento 2 instance.
• SSH and web root path of your Magento 2 instance.
• PHPMyadmin credentials of your databases (M1 and M2 databases)
• A customer credentials with the issue as you mentioned.

I will check and get back you then.
PS. Please make sure you mark your reply as a private reply, then all your credentials above will be kept confidential. Only you and our technical team can access.
Regards,
Mall.

Hi there,
Please pause all you activities at your end on our migration tool. I’m need more time to detect further the issue as you mentioned in your instance.
And then, i will get back you later.
Thanks for your waiting time.
Regards,
Mall.

Hi there,
I have to detected in long time in your instance and see the root issue because your database has some custom customer attribute and customer address attribute, which was not ready in Magento2 database: https://prnt.sc/h5v3nl
For that case, i have added more tweak code in the step #6 of our tool (pub/ub-tool/protected/controllers/Step6Controller.php)
And then, i have run delta migration with mode update in the step #6 again by run CLI command:
php -f bin/ubdatamigration run --step=6 --mode=update
And now, the issue as you mentioned was solved:
http://i.prntscr.com/D16_vTx8RgeEGjvNBb-H0A.png
http://i.prntscr.com/3A684ODvRemo3bmGrW6kwQ.png
http://i.prntscr.com/1pvulpqvQpeEdegMLBVk0g.png
Kindly have a look and contact me if you need further assistance.
Regards,
Mall.
 

Hi there,

In my primary checking, it seems like problem is resolved.
I am testing with my data. 

Yes, please continue and let me know if you need further assistance.

Please let me know if there are any changes in core files of Ubertheme, so that I will update all those in my staging server code.

As per my reply #8, to handle your case, I have applied additional tweak code in the step #6 of our tool (to the PHP file at :pub/ub-tool/protected/controllers/Step6Controller.php)
PS. If you proceed migration on a new instance, you should download and re-install our UB Data Migration Pro package again.
Regards,
Mall.