Skip to main content

Migrate time off requests from TSM

Written by Franzi Schuetzer

This article will guide you through the process of importing TSM time off request data into Kenjo using the bulk upload feature.


1. Basics

Kenjo allows you to import historical time off request data via a TSM export. This is particularly useful for maintaining compliance, ensuring accurate records, and facilitating a smooth transition from systems.

Few things to note before you start the migration process,

  1. Migrated time off requests are only stored and can’t be edited.

  2. For editable requests, please create new time offs either individually or in bulk.

  3. Requests with future dates will not be imported.

  4. Migrating past requests via TSM export will not automatically adjust current allowances for an employee. Use manual adjustments. Learn more.

Before you initiate the migration, it’s important to understand how we transform the data from TSM and how historical data will appear in Kenjo after the migration.

Note:
The file for time off data and attendance data is the same. Check out how to download it here.

Example:

  • Information from the TSM export file looks like this:

Kenjo processes this data like this:

  • Employee 2 has an approved hourly paid time off of 8 hours on Friday 21st March 2025

  • The time off entry belongs to the paid time off (PTO) type, Urlaub

Once you perform the migration, Kenjo does the following:

  • maps the Employee # to the Employee ID field in Kenjo to identify the respective employee

  • creates a dummy policy under the mapped time off category (Name of dummy policy in this example - Urlaub: TSM)

  • creates a time off request with the following aspects:​

Full day hourly requests

number of hours = value under PAID TIME OFF column in the file

Status

is submitted (i.e. already approved)


Description

value under SITE NAME column in the file


Step 1: Select Import Type

  • Navigate to Settings > Data import

  • Select Time off and click Import

  • Choose the option Migrate with TSM export and click NEX


Step 2: Upload Your File

Before you start,

  • Make sure each employee in the file is already created in Kenjo with the correct Employee ID. Kenjo will use the Employee ID as the unique identifier to map it to the employees in the system.

  • You can update Employee IDs individually via the employee profile or in bulk via the Import wizard

  • The export file needs to be in any of the 6 languages supported by Kenjo

  • Make sure you have the correct export file from TSM

  • Select the language of your file’s header columns (e.g. English).

  • Drag and drop your TSM export file (CSV/XLSX format) or select it from your computer.

  • Click UPLOAD once the file is attached.


Step 3: Map Your Data

In this step, you don't need to take any action. If the correct export file was uploaded in the previous step, Kenjo converts the time-off data from TSM into our system format and allows you to continue the import.

If there is an error on this step, please check if you have the right file from TSM.

  • Click Confirm to proceed to next step


Step 4: Map Time Off Types

Kenjo will map Paid time off types identified from the file to the time off types available in Kenjo. For unmapped time off types you need to select the correct time off type using the drop-down menu.

Note:
In France, PRIME D'INTERVENTION is skipped, as this is handled as an Attendance category in Kenjo.

1

This is the name of the mapped time off type in Kenjo

2

The green check mark indicates that the respective field has successfully been mapped

3

The black x indicates that the TSM field was not mapped

  • Click x to delete the Kenjo field that has been mapped by default

  • Find the correct field via drop-down-menu and select it

4

Check this box to exclude unmapped columns

  • Click Confirm after mapping is complete.


Step 5: Finalize Import

  • Review the file name

  • Click Finalize import to complete the process

When all data is processed you receive an email of the import. You can also view it in the Data import section, also whether errors occurred.

Did this answer your question?