Importing Keys
Follow these steps to import multiple keys into LivionKey Register using a CSV file:
Download the import keys template
Navigate to the "Keys" -page
From the "Actions" dropdown menu (3 dots in top-right of the page), select "Import Keys"
Click "DOWNLOAD TEMPLATE" to get the CSV file. Save the file to your computer.
Fill in the Template
Open the CSV-file on your computer and fill in the key information. Do not modify the column headers!
Required fields:
Building ID or Customer ID (must match an existing building or customer)
Customer KeyID (a unique identifier to prevent duplicates)
Selected storage ("manualStorage" or "device")
Conditional fields:
Description: Required if "Selected storage" is "manualStorage.", provide details about the storage location.
LivionKey Automat ID: Required if "Selected storage" is "device.", the imported keys will be assigned to this automat.
Contract-related columns (optional): If filled, the key will be marked as handed over upon import.
Start date
End date
Contact Name
Company
Phone number (mobile)
Fixed phone number
Email
Send email (enter "YES" to enable notifications)
Send SMS (enter "YES" to enable notifications)
Language (fi-fi / en-gb / sv-se / de-de)
Verification
How to Format Multiple Contacts in Import
Use the standard contact columns from the Livion key import template and place multiple values in the same cell, separated by commas.
Standard Contact Columns
Contact nameEmailPhone numberFixed phone numberCompanyLanguage (fi-fi / en-gb / sv-se / de-de)
Example
Column | Example value |
|
|
| |
|
|
|
|
|
|
Contact Ordering Rules
The first value in each contact column is used for the primary contact.
Later values are used for additional contacts.
Additional contacts are only created if they have a name.
If an additional contact does not have a language value, Livion falls back to the primary contact's language.
Contact Custom Fields in Import
If your organization uses contact custom fields, the key import template can include those fields, too.
Use the custom-field columns from the downloaded Livion template.
If one row contains multiple contacts, enter the custom-field values in the same order as the contact names.
Separate multiple values with commas, just like the standard contact columns.
Example
Column | Example value |
|
|
|
|
|
|
Save Contact During Import
Use the Save Contact Column: When importing contract contacts, they should also be created in the contact register.
If
Save Contactis set on a row, Livion tries to save the main contact and all additional contacts from that row.Saved contacts include imported basic data and imported custom-field values.
If contact saving fails for a single contact, the key import can still succeed.
Note!
To find the building's ID or Customer's Own ID:
Click "Buildings" on the left menu.
Search the building from the view and double-click it.
The ID and Customer ID will be displayed on the right side of the view.
Save the file in CSV format, using a comma (,) or semicolon (;) as the separator.
Important!
Pay attention to save the file in the correct format. The file format/encoding should be 65001: Unicode (UTF-8)!
Import the File
Click the "UPLOAD FILE" button and select the modified CSV file from your computer's folder. After that, press "VALIDATE".
Confirm the imported keys by clicking "IMPORT".
Once the keys are imported, the system shows a summary of the import.
Grouping multiple Keys into a single Contract:
Keys with identical contact information in the CSV will be grouped into one contract.
If the key holder is unknown, use "Unknown" in the Contact Name field and leave other fields empty.
To avoid a single contract for multiple unknown keys, use unique identifiers like "Unknown 1," "Unknown 2," et.c
Key imports are processed per file. New keys won't be added to existing contracts, even if the contract data matches.
Future contracts and verification
It is now possible to import keys scheduled for future handover.
You can also enable contract verification for such contracts by adding an X in the verification column.
Validation Guidelines:
Column headers must match the template
Each CSV file can contain a maximum of 1500 keys
Required fields: Building ID or Customer ID, Customer KeyID, and Selected storage
If contract-related columns are used:
- Contact Name is required
- Start and end dates must be in yyyy-mm-dd format
- Phone number must be in international format (e.g., +358401234567)
- Email format will be checked
- Customer KeyID must be unique