1. Migrating to EPiServer CMS 5 Johan Björnfot - jb@episerver.com

2. Why Migration and Not Update? »Major changes in CMS5 compared to 4.62 Own user handling -> ASP.NET membership Unified file system -> Virtual path providers Permanent link support New serialization format in Object Store … 2

3. Parts of Site Migration »Data migration Data in database File systems »Code migration Page templates Custom properties 3

4. Migration Tool – Data Migration »Prerequisites Site to migrate must be version 4.62 (source) Installed CMS 5 SP2 site (target) SQL Server 2000 not supported Form properties must be converted to Xforms (or removed) 4

5. Things to Check Before Migration »Run migration on backup of database! Migration tool will do an ”in place” migration of the database. »Use Simple Recovery model in SQL server. »Drop custom constraints toward EPiServer CMS db tables. »Check that unified file systems are configured as wanted? »Check that there is enough disk space. »Migration tool events for custom actions. 5

6. Migration Steps 1.Object store data 2.Relational data (includes conversion of custom property types) 3.Update database schema 4.Update web.config settings 5.Register ASP.NET and WF sql scripts 6.File systems 7.Convert links 8.Convert LongString -> XhtmlString (optional) 9.Create ”skeleton” page types 6

7. Demo »Migrate 4.62 site 7

8. Time Estimation »Most time-consuming steps Object Store (~ 30 mins/100,000 objects) Native File system (~ 10 mins/1GB) Link migration (~ 25 mins/10,000 pages) 8

9. What Else Does the Migration Tool Do? »The migration tool will create a ”converted” type for each custom property type. »In EPiServer CMS 5 each language code must be parseable as a CultureInfo object. Migration tool offers conversion, e.g. ”DK” should be ”DA”. 9

10. What Doesn't the Migration Tool Do? »Migrate Oracle-based sites »Migrate users (although access rights are migrated) »Migrate mirroring state »Migrate workflows 10

11. Logging »There will be a log called MigrationLog.log created in C:\ProgramFiles\EPiServer\MigrationTool »Any errors occured during link migration is logged on a file MigrateLinksErrors.txt in the root of the target CMS 5SP2 site. 11

12. What to Do After Migration of Data? »Convert page templates »Convert custom page properties »Scheduled jobs »Code conversion to CMS 5 API 12

13. Documentation »Tech note about migration tool  http://world.episerver.com//Documentation/Items/Tech- Notes/EPiServer-CMS-SP2/Migration-Tool-RC1/ http://world.episerver.com//Documentation/Items/Tech- Notes/EPiServer-CMS-SP2/Migration-Tool-RC1/ »Tech note about migration of code  http://world.episerver.com//Documentation/Items/Tech- Notes/EPiServer-CMS-5-SP1/Migrating-from-CMS-462-to-CMS- 5-SP1/ 13