What Can Be Migrated? :: SAS(R) 9.3 Intelligence Platform: Migration Guide

The SAS automated migration tools migrate the following content and configuration from an earlier SAS version that reside under the SAS configuration directory (for example, /SAS/Config/Lev1):

content stored in metadata

(such as libraries, reports, jobs, information maps, data explorations, and so on)
content in the WebDAV repository

(such as report definitions and documents)
configuration stored in metadata

(such as for servers, users, groups, ACTs, and so on)
certain server configuration files

(such as adminusers.txt and trustedusers.txt)
Web application configuration

(such as deployment properties and configuration files)

The SAS automated migration tools do not migrate the following SAS content and configuration:

tables (outside of the configuration directory)
deployed jobs (outside of the configuration directory)
stored processes (outside of the configuration directory)

For more information, see Migrating Content Stored outside the SAS Configuration Directory.
certain SAS Application Server configuration files

autoexec files (appserver_autoexec.sas) and sasv9.cfg files are not migrated. For more information, see Update SAS Server Configuration Files.
SAS middle-tier configuration information

For more information, see Review the SAS Middle-Tier Configuration.
custom portlet code

For more information, see Developing Portlets for the SAS Information Delivery Portal 4.2, available at http://support.sas.com/documentation/cdl/en/prtltidpdg/61650/PDF/default/prtltidpdg.pdf.
custom metadata

A custom metadata definition is a metadata definition that you create using the SAS Open Metadata Interface, SAS Java Metadata Interface, or SAS metadata DATA step functions. (Custom metadata is not created when using SAS Management Console wizards and wizards provided by other SAS platform products and solutions.)