Doors.NET to Borealis Database Conversion Procedure

Doors.NET to Borealis Database Conversion Procedure


1.0 Introduction

Keri Systems White Glove Conversion procedure will handle the complete conversion of your Doors.NET database to Borealis.



The White Glove Conversion procedure will be completed entirely by Keri Systems conversion experts so you will not have to worry about a thing. The conversion will copy across cardholders, credentials (including multiple credentials), controllers and door settings, time schedules and holidays. In addition, v3.0.4.0 also supports the importing of access group names and access rights assignment to cardholders).

Keri Systems will pre-configure your Borealis conversion – this will include pre-checks and configuring your system & sites. Keri Systems will also configure operators and claim communication hubs on your behalf. We will then complete the conversion and move your existing data to your new Borealis cloud solution.


Important Notes:
- Importing access group/access rights information is not supported if any cardholders in the Doors.NET system has more than one access group assigned.
- The Doors.NET to Borealis conversion supports NXT, NXT-MSC and PXL-500 controller types are supported.  True Mercury hardware support will be included in the future.
- If you are importing Keri NXT controllers, all controllers must be programmed with an IP address and if the controllers were manually added to Doors.NET they must also have the correct MAC address.
- Once the conversion is completed, NXT-MSC controllers will require a memory reset. Standard Keri NXT controllers will also require a Basic reset. Controller resets are performed from the controller screen in Borealis.
- Following the successful conversion, the controllers will not be fully functional until your Borealis cloud subscription payment has been processed.
- If your system uses Dual Verification/Card + PIN, PINS will not be included if there are duplicate PINs in Doors.NET. The conversion tool will only import unique PINs.


2.0 Why Move Your Access Control System to the Cloud?

  • No Software Required
  • Browser-Based
  • Remotely Accessible
  • Mobile & Tablet Ready
  • All-in-one dashboard
  • Real-Time Reporting
  • Hosted In The Cloud
  • Eliminate Local Servers
  • Automatic Disaster Recovery and Backups Built-in
  • Infinitely Scalable Solution


3.0 Pre-Configuration Requirements

  1. Register a new Borealis account.
  2. Create a new system  - (You will need to contact Keri Systems for this step).
  3. Create a new site.
  4. Add a hub to the site  - When you add a new hub, ensure the site has the correct controller type that is currently being used in the existing Doors.NET system (Keri NXT, NXT-MSC and Mercury or PXL controllers).
  5. Doors.NET Software  - Should be updated to the most current version and all controllers should be updated to the latest firmware version (included with Doors.NET). 


4.0 Using Multiple Hubs

The conversion tool supports the use of multiple hubs. Multiple hubs are used in the following circumstances:
  1. If controllers are located in different geographical time zones.
  2. If controllers are on different subnets.
  3. If you are using a mixture of different controller types.
  4. If you have more than 32 doors on your site.  


5.0 Contact Keri Systems for Further Information

- Request further information via the White Glove Conversion Inquiry Form. Enter your e-mail address and additional information will be sent to you.




              
PN 02411-001 Rev B

    • Related Articles

    • Doors32 to Doors.NET Database Conversion Procedure

      1.0 Introduction This document provides basic information regarding the process for converting a Doors32 database/system for use in a Doors.NET access control system. It is intended to ensure that you (the customer) understand the steps you need to ...

    • Doors32 to Doors.NET Database Conversion Agreement

      Doors32 to Doors.NET Database Conversion Agreement - standalone document

    • Doors32 - Doors.NET Database Conversion FAQs

      Doors32 Database Conversion FAQs  Keri’s Doors.NET software, originally designed for our NXT hardware platform, now also supports PXL-500 and Entraguard (requires version 3.5.1.20 or higher), providing customers currently using Doors32 more ...

    • Restore the Doors.NET Database

      Instructions for Restoring the Doors.NET SQL Database Notes: - performing this task will completely overwrite ALL data in the existing Doors.Net database. - this backup procedure pertains to Doors.Net databases using Microsoft SQL Server 2016 ...

    • Backup the Doors.NET Database

      This procedure describes a backup process for Doors.NET databases using Microsoft SQL Studio Manager 2019, however, the procedure is almost identical to other versions of SQL Studio Manager. Note: These instructions specifically cover a Disc backup; ...