# Migrating ADS Based Data To New System

With the introduction of the new database engine, it will be required to migrate already existing data from an ADS based system to the new database.

The migration process looks (in short) like this:

1. First update your system to the latest available version of the still ADS based ZeeBORN software system. This will prepare your existing system for the migration to the new database engine.
2. Install the new database engine on a selected server. This can be the same server where the ADS is installed but can also be installed on a different system.
3. Install the new ZeeBORN software to the new database server (ServerSetup.exe).
4. Install the separate migration package available from ZeeBORN support.
5. Run the migration tool for copying the data from the ADS database to the new database.
6. Run the ServerSetup.exe again in Repair mode for checking the database for potential problems.
7. Install client software (ClientSetup.exe).
8. Start using the migrated database.

# Planning

As the migration can be quite time consuming, the following should be considered for planning the optimal time for doing the migration:

1. The migration can be executed site by site (vessel by vessel). There is no need to migrate the office and all connected sites/vessels at the same time. We recommend starting in the office first and continue migrating connected sites whenever suitable. Data replication between office and sites works identical to older versions and automatically adapts to the existing software versions.
2. If you use automatic data transfer tools in the ADS version, make sure to disable automatic transfer for sites/vessels that have been already migrated to the new database.
3. We still recommend to plan a time frame of only 1 to 2 months for finalizing the migration of all sites, as future feature updates can be rolled out only after complete migration of all involved sites.
4. You might also consider a test run for the migration, where the full migration process will be executed in parallel to the existing system. This gives you the option for testing the new version and database engine without any impact on your productive work. As soon as the test results of the test run satisfy your requirements, the migration can be executed again with recent changes and new data from the current production system.

# Duration To Be Considered

• Installation of the database engine: 5 minutes
• Installation of the migration package: 5 minutes
• Migration of the database: up to 4 hours (depending on number of vessels/sites managed in the system)
• Client installation: 1 minute per client, if done manually

# Consideration for a Site Migration

1. After starting the migration (running the migration tool), no new data should be added to the old system and no existing data should be modified. All data changed or added after starting the migration won't be available in the new database. While the migration is ongoing, users still can access the old system for retrieving information, creating reports or doing any other activity that doesn't change the content of the database.
2. There is no global read-only switch in the old system that would prevent any unwanted modification after migration start. It should be considered to remove all related user rights after migration start.
3. After successful database migration, the client software should be rolled out as soon as possible.

# Database Engine Installation

It's not necessary to install the new database on the same server where the previous ADS based version is already installed. While having both databases on the same server would have the benefit that migration processes would run faster, the introduction of the new database engine might also be a good point in time considering new or upgraded hardware for a new database server.

More details about the installation of the database engine can be found at Database Engine Installation.

# Installing the Server Software

After the installation of the database engine, the preparation of the server can continue. With the Server Installation tool (see Server Installation).

# Migration Package Installation

After obtaining the migration package from ZeeBORN support, install the package on the same server where the new database engine is installed. As the migration tool needs access to the old database, please make sure that the server with the old database and the related network share can be accessed by the migration package. If the new database server and the old database server are located in different networks, please contact ZeeBORN support for assistance.

# Running the Migration Tool

If the new database and old database are located on different servers, the tool will first ask for the network share name to be used for accessing the old database. Next the main database will be migrated by clicking the Migrate DB button. Depending on the size of the database and the available network speed, this process can take up to several hours. A migration log is created in real-time and provides an insight into the migration process.

# Check of Migrated Data

For checking the migrated data for potential problems, run the Server Installation tool again in Repair mode. All migrated data will be upgraded to the latest database table structures and the newest client software version will be made available on the server.

The upgrading of the table structures from the data copied with the migration tool to the table structures required by the new software version can also take up to 20 minutes.

# Client Software Installation

For users having administrative rights on their PC (at least having the right for installing new software), ZeeBORN provides a pre-configured installation package that already includes the necessary settings for connecting to the new database server (see also Using ClientConnect Tool). For users without administrative rights, ZeeBORN provides another solution that allows a self-service install and update of the client software even without the necessary administrative rights. As this might be not compliant with company IT's policy, please contact support for more details.

# Running Old and New Version in Parallel

If the client software for the new system is installed on a PC where the ADS based client software is already installed, the ZeeBORN icon on the desktop will be replaced with a version to the new software version. An additional "ZeeBORN ADS" icon will be created, that still gives access to the old version.