Prev |
Migrating a site includes several activities:
- Preparing a database for conversion.
- Copying site content.
- Checking the result.
This chapter gives some general recommendations on these parts of the process.
You should also refer to the links below:
1. Migrating from Sitecore V4
Preparing a 4.3.x Database for Conversion
- Backup your database.
- If your Sitecore installation is not 4.3.2.x, upgrade database to the latest Sitecore 4 version. Please, refer to SDN for upgrade instructions.
- Check that items and masters have valid templates assigned since items without templates are not supported in Sitecore V5.
- Check item names to match item naming rules for Sitecore V5. See Checking the result section below for more information.
- Backup the resulting masterdata.xml and masterindex.xml files.
Copying Site Content (database)
Please refer to the Data Migration Module documentation for details.
Checking the Result
Here come the points to keep in mind when reviewing the converted database:
-
Item Names
Item naming rules in Sitecore V5 are much stricter than those in Sitecore 4. For example, the following names are not valid in Sitecore V5:
- add-on modules (dash inside word)
- Sitecore A/S (invalid character / in name)
- Sample, Inc. (comma at the end of word, dot at the end of item name).
Conversion wizard will perform the following transformations on the names of items:
Strip out any characters that are listed in InvalidNameCharacters setting and add appropriate entries to log.
-
Layout groups
When converting layouts, wizard will perform the following steps:
- For each Sitecore 4 layout group (listed in /sitecore/system/layout groups) a device item will be created with the same ID as layout group item, name ‘Layout Group <GroupName>’ and query string lg=<layout-group-name-in-lowercase>
- Each item in /sitecore/layout, based on __layout group template, will be converted into a folder, containing the same items as in Sitecore 4.
- When filling in renderings field, wizard will detect complex layouts (based on __layout group template) and attach each sub-item to a corresponding device (as well as all renderings). If complex layout item has ‘blank is default’ field set, then the layout item which has empty ‘layout group’ field will be assigned to the ‘Default’ device.
-
WebControl renderings
Wizard will copy any WebControl rendering items in /sitecore/layout/renderings tree, but will not convert and namespace or assembly references in these items. There are two points to keep in mind when reviewing the database:
- Sitecore.WebControls namespace has been changed into Sitecore.Web.UI.Web.Controls namespace in Sitecore.Kernel.dll.
- Not all Sitecore 4 WebControls are implemented. See API reference documentation on SDN site for more information.
2. Migrating from Sitecore V5
Before beginning this or any Sitecore modification, be sure to make a full backup of your existing site. The backup should include both the web root files and Sitecore databases (backed up with appropriate database vendor provided tools).
Note: Proxies should be deactivated before transfering.
Copy any site specific files from the previous Sitecore installation web root into the new Sitecore web root. Site specific files are likely to exist in the following directories under the Sitecore web root.
The Sitecore web.root
This directory may contain site specific files. For example, the default.css file may have been extended for this site.
NOTE: The web.config file has most likely also contains site specific changes, but this file should NOT be copied to the new Sitecore 5.1 installation. Rather, the web.config changes should be MERGED into the Sitecore 5.1 installation (described below).
bin
This folder usually contains custom dlls. Do NOT copy all the files in this directory, only files that are site specific.
data
This folder contains the license.xml file.
layouts
This folder contains the site's presentation layer files, such as aspx, ascx, and related files.
upload
This folder contains the site's media library files.
xsl
This folder contains the site's XSLT renderings.
Install and use the Sitecore Data Migration module.
The migration process is now complete. We recommend that you perform a full test of your site.
Note:
- Please make sure that all code that references the Sitecore API is compatible with the current version of Sitecore. Some code may require to be recompiled.
- If you use some Sitecore modules, please make sure that you have the latest versions installed.
Prev