Import Data

If you are only importing operators, follow the process described in Import Operators and Templates and Import Operator Teams instead.

Contact Honeywell Support to do either of the following:

  • Export from one instance to another instance of VoiceConsole.
  • Migrate to a VoiceConsole SaaS deployment from a VoiceConsole On Prem deployment.

Contact Honeywell Tech Support if you are importing from older versions of VoiceConsole.

You must have a license imported into VoiceConsole.

To import data:

  1. Under Administration, click Import Data.
    The Import Data page opens.
  2. Click Browse, and navigate to and select a file.
    The file you select must be a compressed (.zip) file containing data exported from VoiceConsole. The items imported vary.

    You cannot import data from a VoiceConsole version 5.5 or older into version 5.6.1. If you select one of these older versions, a banner with the following message appears: "File is not compatible with current version".

  3. Once you have selected a file, click Next.
  4. The next page shows the imported data and mappings. If an imported site does not exist in the current instance of VoiceConsole, you can select whether to create the site in this instance, import the data into another existing site, or choose not to import the site's data.
    Click Next.
  5. The next page shows the operator teams being imported for each site. Click Show Details to view which operator teams will be imported into that site. Click Show Operators to see the operators in each team.
  6. Click Import Data. You will be unable to interact with VoiceConsole while the import process runs. Click Cancel to cancel the import.

Import Notes

Item Precautions
System Configuration

Conflicting system properties data is overwritten by an import. If multiple import files contain system properties data, each import overwrites conflicting data in the database.

Devices

Once a device is imported to a new site and starts communicating with VoiceConsole, all the device properties are updated.

Previous values on the device are cleared.

Device Profiles

If a default profile exists in the target before importing devices, the default profile is not changed.

If a default profile does not exist in the target, the first imported default profile becomes the default profile in the target.

Task Packages

All tasks and task packages within the current site are included in the export file.

Users and Roles

While importing user data, if a default role is deleted on the new system, the users with that role are not imported.

When there are two exported files with two different users but with the same roles, only the first imported user is successfully imported.
Accessories Battery threshold: If you are importing battery data, any changes to threshold settings made in the previous install are not imported into the new system. This may cause differences in information between the previous instance and the new one.

Data Not Exported or Imported

Due to privacy concerns, the following information is not included in the export file. If it somehow is exported, the import process will block it from being imported:

  • TEMP_JWT_CLIENT_ID,
  • JWT_CLIENT_ID,
  • TEMP_JWT_CLIENT_SECRET,
  • JWT_CLIENT_SECRET,
  • "AUTH_API_KEY",
  • "opIntelApiCredentials",
  • "DIRSERV_Search_Password",
  • "SMTP_Password",
  • "Salted_PSK",
  • SALT_VALUE,
  • "LICENSING_CUSTOMER",
  • "LICENSING_CHANNEL_PARTNER",
  • "ACTIVE_CLOUD_SERVER_ID",
  • "VoiceConsoleUpdatesURL",
  • "SoftwareUpdateLastRun",
  • "SoftwareUpdateFrequency",
  • "DataAggregationFrequency",
  • "BatteryHealthJobLastCompleted",
  • "Backup_Dir",
  • "LOGGING_BASE_DIR",
  • "VOICE_CONSOLE_PORT",
  • "VOICE_CONSOLE_HOSTNAME",
  • "PUBLIC_KEY",
  • "FILE_BASE_DIR",
  • "APP_CLUSTERED",
  • "SSO_ENABLED",
  • "IS_NEXT_GEN",
  • "LICENSING_SERVER_TYPE",
  • "LICENSE_BASE_DIR",
  • "VOICE_CONSOLE_CLUSTER_SERVER",
  • "reportType.DefaultRenderFormat"