Migration from eZ Publish

eZ Platform and eZ Studio introduce a whole new user interface a= nd several new features. This section will attempt to give an overview of t= he migration process.<= /span>

Changes overview

Incompatibili= ties with legacy

eZ Platform and eZ Studio represent the 6th generation of eZ Publish, an= d while the 5th generation had a major focus on backwards cod= e compatibility with the 3rd and 4th generations (legacy), the 6th= generation does not.

The 6th generation is aimed at being fully backwards compatible on the f= ollowing:

Content from 4th and later 5th generation installation=
Code from 5th generation system when written for P= latform (Symfony) stack

The specific incompatibilities

The specific changes that will be migrated and are incompatible with leg= acy are:

XmlText fields have been replaced with a new RichText field
Page field (ezflow) has been replaced by the LandingPage field, and is now provided by= our commercial product eZ Studio
Incremental future improvements to the database schema to improve featu= res and scalability of the content repository

Together these major improvements make it practically impossible to run = eZ Platform side by side with eZ Publish legacy, like it was possible in 5.= x series. For these reasons we recommend that you use eZ Publish Enterp= rise 5.4 (which is supported until end of 20= 21) if you don't have the option to remake your web application ye= t, or want to do it gradually.

Migration Path

From legacy (4.x or 5.x) to Platform stack (5.4/2014.11)

If you are coming directly from legacy (4.x), you need to follow the bes= t practice 5.x Platform migration path and do the following:

Rewrite custom Field Types for the new Platform stack, see Field Type Tutorial
Rewrite custom web front end to use the new Platform/Symfony stack= , see Beginner Tutorial=
Rewrite custom admin modules to use the new Platform/Symfony stack
- And if you do this while on 5.x, you can use several of the available legacy migration features<= /a> to make the new code appear in legacy admin

See Upgrade documentation on how to perform the actual upgrade: Upgrade (eZ Publish Platform page)

From Platform stack (5.4/2014.11) to eZ Platform / eZ Studio
As eZ Platform and eZ Studio introduced completely new user interfaces w= ith greatly improved user experience, the following custom developments nee= ds to be made if you have customization needs:

Write UI code for custom Field Types for the new Javascript-based edito= rial interface, see = Extending PlatformUI and Extending Studio UI

Adjust custom admin modules for the new Symfony-based admin interface,&= nbsp;PLANNED TUTORIAL FOR 2016

For a detailed guide through these developments see Upgrading from 5.4.x and= 2014.11 to 16.xx WILL BE AVAILABLE TOGETHER WITH 16.02 RELEA= SE