Upgrade From v3 To v5+

Please note: this is legacy documentation. Please check out https://docs.miarec.com/all/ for the most up-to-date documentation and user guides. 


Upgrade from MiaRec version 3.x consists of the following steps:

  1. Backup recordings on version 3.x

  2. [Optional] Stop all MiaRec services and backup full directory C:\Program Files\MiaRec Business

  3. Uninstall version 3.x

  4. Install MiaRec version 5.x

  5. Import recordings from backup

  6. Create users/groups/roles

  7. Assign previously recorded calls to users

Supported data migration during upgrade

During the upgrade the following data will be migrated from the old version to the new one:

  • Call recordings

  • Folders (they will be migrated to "categories").

Non-supported data migration during upgrade

Data, which is not migrated from the old version to the new one:

  • Users configuration. Due to significant changes in users' access right system, the user accounts are not migrated from the old version. It is necessary to re-create users manually in the new version.

  • Auto-sort into folders rules. We are working on similar functionality for auto categorizing calls. But, probably, you do not need such auto-sorting anymore. In the old version, the folders were used primarily for grouping calls by users. Our customers created a dedicated folder for each user. In the new version, this is not necessary anymore because MiaRec automatically sorts calls by users and provides search "by user" capability out-of-box.

Incompatibilities Between v.5 And v.3

The new version of MiaRec includes a lot of new features and improvements in usability and user experience. Below we will list only significant incompatibilities between new and old versions:

  • New role-based permission system (more intuitive and flexible)

  • "Folders" were replaced with more flexible "Categories" (one call may be marked with multiple categories simultaneously).

  • "Recording rules" are configured on a per-user basis. Previously the recording rules were configured separately from the user's configuration.