Pilot upgrade

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 Enterprise 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 most recent data looks in your new environment. You can repeat this step as many times as you need.

This step does not import any configuration information, only data records. If you have made any configuration changes to your existing production system after creating the pilot database, they will not be reflected.

Switch to Production

Once you have a fully configured and tested pilot database and are ready to begin the production use of Alloy Navigator Enterprise, 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 again, now for the last time. When the resync finishes, your original production database will be taken offline, renamed, then the new database will take the name of the original database.