Are you migrating an episerver site to a new version or are you going to re-build a site based on an other platform to EPiServer?
If the latter, you should, IMHO, take a general grip on the site as if you were creating a completely new site. Go back to the initial requirements and take them for another round, dropping old requirements and adding new ones. If you try to do a 1:1 migration you are bound to run into problems with old designs that were affected by the old architecture and have to be really squeezed and twisted into the episerver platform. It will only end in tears. Promote this as a chance for the customer to improve functionality and user experience. There are, IMHO, no pure technology migrations.
If anyone has any top tips for things to think about or watch out for as we begin our EPiServer migration project, I would be very grateful!
Our website is www.cimaglobal.com, an international accounting qualification and membership body. The site is medium-sized, about 3000 pages. It is a fairly straightforward site in terms of functionality. Our users are profesisonals and students all over the world. We get about 2 million unique users a year.
Any tips would be great.
You can also find me on the 'Web Managers' group on LinkedIn. It would be great to connect with other web managers using EPiServer.