Name, Visibility and other product fields emtpy

Hi there,

with the latest version auf DB Migration Pro Tool (bought yesterday) I have the problem, that a least name, price, status and visibility are missing on imported products. What are we doing 

Kindly re-check, seem you do data migration in a backup database of your M1’s database? And you are do wrong when import the backup file.sql. Or you have issue with PHP’s settings on limited of the ‘max_input_vars’ param.
Please provide me the information as followings:
+ Admin credentials and site URL 
+ SSH credentials and web root path of your Magento2 instance.
I will check further and tell you known the root of issue and workaround to solve that.
Regards,
Mall.

Hi there,

Addition: max_input_vars was corrected as suggested by your tool and the warning did not appear any more.

That is a good news. Also, please make sure that, the table ‘core_store’ in your M1’s database (source database) has one record which has store_id = 0 as in this screenshot: https://prnt.sc/hwb53j
And then, you could continue with our tool at your end with steps as indicated in the guide of our tool in the Readme.html. And contact me if you need further assistance.
Regards,
Mall.

Hi there,

Can you tell me what is missing? Or is there something we can do, to make it work?

After importing the backup file.sql to new M1’s database, please re-check the table ‘core_store’ as per my reply #4.

We have to remove attributesets and products based on some specific rules.

You shouldn’t do that, because this might cause conflict in the delta migration at a later phase with our tool.
You could disable or remove un-used products, attributes… later after you complete data migration (including delta step) via your M2 back-end.
Regards,
Mall.

Hi there,

I have recognized, that in step 3 table ub_migrate_step_3_attribute the attribute name and visibility (and some more) are missing.

That because you have issue with PHP’s settings in param named ‘max_input_vars’ in first time. As you said in your reply #3 this was solved from your end.
Therefore, you must reset all steps: #8, #7, #6, #5, #4, #3 and redo data migration in these steps again.
You could use CLI command to reset in all steps: php -f bin/ubdatamigration reset
Regards,
Mall.

Hi there,

So is it possible to import from a backup in principle? Because we really have to do that.

Yeah, you could do data migration with our tool with a M1’s database backup instance as you did.
Regards,
Mall.

Hi there,

Got it: The suggestet max_input_vars value of your tool is too low. Testes with 30000 and everything works out fine! Thank you!

Yeah, that depending on the volume of your Attribute sets, Attribute groups and Attributes. Let’s continue at your end and contact me if you need further assistance.
Regards,
Mall.