How to migrate from Magento 1 to Magento 2

Editor's Notes

• #9: Can‘t talk about everything today
• #10: it's not a simple update You don‘t get Magento 2 with the click of a button or a few commands It‘s a process which involves a lot of manual work. Use it as a chance for a make-over [Next]
• #15: Add repository Magento 2 installation needed, but not Magento 1 Install tool Installation: composer require from Github or repo.magento.com Symfony Console Monolog Configure XML Files Credentials for M1 and M2 databases
• #17: * Custom = your extensions, 3rd party extensions Tables * copy * ignore * rename Columns * copy * ignore * rename * transform value => handlers can be defined (null handler, custom handler, …)
• #20: but it has issues – reserve time! As with every integration project: get real data as soon as possible
• #21: Ensure data integrity Remove un-needed entries
• #22: Create database backup after install (it's easy to introduce foreign key errors in target database; tool expects fresh database) Script steps for execution and reset
• #23: First „collect“ all errors (ignore documents / fields, rename to „“) and when the script runs through think what you make out of that information
• #24: You can have your files anywhere in the file system: Version them in your own repository outside of the migration tool directory structure for better overview and easier re-use You can divide config files further, for example for the different calls
• #25: Although you use a M2 installation, at the moment there is no way for your migrated M2 community extensions to specify mappings in own files – you have to define mappings manually for extensions for every project
• #26: Is said to be not working perfectly at the moment
• #27: Ubertheme Pro: easy to use, little configuration, does the job for standard data, supports delta Con: slow, hard to rewrite, not secured
• #28: Go through the list of extensions and make basic decisions for every module
• #34: 3rd party code: Marketplace
• #37: Second, decide on your homegrown modules
• #42: if you do the extension yourself: do you want to migrate the extension or rewrite it from scratch?
• #43: If you rewrite the extension from scratch: Try to use automated testing – base is better Follow official coding standards Document behaviour as it was in M1 so you know what should work how afterwards Maybe write platform independent code
• #45: If you want migrate the extension: Make sure you followed the coding standards in Magento 1, otherwise you may want to refactor the extension before migrating Good if you have files in separate directory like you have with modman or Composer Of course, also any kind of automated testing helps too Also here: document M1 behaviour think about writing platform independent code: (even more so if you have to develop new stuff before migrating) 
• #46: It has a good documentation!
• #48: A few things that I learned here: [next]
• #49: Installation: you could also do composer require, but there are no official versions yet (current: "0.0.1-alpha") Symfony Console Monolog No Magento 1 or Magento 2 installation needed
• #50: <src>: Good for you if you extracted your code into Composer modules or the like Bring your code in order before doing the migration! See Sergii Shymkos presentation: remove unused modules, revert core modifications. Also interesting: remove core bugfixes irrelevant to M2
• #54: Mapping files make code migration possible Out of the box: newest M1 version to M2 Generated by you: your M1 version to M2
• #55: Obey the order!
• #56: May generate warnings generateModuleMapping: exception with EE If you use <m1>, then mappings for third-party tools etc. may be added
• #58: convertConfig: config.xml is unchanged, so you have to find out yourself what has been moved and what not Bugs: convertConfig: system.xml type, show_in_store etc. not used convertPhpCode: Originale Dateien werden beibehalten, man kann vergleichen was gemacht worden ist Dependency information not migrated properly(?) Event observers not migrated properly(?)
• #59: be pragmatic. work together. find solutions together as you're both going to learn a lot about Magento 2 at this point of time To build a better shop!
• #60: Topics I didn‘t mention at all or not in detail: Theme migration Build & Deployment process