Database Migration for Alloy Navigator Express Express

The new version includes new features and a greatly improved workflow and business logic. Some of the new features rely on new workflow, so we highly recommend that you use a Pilot System scenario for data migration. This enables you to review and adjust test new configuration settings in a pilot environment, then switch over to production when you are ready.

The recommended Pilot System scenario for an Alloy Navigator Express database includes three steps: Create Pilot Database, Update Pilot Data, and Move to Production.

Create Pilot Database

The first step imports all your data (i.e. the configuration information and data records) from the production database to a new Alloy Navigator Express 8 database. After that you use that new database as a pilot database for configuring and initial testing while still using your existing system in production.

Update Pilot Data

This step is optional. During configuring and testing you may want to update your pilot data with the latest data records from your production database. This will show how your fresh data looks in your new environment. You can repeat this step as many times as you need.

Updating pilot data does not affect the Alloy Navigator Express configuration. However, any changes made to the Network Inventory configuration in the pilot database will be discarded.

Move to Production

Once you have a fully configured and tested pilot database and are ready to begin the production use of Alloy Navigator Express Express8, take the final step. It will replace all data records (such as Tickets, Knowledge Base Articles, Computers, etc.) in the pilot database with your latest production data one last time again.

The "Move to Production" step does not import any Alloy Navigator Express Express configuration information, only data records, so configuration changes made to your current Alloy NavigatorExpress production system after creating the pilot database will not be reflected.

For the Network Inventory module, this step imports both configuration information and data records again, so any changes made to the Network Inventory configuration in the pilot database will be discarded. You will have to re-apply them in the production database, if needed.

When the migration finishes, the old database will be taken offline, renamed, then the new database will take the name of the original database.

FOR VERSION 7.2 OR LATER: The final step also turns on the Automatic Upgrade feature, which helps distribute client components of the Alloy Navigator ExpressExpress8 among your technicians.