1.0 Introduction

1. The Lenel Import wizard does not support importing Mercury MP controllers, only EP and LP controllers (plus any additional downstream modules).
   
2. The Lenel Import wizard does not support Local Linkage actions as these are configured differently in a Lenel system.
   
3. The Doors.NET license must have Database Import Client enabled.
   
4. When using non-Keri OEM controllers or downstream modules, these will not be fully functional until they have been enabled on the Doors.NET license. 
   The license setting is Allow non-Keri Mercury Security Hardware.
   

2.0 Connect to Doors.NET Via the Import Wizard

1. On the Doors.NET host PC, navigate to the default directory: C:\Keri\Doors.NET
   
2. Locate the file named: ImportWizardLenel.
   
   
   
   
3. Double-click the file to open it.
   
4. The server IP address defaults to the localhost.
   
5. Enter the Doors.NET system admin user name and password.
   
6. Click the Connect button.
   
   
   

3.0 Select the Lenel SQL Database

1. You can also type in the SQL Server and Instance name in the drop down menu field if the SQL server hosting the Lenel database is not set to respond to discovery.
   
2. By default, the Lenel database is named AccessControl - this is what the Lenel database must be named otherwise it will not be possible to connect.
   

1. Select the SQL Server on the network which has the Lenel Database - or enter the SQL Server and instance name.
   
2. Leave the authentication method at Windows authentication.
   
3. Click the Connect button.
   

4.0 Select an Existing Gateway or Create a New One

1. Click Next and the Review tab will appear.
   

5.0 Review the Hardware to be Imported

1. The hardware tree is fully-functional - so you can expand the hardware properties and view properties and settings before the database is imported.
   
2. In the Lenel system, the default input designations for door contact and RTE is different to the default configuration in Doors.NET. The input wizard will retain the mapping of all inputs, outputs and readers so that no rewiring will be required in the field following the conversion.

Important Note: If Elevator Control is configured in the Lenel system, the wizard will look for multiple cab readers on the same controller.  That is not the recommended configuration for Elevator control and Doors.NET does not allow one controller to handle all the elevator cabs in a building.  Therefore, Elevator Control would need to be reconfigured and the wizard will not import any of the Elevator Access levels.

6.0 Select What to Import

The final tab allows you select exactly what you wish to import into Doors.NET

1. Default - The default selection is to import everything: Hardware, Cardholder, Credentials, Access Groups/levels, Schedules, Holidays and Card Formats. 
   
2. Second Option - Everything is important, like the default selection, but all imported cardholders are assigned the same access rights.
   
3. Third Option - Only imports the cardholders and all cardholders are assigned the same access rights.
   

Important Note: Additionally it is very important to select the correct database version for the existing Lenel system - as the cardholder and credential data varies between each version.

7.0 Additional Hardware Notes

1. The Lenel Panel Layout and Master Schedule are greyed out but shown - this is because the wizard is using exactly what is in the Lenel database for the hardware mapping.  Lenel assigns inputs functionality different for the DC, Rex, and strike outputs.  So to avoid any rewiring in the field, the Doors.NET configuration will match how the controller is wired and configured. 
   
2. In some cases the Lenel database may not include all the inputs and outputs that physically exist on the that are on the MR52, MR16in, etc. When this occurs the import wizard will add the missing ones so they will become available to use in Doors.NET.
   

8.0 Import the Lenel Database

1. On a large databases it can take a while for the import to complete. You will be prompted that you wish to proceed to the next type of data - this will allow you to review the imported hardware before importing all the cardholder data.
   
   
   
   

9.0 Mercury Controller Name Comparisons