Critical Information - Do Not Skip This Part
This page covers the 3 different articles to migrate Chronicall to a new server from an old server, or from one drive to another drive (C:/ to D:/ for example).
- Running the backup and migration may cause significant downtime for Chronicall. It is highly recommended to run it after hours.
- NOTE: For Multimedia or Contact Center, you want to ensure you have an IP Office Failover, so if your call routing is not back up before you open, you can still route calls through traditional Hunt Groups.
- NOTE: Please verify that your exact version of Chronicall is available on our website, by visiting our downloads page
- If the versions do not match, please update Chronicall to a current version on the current server before migrating to a new server so versions match
- I.e. If you are on version 4.4.3 on your server but see 4.4.4 on the website, update your old server to 4.4.4 before migrating to the fresh 4.4.4 install
- If the versions do not match, please update Chronicall to a current version on the current server before migrating to a new server so versions match
- It is essential to make sure the new and old server Chronicall versions match for the database migration to succeed.
- To verify your current version, go to Help -> About Chronicall on the main Chronicall screen.