Missing version 2.3.6

[muxmix]

Hello,

What about version 2.3.6? Will it be released or should I use only version 2.3.5 then upgrade?

Thank you

[m2-assistant[bot]]

Hi @muxmix. Thank you for your report. To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[kanevbg]

7 days post release of Magento 2.3.6 :(

[hanaks]

I have already installed Magento 2.3.6. Will there be a data migration tool for it?

[vandark25]

Any update about this ?

[Ddcdom]

Magento 2.4.1 was released on 14th October 2020. The day after (15th Oct) the corresponding migration tool was released. Magento 2.3.6 was released on 14th October 2020, but still no migration tool.

[sweetappleuk]

For reference, if i try a migration from M1.9.4.5, using M2.3.6 with the 2.3.5 migration tool, it repeatedly fails with the following error, after mapping out all errors via my migration Module.

Notice: Undefined offset: 7 in //vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 503

Would be good to have an official Migration TOol for 2.3.6 so I can at least eliminate that as a reason for the migration failing.

[ahonecker76]

I have exactly the same problem. 2.3.6 Migration tool seems not existing yet and 2.3.5 not working. - I am unable actually to migrate an old 1.9.x shop data now to new 2.3.6 :( - Any idea when it would be available ?

[jajajaime]

Bumping this, as I also need it for a project.

[TimboDyne]

Bumping this as well, as I also have an immediate project requirement.

[ahonecker76]

In the meanwhile i could migrating the the date from 1.9.x shop to 2.3.6 shop with help of service called litextension (Google for it) Cost money but works 100% migrating all data and settings (like Taxes). I am only wondering they could do this and the free migration tool still is not able to.

[f1-outsourcing]

In the meanwhile i could migrating the the date from 1.9.x shop to 2.3.6 shop with help of service called litextension (Google for it) Cost money but works 100% migrating all data and settings (like Taxes). I am only wondering they could do this and the free migration tool still is not able to.

"This is an Integration with a Third Party Service. " Yes and send all your data to a third party, very smart (and legal)

[ahonecker76]

"This is an Integration with a Third Party Service. " Yes and send all your data to a third party, very smart (and legal)<

I am terrible sorry, but i do not understand the meaning of your statement. Thats a 3th party service; correct. Thats legal to transfer all product attributes, products, shipment and tax settings; also correct. Smart would be the initial tool would work, or getting an alternative solution.

[jajajaime]

For reference, if i try a migration from M1.9.4.5, using M2.3.6 with the 2.3.5 migration tool, it repeatedly fails with the following error, after mapping out all errors via my migration Module.

Notice: Undefined offset: 7 in //vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 503

Would be good to have an official Migration TOol for 2.3.6 so I can at least eliminate that as a reason for the migration failing.

Just as an FYI, I did not have this issue migrating from a 1.9.2.4 to 2.3.6 using the 2.3.5 tool. The migration succeeded without issues.

[f1-outsourcing]

@ahonecker76

But it is not legal to transfer customers data, without any data processing agreement, nor is it even smart to send all your customers data and what they bought to a third party. I would say it is even careless and irresponsible. Only nitwits handle their clients data like this.