Doors32 to Borealis White Glove Conversions by Keri

Doors32 to Borealis White Glove Conversions by Keri

1.0 Introduction

The following document explains the steps that need to be taken and information to be aware of when converting a Doors32 system to Borealis. Converting a multi-site installation to Borealis will allow for all sites to be combined under a single system allowing for much simplified system monitoring and management even when the sites are in different geographical regions.

The conversion program offers flexibility in terms of how the new system is configured in Borealis and you can also merge separate Doors32 installation if that is required.

Converting a Doors32 system will include all cardholders, credentials, PINs and other credential settings, assigned access rights and access rights configuration, holidays and time schedules settings, controllers, doors and controller and door settings (such as the door name, unlock time, auto-unlock time schedules and door contact settings).

Once the conversion is complete, no further configuration will be required (unless there are multiple sites) - see below for further instructions. Once the reader subscription has been paid and the controllers are online in Borealis you will be ready to start fully administering the system.

Keri's conversion team will require a copy of the Doors32 database and will walk you through all the steps that are required to get you up-and-running in Borealis. The PXL and Entraguard controllers, once programmed, work independently of the host PC so there will be very minimal downtime while the system is being upgraded.





2.0 General Notifications

  1. Doors32 systems must consist of PXL-500 controllers and Entraguard controllers. PXL-250 and PXL-510 (Alarm Panel) controllers are not supported in Doors.NET or Borealis.
  2. There are firmware requirements for using PXL and Entraguard controllers in Borealis - controllers using older firmware will require a physical chip upgrade.

    - PXL-500 controllers - v08.04.49 minimum/v08.06.09 is recommended
    - Entraguard Titanium -     v7.8.02 or greater
    - Entraguard Platinum - v9.2.02 or greater

    Note: There are older PCB revisions of Entraguard controller that do not support the plug-on LAN-520 module - these controllers can therefore not be used as primary controllers in Borealis. The new style PCBs are revision P/N: 05738-001 (this is printed on the PCB). The older style of Entraguard will not have the J7 LAN-connection port.



  3. Borealis does not support a Serial or Modem connection method. Communication to all primary controllers in Borealis is via Ethernet. Primary PXL-500 or Entraguard controllers will require a plug-on LAN-520-AESP module (the primary controller is addressed #1).
  4. For a single site, the imported access rights will be correctly assigned to the cardholders and the import will also include the reader and time schedule setup for the access rights.
  5. All events should be collected from the controllers using the Doors32 software as this event history will no longer be accessible following the import.
  6. Prior to the conversion, after purchasing and receiving a hub, the MAC address of the hub will need to be sent to the White Glove conversion team. Your new system will then be created and the hub will be claimed to the system.
  7. Each Borealis hub will support a maximum of 32 readers per hub. Additional readers will require additional hubs. If your system exceeds 32 doors please discuss this further with the conversion team as additional work will be required for recreating access rights.





3.0 Handling Multiple Sites

3.1 Borealis Setup Options

If there are multiple sites in Doors32 there are two options related to how the data is imported into Borealis:
  1. Each site in Doors32 can become an individual site in Borealis - The entire Doors32 database will be imported into a single Borealis system and the individual sites will be recreated in Borealis.
  2. Each site in Doors32 can become a separate system in Borealis - each system will have it's own database of hardware, cardholders, credentials, etc and each system will be administered completely independent of each other.


3.2 Access Rights for Multiple Sites

When importing multiple Doors32 sites into multiple Borealis sites, only the access rights for the first site will be recreated in Borealis... additional work is required to recreate the access rights for additional sites. If required, you will be guided and assisted as part of the White Glove Conversion procedure.


3.3 Importing Cardholders when using Multiple Sites

  1. The Doors32 to Borealis conversion allows you to import all cardholders that exist in the Doors32 database... or you can choose to only import cardholders for a specific site.
  2. Cardholders that are assigned 'Total Access', which spans across multiple sites, will only be imported once but following the conversion they will have multiple access rights assigned (Total for Site 1, Total for Site 2, etc).




4.0 Borealis PXL System Capacities

  1. Maximum number of readers per hub - 32 (this does not include a PXL 'Exit' reader) - where both readers on a PXL-500 control one door.
  2. Maximum number of credentials per system - 50,000
  3. Maximum number of credentials per hub - 10,000
  4. Maximum number of access rights - Unlimited
  5. Maximum number of access rights per cardholder (per site) - 1
  6. Maximum number of time schedules - 32
  7. Maximum number of time intervals per day - 4
  8. Maximum number of time intervals per week - 28
  9. Maximum number of holiday schedules - 3
  10. Maximum number of holiday days per schedule - 32
  11. Maximum number of holidays per interval - 3

5.0 Conversion Procedure Summary

The following steps summarize the procedure for converting a single-site Doors32 system to a single-site Borealis system. 
  1. Register and verify your new Borealis operator account.
  2. Setup an Organization and wait for the Organization to be approved. An Organization only needs to be created once. All new systems can then be assigned to the Organization.
  3. Upload the Doors32 database as a single zip file via the www.kerisys.com website. The upload location can be found here:

    https://kerisys.com/doors-net-to-borealis-database-upload

  4. When uploading the database you will need to enter Borealis-specific information, such as: Integrator Email, the name of the new Borealis system.
  5. You should also enter the Keri Systems purchase order number as this is important for tracking database conversions.
  6. Typically, the next step would be to purchase a Borealis hub - then connect the hub to an internet enabled-DHCP network that is NOT on the same physical network as the controllers.
  7. A new system and site will then be created by Keri's conversion team and the hub will be claimed to the site.
  8. The data will then be imported to Borealis using the data in the backup file.
  9. Keri Systems will then contact you to arrange a cut-off time and date. The Doors32 system will then be deactivated and system administration will then switch-over to Borealis.

    Note: Once a new Borealis system has been setup it will be within a 30-day Setup period. If items in the cart are not paid for within the 30 days then the system will be temporarily suspended. 

  10. The Borealis System Owner can then pay for the readers which are automatically added to the shopping cart. The quickest and easiest method is to process the payment using a credit card.
  11. Once the subscription is paid the system status will be fully active.


6.0 Contact Information

To further discuss upgrading a Doors32 system to Borealis contact Keri's sales team:
  1.   (001) 408-435-8400

    • Related Articles

    • Doors.NET to Borealis Database Conversion Procedure

      1.0 Introduction Keri Systems White Glove Conversion procedure will handle the importing of the access control system data - this includes all cardholder and credential information - including multiple credentials, plus controller and reader ...

    • Getting Started with Borealis

      1.0 Introduction This document guides you through getting started with Borealis and setting up your new system. It assumes that you have purchased a communication hub and controllers and this is the first time using Borealis. Conversions From ...

    • Borealis Troubleshooting Guide

      1.0 Borealis System Troubleshooting Cannot view the System - This is most likely caused by the registered account not being added as a system operator. Once an e-mail has been registered and verified, that e-mail address should then be added as a new ...

    • Borealis FAQs

      1.0 General Borealis Questions What is Borealis? Borealis is Keri Systems’ cloud-based access control system. Borealis gives you complete visibility and control of your system from any computer, tablet or mobile device that has a web browser and an ...

    • Borealis Overview

      1.0 Introduction The new Borealis Cloud user interface is a completely new and re-designed front end for Borealis. It is extremely easy to learn and operate and allows you to quickly and easily find all your access control data - all in one place. ...