Planning an Upgrade to Siebel 7 > Planning an Upgrade >

Identifying Data Migration Tasks

After completing a development environment upgrade, review each of the following types of data or files and identify changes that you must migrate to the test or production environment. Although this is essentially a data migration task, it should be considered part of the upgrade process.

NOTE:  If you are upgrading from Release 5.x or 6.x, you must modify your existing data migration processes to include any new objects introduced in Release 7.x.

• Siebel Repository File (SRF). Copy the SRF from the development environment to the correct location in the test or production environment. See Configuration Guidelines on the Siebel Bookshelf for detailed information.
• Web Templates and related files. Migrate modified Web templates and related files, such as images, to the appropriate location in the test or production environment. See Configuration Guidelines for detailed information.
• Reports. Migrate .ROX files and associated .txt files that contain language-specific static strings in reports to the target environment. The Reports Server uses the .ROX files to generate reports and pulls static strings from the associated .txt files. See Siebel Reports Administration Guide for more detailed information about migrating .ROX and associated .txt files.
• Lists of Values (LOVs). If you added LOVs or LOV types to the development environment, you must also add them to the production environment. Use the LOV Administration view to manually add these to the production environment. For new LOV types with many values, use EIM to do an automated batch upload. See Applications Administration Guide for detailed information
• New Responsibilities and Views. Any new views and responsibilities you have added in your development environment must be also registered in the test or production environment and associated with employees. This is an administrative function and as such is generally added manually in the production environment using the Responsibility Administration view. For a large number of new responsibilities, responsibilities that have large number of existing employee associations, and so on, using EIM is also an option. See Applications Administration Guide for detailed information.
• Workflow Processes. Use the XML based Export and Import utility available from a button in the Workflow Process Administration view. See Siebel Business Process Designer Administration Guide for detailed information.
• Workflow Policies. Depending on the number and complexity of Workflow Policies, they can be entered manually using the Workflow Policy Administration view or using EIM (EIM_WFM_ tables). See Siebel Business Process Designer Administration Guide for detailed information.
• Assignment Rules. If you have new assignment rules you can add them manually using the Assignment Rule Administration view or using EIM depending on the number and complexity of the rules. See Siebel Assignment Manager Administration Guide for detailed information.
• Product Configurator Rules. Use the Export/Import functionality provided by Siebel Product Configurator to export from test and import into production. See Product Administration Guide for detailed information.
• Smart Scripts. Use Export/Import functionality provided by Siebel SmartScripts to export from test and import into production. See Siebel SmartScript Administration Guide for detailed information.
• Client Side Business Services. Client side business services can be migrated using Export/Import functionality from the Siebel Client Business Services Administration view. See Siebel Tools Reference for detailed information.

  NOTE:  No additional import is required for Tools Business Services, because they are part of the Siebel Repository File and will migrate as part of the repository migration process.

• State Model. After testing, you must manually create the state model in the production environment. Be sure that the end date is set to a prior date until the state model is entered in its entirety. See Siebel Business Process Designer Administration Guide for detailed information.
• Pre-defined queries (PDQ). Creating new pre-defined queries is considered a administrative function and as such is generally added manually in the production environment. Users add predefined queries as needed, but administrators may enter complex PDQs using the PDQ Administration view. EIM can also be used for bulk load of tested PDQs from test to production. See Applications Administration Guide for detailed information.

Migrating Data

To migrate files and data from one environment to another, use one of the following utilities, as appropriate for the type of data you are migrating.

• Repository Migration. See Siebel Tools Reference for detailed information.
• EIM. See Siebel Enterprise Integration Manager Administration Guide for detailed information.
• Export/Import. See the relevant guide on the Siebel Bookshelf for the type of data you are migrating for information about utilities provided as standard functionality in modules such as Business Process Designer, Product Configurator, and SmartScripts.
• Development to Production. Also see Developing and Deploying Siebel eBusiness Applications for information about migrating data from a development environment to a test or production environment.