if we do an upgrade what happens to the actual data stored in episerver. Does it dissapear if we haven't created corresponding blocks before doing the upgrade?

Is all information still available in EPiServer and we can just replace the composer functionalty template by template?

Does no one have any input on this?

Hi Per,
The structure and format that Composer uses for storing Block data is quite different to the one used for Blocks in CMS 7. So when we looked at different options for bringing a Composer site to CMS 7 we made the decision to use a migration strategy to keep things simple.

If you were to just upgrade a Composer site, all the information would still be there but not in a form directly usable to CMS 7. You would end up with a page structure containing what is known in Composer as shadow pages or block and container pages. These pages along with each page that has any Composer elements on it would each have a long string property containing XML used by Composer.

To make these pages work in CMS 7 as blocks, you would have to restructure the shadow page tree, transform the xml property values and replace a number of property types. This is essentially what the Composer migration module does when importing content that has been exported from a Composer site.

Hope that helps explaining things a bit further, it would also be good to learn why you found the migration approach not to be sufficient.

Regards,
Henrik

Thanks for the reply Henrik.

I have never worked with composer and I'm just trying to figure out what options I would have. Would it for instance på easier to just upgrade the site and throw away the composer stuff and have the editors replac the content manually? I guess that is no straight answer for this though and I fully understand that.

I don't think the migration process to be insufficient. The word migration just gives me a headache because of previous work experiences :).

Thanks again for answering.

/Per