Migrate Custom System Data

QAD 2017 Enterprise Edition > Installation-Conversion > Conversion Guide > Upgrading QAD Enterprise Edition into a New Environment > Upgrading Enterprise Edition into a New Environment > Migrate Custom System Data

Upgrading does not convert or upgrade custom data changes, but the upgrade process does delete all records from a number of tables, defined in inpempty.lst. QAD-owned system data is subsequently reloaded during the upgrade, but custom data is not.

If you added custom data to any of the following default system data tables, you must dump the customized records before beginning an upgrade. If you have not made any customizations, skip this section.

• Custom menus (mnd_det, mnt_det) and messages (msg_mstr)

Note: You must reassign Roles after loading the custom menus. See the QAD Security Administration Guide for information on defining Role membership.

• Custom labels (lbl_mstr, lbld_det)

• Custom language detail (lng_det)

• Custom field help lookup (flhd_det, flhm_mstr)

• Custom reports, browses (use the import/export function in report resource export and browse maintenance), and favorites used in the QAD .NET UI (collections and metrics stored in Tomcat under storage directory in qadhome)

Note: Table names are for information purposes only. The list of tables may be incomplete and is subject to change.

After dumping your custom data and completing the upgrade, incorporate your customizations in your target version environment. For more information, see the QAD 2017 EE Configuration and Administration Guide.