Overview of steps

1 Two to four weeks before the date you plan to implement the new release in your production environment, contact aPriori Customer Support (support@apriori.com) to inform them that you would like them to complete the migration. This allows time for testing and potential debugging.

2 Export a copy of your production database and send it to aPriori. Starting now, until the production migration, please limit making any system-wide changes such as to variables or users.

When you move to production you can easily update the migrated database with any cost estimates (scenarios) that have changed since the copy was made, but there is no easy way to update other types of data. If you must make these types of changes, please document what has been done so they can be done again in the updated database.

3 aPriori:

• migrate the data and test against the new version.

• assess configured VPE changes and scope amount of work required (if any).

• provide a time frame for any VPE reconfiguration to be done (if necessary).

• send the migrated database back to you.

4 (Highly recommended) Install the new release in a staging environment and conduct independent testing of custom VPEs as well as of general compatibility with your systems, hardware, CAD environment, etc.

5 (Optional) Meet with aPriori Support to answer any questions about how to move from staging to production.

6 Move from the tested, staging environment to production:

• Disable access to the older, production database.

• Use the aPriori client software to export any data from the older production database that has changed since the database was exported.

• Import the migrated database to the new production database schema

• Use the aPriori client software to import into the new database the changed data that you exported above.

• Install the new client software and connect to the migrated database