This document assumes migration from DLXS 12/12a to DLXS 13.
Read the DLXS, Getting Started documentation, and this document, completely, before proceeding. You might also want to skim the Release Notes.
Image Class requires, as of release 13, that there be an ImageClassMediaFiles table. This table is created automatically at installation, but your collections will not work with DLXS 13 until the table has been populated. Please read migration section of Image Class Media Loading for Online Delivery for details.
If you have customized the user interface using XML/XSL or Perl in previous DLXS versions, it is strongly recommended that you first get your existing collections basically up and running with the default interface before attempting to migrate XML/XSL or Perl customizations from DLXS 12/12a to DLXS 13. Once you have done this, evaluate each customization situation and decide how best to migrate the changes. Ideally, you will simply copy your files over to the new version and be done with it. However, consider the possibility that a) your customizations or similar are already included in DLXS 13, b) changes in DLXS 13 will force modifications to your customizations. As a general principle, you want to avoid unncecessary duplication of code. For example, an XSL customization that requires a change to just one template does not generally require the entire stylesheet to be duplicated.
See DLXS User Interface documentation for details.