Tackle content migration needs for as many eZ Publish versions prior to 5.4 as possible to be able to migrate to eZ Platform. 5.4 migration is already covered out of the box.

Involves:

• Create script cable of migrating content
  • Could either be one upgrading the database and running true all update scripts, or as a content export from legacy using a existing extension, and importing this into new stack.
• Open for community to try out
• Continuously improve script to handle edge cases, and fix database issues detected during upgrade
  • So if import is done via API that will provide us with a lot of exceptions to handle in regards to wrong formats and what not.