Skip to content

Magento 2.1 support? #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
csdougliss opened this issue Jun 17, 2016 · 18 comments
Closed

Magento 2.1 support? #97

csdougliss opened this issue Jun 17, 2016 · 18 comments

Comments

@csdougliss
Copy link

Hi,

When 2.1 is released, can I update to this and the data migration tool will be updated to reflect the changes?
Or will further work be required.

@victor-v-rad
Copy link
Collaborator

Hi,
It is better to wait the release of data migration tool 2.1 There are lots of changes in Magento 2

@redboxmarcins
Copy link

@victor-v-rad Will data migration tool 2.1 be released same time as Magento 2.1?

@victor-v-rad
Copy link
Collaborator

Final test and fix for the tool needs to be done after Magento 2.1 release. So it will take some time.

@csdougliss
Copy link
Author

@victor-v-rad Hope the data-migration-tool for 2.1 is updated soon, there are many bugs in 2.0 and I'd rather develop against it.

  Problem 1
    - Conclusion: don't install magento/framework 100.1.0
    - Installation request for magento/product-enterprise-edition 2.1.0 -> satisfiable by magento/product-enterprise-edition[2.1.0].
    - Installation request for magento/data-migration-tool 2.0.7 -> satisfiable by magento/data-migration-tool[2.0.7].
    - magento/product-enterprise-edition 2.1.0 requires magento/product-community-edition 2.1.0 -> satisfiable by magento/product-community-edition[2.1.0].
    - magento/product-community-edition 2.1.0 requires magento/framework 100.1.0 -> satisfiable by magento/framework[100.1.0].
    - magento/product-community-edition 2.1.0 requires magento/framework 100.1.0 -> satisfiable by magento/framework[100.1.0].
    - Conclusion: don't install magento/framework 100.1.0

@victor-v-rad
Copy link
Collaborator

The tool will be released not only with Magento 2.1 adaptation but also include bugfixes were exist in 2.0

@csdougliss
Copy link
Author

@victor-v-rad When will it be released?

@tadhgbowe
Copy link

Hello. I've just tried:

composer require magento/data-migration-tool:2.1.0

and I get this:

Problem 1
- The requested package magento/data-migration-tool could not be found in any version, there may be a typo in the package name.

Am I correct in saying there's no data migration available for 2.1.0 yet? If there isn't then I'm assuming it would be best to wait until one is available because 2.1.0 is a completely new beast?

If somebody could confirm then I can go home early :-)

Thanks
Tadhg

@redboxmarcins
Copy link

@tadhgbowe correct, data migration tool has different release cycle than Magento, so we can expect it couple weeks later than 2.1

@tadhgbowe
Copy link

redboxmarcins - thank you!

I had been previously playing about with 2.0.7 ce to ce migration tool with decent success. So I shall ignore the potential causes it informed me of and instead wait with great excitement for an updated release very soon!

Cheers
Tadhg

@djmarcsmith
Copy link

Any update for this ? As keen to get migrated over to 2.1 thankyou

@ilol
Copy link

ilol commented Jul 1, 2016

Update for MT to support 2.1 is not ready yet. We are working hard on this

@csdougliss
Copy link
Author

Works thank you 👍

@toddliningerdesign
Copy link

toddliningerdesign commented Aug 9, 2016

@ilol Any update?

@tadhgbowe
Copy link

toddliningerdesign - it's all sorted. You can download v2.1.0 using composer, it installs fine and works okay too. Happy data migrations!

@toddliningerdesign
Copy link

toddliningerdesign commented Aug 10, 2016

@tadhgbowe Thanks for your message.

We are getting the following error while attempting data migration:

Notice: Undefined offset: 14 in /var/public/html/magento2/vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 433

@tadhgbowe
Copy link

Hi toddliningerdesign.

Looking at the code that's in moveAttributeToGroup. Is there an attribute group that M2 can't recognise. In our case we decided not to migrate any eav attributes across. Our EE version (1.13.0.2) had been previously upgraded from a older version so for example none of the eav product attributes matched up when the migration tool began (lots of errors). Our source also contained lots of unwanted attributes. So we decided it would be best to migrate customers and sales orders only. That in itself is a little tricky to do and requires some database tidy up afterwards.

So the error you're getting we've avoided by tweaking other things. No two migrations will be the same. It's a bit of a minefield to identify the source of issues when they do occur. Best of luck!

Cheers
Tadhg

@toddliningerdesign
Copy link

toddliningerdesign commented Aug 10, 2016

@tadhgbowe Thanks for your response, but we need to transfer products as well.

@tadhgbowe
Copy link

toddliningerdesign sorry I'm not able to help here. This issue is closed. Perhaps you can raise a new issue specific to the error you're getting. I hope it works out.
T.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants