---
title: "Migrating Data"
description: "The Migration workspace lets you move your existing lease portfolio from the IFRS 16 script into Lucanet Lease Accounting. You upload the H2 database file together with the lookup file, run the migration, validate the migrated data, and approve the result."
source_url: https://support.lucanet.com/en/documentation/lease-accounting/basic-configuration-lease-accounting/migrating-data
language: en
last_updated: 2026-06-01
---
# Migrating Data

## Overview

The **Migration** workspace lets you move your existing lease portfolio from the IFRS 16 script into Lucanet Lease Accounting. You upload the H2 database file together with the lookup file, run the migration, validate the migrated data, and approve the result. Once the migration is approved, Lease Accounting takes over the carrying amounts of your lease portfolio and you can resume calculations, postings, and exports without recalculation gaps.

{% info-box %}
Preparing the IFRS 16 script in Lucanet.Financial Client and exporting the H2 database file and the lookup file from it is carried out together with your Lucanet Professional Services consultant. This page describes the steps that follow inside Lease Accounting in the CFO Solution Platform.
{% /info-box %}

## Prerequisites

To run the migration from the IFRS 16 script to Lease Accounting, you need one of the following roles:

- Full access administrator
- Settings administrator
- Lease operations administrator

Before you start, prepare the following files from your source IFRS 16 script:

- The **H2 database file** (.mv.db) exported from the IFRS 16 script. This file contains your leasing components, associated payments and options.
- The **lookup file** (XLS or XLSX format) exported from the IFRS 16 script. This file maps source OIDs to their respective transaction currencies and is required so that each migrated component carries the correct component currency.

## Overview of the Migration Flow

The migration from the IFRS 16 script to Lease Accounting consists of the following stages:

{% stepper %}
{% stepper-step %}
**Upload** the H2 database file and the lookup file in the **Migration** workspace.
{% /stepper-step %}
{% stepper-step %}
**Start the migration** with the migration date that applies to your data.
{% /stepper-step %}
{% stepper-step %}
**Download the migration and component validation reports** to identify any data gaps.
{% /stepper-step %}
{% stepper-step %}
**Validate** the migrated data in **Lessors**, **Contracts**, and **Contract components** workspaces.
{% /stepper-step %}
{% stepper-step %}
**Approve the migration** to unlock calculations, postings, and exports.

{% /stepper-step %}
{% /stepper %}

## Uploading the Migration Files

To upload the migration files:

{% stepper %}
{% stepper-step %}
Navigate to **Settings | Migration**.
{% /stepper-step %}
{% stepper-step %}
In the upload area, choose one of the following options to attach the files:

- Drag and drop both files onto the upload area.
- Select **choose a file** and pick both files from your file browser.

The upload area accepts .mv.db database files together with the .XLS and .XLSX lookup files. You must provide both the H2 database file and the lookup file together — the **Upload files** button only becomes active once both files are present and in their expected formats.
{% /stepper-step %}
{% stepper-step %}
Click **Upload**.

The files appear as a combined entry in the **Uploaded databases** table with the status **Ready to migrate**.
{% /stepper-step %}
{% /stepper %}

{% warning-box %}
**Upload only the latest version of the H2 file and its lookup file.**

Both files are mandatory and must be uploaded together as one package.

If you upload another package after a migration has finished, Lease Accounting adds the new data to the existing migrated data instead of overwriting it.

You can delete an uploaded file until you approve its migration. Deleting an uploaded file does not remove any data that has already been migrated.
{% /warning-box %}

## Starting the Migration

To start the migration:

{% stepper %}
{% stepper-step %}
In the **Migration date** field in the **Migration** workspace, select the date from which existing carrying amounts for the right-of-use assets are taken over from the IFRS 16 script.

The migration date is used to avoid recalculation gaps or migration differences. Lease Accounting stores the migration date with the uploaded file and shows it later in the **Migration date** column.

Migration date in the 'Migration' workspace
{% /stepper-step %}
{% stepper-step %}
In the **Uploaded databases** table, select the **Start migration** icon next to the file you want to migrate. The **Start Migration** dialog is displayed:

'Start Migration' dialog
{% /stepper-step %}
{% stepper-step %}
Review the file name and the migration date, then click **Proceed**.

While the migration runs, the **Status** column displays the progress of the migration. When the migration finishes, the status changes to **Migrated** and Lease Accounting displays a confirmation dialog:

Migration confirmation
{% /stepper-step %}
{% /stepper %}

## Downloading the Migration and Component Validation Reports

After a successful migration, you must validate the migrated data before you can approve the migration and resume calculations, postings, and exports. The data carried over from the IFRS 16 script may contain placeholder values, missing mandatory information, or zero amounts that need your review.

To help you identify these gaps, Lease Accounting provides two on-demand reports — the **Migration report** and the **Component validation report**. Both reports are generated in Excel format and tell you which records need attention, so you know exactly what to correct in the next step.

To download a report:

{% stepper %}
{% stepper-step %}
In the **Migration** workspace, select **Migration report** or **Component validation report** above the **Uploaded databases** table.

Uploaded databases table with the Migration report and Component validation report

The reports are generated in the background. Once they are ready, they are automatically displayed in the **Generated reports** table in the same workspace.
{% /stepper-step %}
{% stepper-step %}
Click the **Download** icon next to the report to save the Excel file to your computer.
{% /stepper-step %}
{% /stepper %}

### Migration Report

The **Migration report** lists, for each migrated element (lessors, contracts, contract components, payments, options), whether the element was migrated successfully and, where applicable, the reason for which an element could not be migrated. Use this report to confirm overall data integrity after the migration.

### Component Validation Report

The **Component validation** report lists every component together with its validation findings — the validation rule that triggered, the message returned, and the result (warning, error, or exception).

After a migration, the report shows two additional categories of findings under **Migration from legacy solution:**

- **Dummy values** — flagged whenever a component field still carries placeholder text from the IFRS 16 script. The finding is an error when the placeholder is in the asset class or component currency, and a warning on any other component field.
- **Zero amounts** — flagged as errors whenever an amount field on the component form equals zero, since these usually require review after the migration.

Use this report to find the components that still carry placeholder values from the IFRS 16 script, or that contain zero amounts that may need to be corrected before approval.

## Validating the Migrated Data

After you have the report findings, work through them in Lease Accounting. While the migration is pending approval:

- Migrated lessors, contracts, and contract components are available under **Data collection** for review and correction.
- You can save migrated records even when required fields are empty or still hold placeholder values. Normally, Lease Accounting blocks saving until every required field has a valid value, but this rule does not apply to migrated records while the migration is pending approval. This lets you save partial corrections and return to them across multiple sessions. The full check is restored when you approve the migration — every required field must be complete and free of placeholders before you can approve.
- The [Calculation | Preview](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) workspace remains available so you can review potential calculation results at any time. After the migration is approved, use **Calculate and save** to finalize the calculations.
- The [Calculation | Calculations](https://support.lucanet.com/en/documentation/lease-accounting/measurement.md) workspace, all workspaces under [Postings](https://support.lucanet.com/en/documentation/lease-accounting/create-postings.md), and [Export | Export postings](https://support.lucanet.com/en/documentation/lease-accounting/export-data.md) are hidden until the migration is approved.

To review and correct a migrated record flagged in the reports — a lessor, contract, or contract component — proceed as follows:

{% stepper %}
{% stepper-step %}
Navigate to [Data collection | Lessors](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-lessor.md), [Data collection | Contracts](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contracts.md), or [Data collection | Contract components](https://support.lucanet.com/en/documentation/lease-accounting/data-collection/create-configure-contract-components.md).
{% /stepper-step %}
{% stepper-step %}
Open the record and review each tab.
{% /stepper-step %}
{% stepper-step %}
Replace any placeholder values, complete any missing mandatory information, and select **Save**.
{% /stepper-step %}
{% /stepper %}

## Approving the Migration

After you have validated all migrated data, approve the migration.

{% warning-box %}
Select **Approve Migration** only when you are confident that all data has been thoroughly reviewed and validated.
{% /warning-box %}

To approve the migration:

{% stepper %}
{% stepper-step %}
In the **Migration** workspace, select **Approve migration** in the top right. The **Approve Migration** dialog is displayed:

'Approve Migration' dialog
{% /stepper-step %}
{% stepper-step %}
Review the consequences:

- Contract data can no longer be edited.
- Components remain editable until they are calculated.
- Later changes are possible only through standard modifications.
- Further H2 file uploads after approval will follow the migration workspace rules (such as duplicate file rejection by content, not by file name).
{% /stepper-step %}
{% stepper-step %}
Click **Proceed**.

When approval succeeds:

- The warning indicators next to **Lessors**, **Contracts**, and **Contract components** are removed.
- The **Calculations**, **Postings**, and **Export postings** workspaces become available.
- The migrated files in the **Uploaded Databases** table receive the status **Approved**.
{% /stepper-step %}
{% /stepper %}

{% info-box %}
Approval is only possible if all migrated records pass standard validation. If any record still has missing mandatory fields or other validation errors, Lease Accounting prevents approval and notifies you of the outstanding issues.
{% /info-box %}

## Handling a Failed Migration

If a migration cannot be completed successfully, Lease Accounting displays the status **Failed** for the affected file in the **Uploaded databases** table.

If the migration process fails, try the following steps:

{% stepper %}
{% stepper-step %}
**Check the uploaded files** — ensure the H2 file and its corresponding lookup file are valid and not corrupted.
{% /stepper-step %}
{% stepper-step %}
**Retry the migration** — you can delete the affected file entry and re-upload the files before starting the migration again.
{% /stepper-step %}
{% stepper-step %}
**Contact support** — if the issue persists, please contact your Lucanet administrator or Lucanet Support with the details of this error.

{% /stepper-step %}
{% /stepper %}

### Missing Reporting Entity

If the H2 file contains records for a reporting entity that does not exist in Lease Accounting, the migration ends with the status **Failed** and the failure reason names the missing OID.

To recover:

{% stepper %}
{% stepper-step %}
Import or create the missing reporting entity in Lease Accounting under **Settings | Reporting entities**.
{% /stepper-step %}
{% stepper-step %}
In the **Migration** workspace, select the **Re-run** icon next to the failed file.

The re-run skips records that were migrated successfully in the previous run and only processes records that previously failed or were skipped. You do not need to upload the files again.
{% /stepper-step %}
{% /stepper %}