In the first release of EPiServer CMS 5 we can not, unfortunately, guarantee that EPiFields will work.
We are though planning to implement a similar functionality based on the new technology in EPiServer CMS. Currently we discuss if it should be based on either the URL rewrite mechanism, that handles permanent links internally, or by adding functionality to the part that prepares the page with Friendly URL:s. We have also discussed some other technical solutions but in any case it will not be 100% compatible with the old functionality.
The goal is to support this new EPiFields-concept in SP1 at the latest.
It would be very interesting to get information about this, we have a customer that wants to upgrade to CMS 5 who uses EPiFields. What can I tell them?
In Release 2, which is planned for Q3, a new version of epifields is going to be included. It is now called dynamic content.
It is not exactly the same. Functionality written for epifields will not work and has to be completly rewritten. However dynamic content has new and improved functionality.