Importing Keys
Follow these steps to import multiple keys into LivionKey Register using an Excel (XLSX) or 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 template (an Excel .xlsx file). Save the file to your computer.
Fill in the Template
Open the template 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). You can leave it empty: a key ID is then generated automatically.
Selected storage ("manualStorage" or "device")
Conditional fields:
Description: Optional. If "Selected storage" is "manualStorage", describe where the key is kept.
LivionKey Automat ID: Required if "Selected storage" is "device.", the imported keys will be assigned to this automat.
Contract-related columns (optional): If any of these is filled, a contract is created for the key. The key is marked as handed over only if you enter "x" in the handed over column.
handed over (enter "x" if the key has already been handed over to the contact)
Start date
End date
Contact Name
Company
Phone number (mobile)
Fixed phone number
Email
Send email (enter "x" to enable notifications)
Send SMS (enter "x" to enable notifications)
Language (fi-fi / en-gb / sv-se / de-de)
Verification
Signature (filename of the contact's signature image, see Importing already signed contracts below)
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 Excel (XLSX) or CSV format. Only the first sheet of an Excel file is read. In a CSV file, use 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)!
Importing already signed contracts
If the contact has already signed the handover on paper or in another system, you can import the signature with the key. The contract is then created as signed and does not wait for a signature.
Add a
Signaturecolumn to your file if your template does not have one. Write the header exactly asSignature.On each signed row, enter the filename of the signature image, for example
signature-001.png. The filename must end with .png, .jpg or .jpeg.A row with a signature must have "x" in the handed over column and a Contact name.
All rows of one contract must have the same signature file. You cannot mix signed and unsigned rows in one contract.
After validation, click Next. In the Attachments step, click Select files and select the signature images. Images are matched to the rows by filename, ignoring upper and lower case.
Each image is cropped to the signature and saved as PNG. An image is rejected if it contains no signature, cannot be read, or is larger than 1 MB after this preparation.
Before the import, the preview shows how many rows will be imported as signed and how many will wait for a signature.
Locations that require a signature
If the contract settings of a location enforce signature verification, every contract imported there must be signed: handed-over rows need a signature file, and rows that are not handed over yet need Verification = x. Otherwise validation stops with: "Location … requires a signature on every contract. Following rows need a signature, or Verification = x without Handed over. Import before enabling signature enforcement". Add the signature files, or import the keys before you enable signature enforcement in Organization contract settings.
If a location enforces another verification type, the import cannot create those contracts and stops with: "Following locations enforce a verification type that the import cannot create. Import before enabling verification enforcement".
Import the File
Click Upload file and select your filled-in file (XLSX or CSV). After that, click Validate.
Confirm the imported keys by clicking Import.
If your file lists contract attachments (
Contract Attachmentscolumn) or signature images (Signaturecolumn), the button is Next instead of Import. In the Attachments step, click Select files, select every file named in your import file, and click Upload. The import starts after the upload.
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 exactly. If a required column is missing, validation stops with "Required template columns are missing". Columns that are not in the template are listed with "These columns are not recognized and their values will be ignored", and you can still import the file.
Each file can contain a maximum of 1500 keys
Required fields: Building ID or Customer ID, 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





