Pilot System Scenario for Database Migration from Alloy Navigator 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.

IMPORTANT: We also highly recommend that you leverage our Professional Services team who can help you plan the upgrade and migrate your data and business logic to the new platform.

INFO: You can contact Alloy Professional Services team at support@alloysoftware.com.

Database Migration for Alloy Navigator

The Pilot System scenario includes three steps: Create Pilot Database, Update Pilot Data, and Move to Production.

IMPORTANT: Alloy Navigator Express and Alloy Navigator Enterprise of the same major version are incompatible and should be installed on separate locations. If you are migrating from Alloy Navigator Express, we recommend that you use a separate computer or a virtual machine for testing and upgrading the Alloy Navigator8 pilot database.

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 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 does not affect the configuration.

Move to Production

Once you have a fully configured and tested pilot database and are ready to begin the production use of Alloy Navigator8, 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 configuration information, only data records, so configuration changes made to your current Alloy Navigator production system after creating the pilot database will not be reflected.

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