OEM Migration

Since 10.1 Patch 3, it is possible to restore KNM and aQrate databases in the MyQ installation, which allows migrating all data from a KNM or aQrate installation into the MyQ installation. Other directions of migration are not possible.

The same feature is implemented for Central Server.

Prerequisites

• Backup of a database from the current OEM installation, minimum version 8.2

• Installer of the MyQ Print Server (for multi-site installation, the installer of the MyQ Central Server)

• New MyQ license(s) of your choice to be activated in MyQ once the migration is complete

Contact MyQ Support for more information specific to the migration process of your installation.

Recommended steps

Before you begin, we recommend you read our Upgrading MyQ Guide.

General

• Use a backup created immediately before migration to achieve no data loss

• Once the migration process is complete, check the settings of the new MyQ installation – some settings that differ from the MyQ defaults are kept intact; see more information below in the Migration section

Multi-site installations

• Start with the Central Server migration and after the migration, insert the new MyQ license you prepared prior to the migration

• Keep in mind that once the Central Server is migrated, the license recalculations on connected Site servers may end unsuccessfully; this conflict should be resolved by migrating the Site servers as soon as possible

Licenses

Since MyQ and other brands have different licenses, the license is lost when the database is restored. A new MyQ license must be activated instead of the previous KNM/aQrate one.

Migrate to MyQ

Migration can be performed with the use of the standard Database Restore option in the Easy Config.

Data Migration

All data except some settings are migrated without any changes. Database restore runs as usual, after the restore is finished and all following database upgrades are completed, the corresponding settings are updated.

Settings Migration

Settings are migrated with some transformation due to differences in OEM brands.

User policies

Currently, KNM and aQrate have an extended list of default user policies compared to MyQ - one policy is replaced with several other extra policies, see screenshots. So during the migration to MyQ, extra policies are removed and respectively one missing policy is added with its default value selected. Other policies and their values are not changed during the migration.

Email templates

Email templates such as quota notification emails, scanning emails, users pin emails, etc., by default contain OEM brands. During migration all email templates are not changed, except brands are replaced with MyQ. So if there were custom email templates in KNM / aQrate, they are preserved on migration, only brands are switched.

By default all email templates do not differ between brands, the only exception is the email template of scan with attachment, which has a different body in MyQ and KNM / aQrate, see screenshots. Since we preserve custom templates on migration and we don’t reset email templates to their defaults, it is recommended that customers reset templates to their defaults using the “Revert values“ buttons in email templates settings and customize them after if needed.

SMTP sender email

Settings → Network → Outgoing SMTP Server → Sender email - by default, its value respectively is MyQ@MyQ.local or KNM@KNM.local or aQrate@aQrate.local. If the default value is recognized during the migration, then it's replaced with MyQ's default value. Otherwise, the value is not changed.

Site name (Central-Site environments)

Settings → Server Type → Site server → Site name - since 10.1 Patch 3 it may have the OEM brand name as its default value. In this case, it is replaced with MyQ during migration; otherwise, it's not changed.