Preparation

You should not attempt to migrate any of your publications before you have:

• A functioning Content Engine 5.2.7.2 installation to which publications can be migrated.

• Sufficient staff (both technical and editorial) who are familiar with the new version of the software and are capable of maintaining the migrated publication.

• A plan for carrying out the migration.

• A 4.x host available for export purposes. This host must not be a host that you use for editorial or presentation purposes, as you will need to reconfigure the search engine in a way that will degrade search performance for users.

• Sufficient spare disk capacity for handling the export/import data. Copies of all images and multimedia files are created during export, and this will most likely account for the majority of your space requirements. In addition, you will need some additional space for the XML syndication files generated during export, but this is likely to form a relatively small proportion of the total. The syndication files exported from our test database consisting of around 300,000 articles require 6.5Gb of space, but the space required for associated images and multimedia files is far greater. It is probably a good idea to mount a network storage device with sufficient storage on both your import and export hosts: this will also simplify transferring data between the machines.

Once these prerequisites are met, you should install the Migrator plug-in on the version 4.x host you have designated as your export host. For detailed instructions on how to install and use this plug-in, see the Escenic Content Engine Migrator Plug-in Guide.