/
Legacy Version Migration (Older CostOS Versions)

Legacy Version Migration (Older CostOS Versions)

Appendix A – Legacy Version Migration (Older CostOS Versions)

This section applies to older versions of CostOS that use legacy deployment structures or directory-based configurations.
If you experience issues related to concurrent licenses during migration, please raise a support ticket or email the CostOS Support Team for assistance.

A.1 Backup and Preparation

To migrate an older CostOS instance to a new server or location, follow the steps below:

  1. Create a Full Database Backup

    • Use Microsoft SQL Server Management Studio (SSMS) or T-SQL to create a backup of your existing CostOS databases (Master and Project).

    • Store the .bak files in a secure location.

    BACKUP DATABASE [CostOS_Master] TO DISK = 'D:\Backups\CostOS_Master.bak'; BACKUP DATABASE [CostOS_Project] TO DISK = 'D:\Backups\CostOS_Project.bak';

  2. Back Up the Application Installation and Home Directory

    • Create a copy of your current CostOS installation directory and home directory.

    • These contain configurations, license files, and custom resources that must be preserved.

  3. Note the Application Version

    • Ensure the new installation uses the exact same version of CostOS as the old server.

    • Using a different version may cause compatibility or schema issues.

A.2 Installing CostOS Server on the New System

  1. Obtain the Installation Media

    • Download the CostOS Server installer matching your current version.

    • Use the installation package provided by CostOS or your IT administrator.

  2. Install CostOS Server

    • Run the installer on the new server or environment.

    • If the databases have already been restored, configure the installer to point to the existing CostOS database during setup.

    • Do not start the CostOS Server yet.

A.3 Migrating Customization and Configuration Files

After installation, copy the following directories and configuration files from your old CostOS server to the new one.
These ensure that your customizations, templates, and settings are preserved.

Source Directory

Target Directory

Notes

Source Directory

Target Directory

Notes

<old-installation>\ces\apps\ces.ear\ces\db_icons

<new-installation>\ces\apps\ces.ear\ces\db_icons

Copy only if folder exists

<old-installation>\ces\apps\ces.ear\ces\db_images

<new-installation>\ces\apps\ces.ear\ces\db_images

Copy only if folder exists

<old-installation>\ces\apps\ces.ear\ces\db_jrxml

<new-installation>\ces\apps\ces.ear\ces\db_jrxml

Copy only if folder exists

<old-installation>\ces\apps\ces.ear\ces.sar\zdb.properties

<new-installation>\ces\apps\ces.ear\ces.sar\zdb.properties

Mandatory – configuration file required for database access

⚠️ Important:
The file zdb.properties is mandatory. It defines database connection parameters.
Without it, the new CostOS Server will not be able to connect to the database.

A.4 Starting the Application

Once the file transfer is complete:

  1. Start the CostOS Server service on the new machine.

  2. Verify successful startup in the server logs.

  3. Open the application and confirm that all projects, settings, and configurations load correctly.

A.5 CostOS Workstation Migration

If you are also migrating CostOS Workstation instances, follow these steps depending on your license type:

Named License Users

  1. Deactivate the existing license before migration.

  2. Install and activate it again on the new instance.

  3. You can perform this reactivation up to three (3) times.

Concurrent License Users

  1. Import your existing license file into the new installation.

  2. If the concurrent license fails to activate or validate, contact CostOS Support for assistance.

A.6 Validation and Support

After completing the migration:

  • Log in to verify that both the Master and Project databases are accessible.

  • Test project creation, saving, and report generation.

  • If you encounter issues with:

    • License validation

    • Missing resources

    • Database connectivity
      Please raise a support ticket or email support@costos.example.com (replace with your real support address).

A.7 Summary of Legacy Migration Process

Step

Description

Notes

Step

Description

Notes

1

Back up Master & Project databases

.bak files

2

Back up old installation & home directory

All custom folders

3

Install same CostOS version on new server

Use vendor-provided installer

4

Copy custom folders (db_icons, db_images, db_jrxml)

Optional but recommended

5

Copy zdb.properties

Mandatory

6

Start CostOS Server

Verify connectivity

7

Re-activate licenses

Named or concurrent