Help & Support ↗ Lucanet Learning Space ↗
Documentation
Getting Started
Global Functions
Lucanet Lume
Administration
Data Hub
Consolidation & Financial Planning
Lease Accounting
General Functions in Lease Accounting
User Roles in Lease Accounting
All Steps at a Glance
Basic Configuration for Lease Accounting
Importing and Configuring Reporting Entities
Creating and Configuring Asset Classes
Creating and Configuring Interest Rates
Creating or Importing Cost Centers
Creating Profit Centers
Creating Accounting Areas
Creating Business Units
General Configurations
Migrating Data
Selecting a Lessee
Collecting Data
Categorizing Components
Calculating Data
Saving Postings
Reversing Postings
Exporting Reports and Postings
Importing Postings into Consolidation & Financial Planning
Extended Planning & Analysis (xP&A)
ESG Reporting
Disclosure Management
XBRL Tagger
Tax Compliance & Reporting
Banking & Cash Management
Data Collection
Glossary

Migrating Data into Lucanet Lease Accounting

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, execute 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.

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.

Prerequisites for the Migration to Lease Accounting

To execute 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 the migration to Lease Accounting, 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 in Lease Accounting

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

1

Upload the H2 database file and the lookup file in the Migration workspace.

2

Start the migration with the migration date that applies to your data.

3

Check the migration result in the Migration result tab and download the migration and component validation reports to identify any data gaps.

4

Validate the migrated data in Lessors, Contracts, and Contract components workspaces.

5

Approve the migration to unlock calculations, postings, and exports.

Uploading the Migration Files in Lease Accounting

To upload the migration files in Lease Accounting:

1

Navigate to Settings | Migration.

2

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.

3

Click Upload.

The files appear as a combined entry in the Uploaded databases table with the status Ready to migrate.

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.

Starting the Migration in Lease Accounting

To start the migration in Lease Accounting:

1

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.

Lease Accounting uses the migration date to avoid recalculation gaps or migration differences. Lease Accounting stores the migration date with the uploaded file and displays it later in the Migration date column.

Shows the 'Migration overview' tab of the 'Migration' workspace in Lucanet Lease Accounting with the 'Upload database' section, the message 'Upload only the latest version of the H2 file and its lookup file.', the upload area 'Attach file using drag & drop, or choose a file' for '.mv.db,.xlsx,.xls' files, the mandatory 'Migration date' field with the placeholder 'YYYY-MM-DD' and the help text 'The date from which existing carrying amounts are taken over from the previous solution — avoiding recalculation gaps or migration differences.', and the 'Uploaded databases' table with the columns 'Files' and 'Migration date'. Highlighted in red are the 'Migration date' field and the 'Migration date' column.
Migration date in the 'Migration' workspace
2

In the Uploaded databases table, select the Start migration icon next to the file you want to migrate. The Start Migration dialog is displayed:

Shows the 'Start Migration' dialog in Lucanet Lease Accounting with the file name 'test2.mv.db', the migration date '2026-05-22', the note that the data migrated from this file is not overwritten but added to the existing migrated data if you upload another H2 file later, and the 'Cancel' and 'Proceed' buttons.
'Start Migration' dialog
3

Review the file name and the migration date, then click Proceed.

While the migration is in progress, 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:

Shows the 'Migration to Lease Accounting Completed Successfully' dialog in Lucanet Lease Accounting with the request to review and validate the migrated data, to download the migration and the component validation reports, and to complete missing information in the sections 'Lessors', 'Contracts', and 'Contract Components', the note that calculations, postings creation, and subsequent actions are not possible until the migration is approved with the 'Approve migration' button in the 'Migration' workspace, and the 'Understood' button.
Migration confirmation

Downloading the Migration and Component Validation Reports in Lease Accounting

After a successful migration, you must validate the migrated data before you can approve the migration and resume calculations, postings, and exports in Lease Accounting. 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 one of the reports in Lease Accounting:

1

In the Migration workspace, select Migration report or Component validation report above the Uploaded databases table.

Shows the 'Uploaded Databases' table in Lucanet Lease Accounting with the columns 'Files', 'Migration date', 'Upload Date', and 'Migration status', and the file 'test2.mv.db / lookup-1.xls' with the status 'Failed', the reason 'No reporting entity found for OID: 239930…', and a start icon and a delete icon. Highlighted in red are the 'Migration report' and 'Component validation report' buttons above the 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.

2

Click the Download icon next to the report to save the Excel file to your computer.

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 displays 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.

Checking the Migration Result in Lease Accounting

The Migration workspace in Lease Accounting contains two tabs: the Migration overview tab with the upload and migration functions, and the Migration result tab, which summarizes the outcome of a migration so that you can assess it without opening the Excel reports.

To check the result, open the Migration result tab and select the migration in the Migration execution drop-down list. By default, the latest migration is selected. The tab displays how many components have been successfully migrated.

If components were not migrated, the Failed components table lists every failed component with the columns Reporting Entity, Lease component, and Reason for failure. The components are grouped by reporting entity, and each component displays its failure reasons. Click Show more to expand long reason lists.

Shows the 'Migration result' tab of the 'Migration' workspace in Lucanet Lease Accounting with the 'Migration execution' drop-down list set to '#34 — (file deleted) — 2026-07-31 11:56:35', the message 'Some Components Were Not Migrated' with the text '0 of 7 components have been successfully migrated.', and the 'Failed components' table with the columns 'Reporting Entity', 'Lease component', and 'Reason for failure'. The table lists the components 'Car 01', 'Car 03', 'Machine 10', 'Machine 12', 'Machine 13', 'Machine 17', and 'Machine 18' of the reporting entity 'Migration Test' with reasons such as 'component is empty in source H2 row' and 'No costCenter found for 2407508', and the footer '10 total failure reasons across 1 reporting entities'.
The 'Migration result' tab

The failed components and reasons match the findings in the Migration report.

Validating the Migrated Data in Lease Accounting

After you have the report findings, work through them. The following applies 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 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 workspace, all workspaces under Postings, and Export | Export postings are hidden until the migration is approved.

To review and correct a migrated lessor, contract, or contract component in Lease Accounting that the reports have flagged:

1

Navigate to Data collection | Lessors, Data collection | Contracts, or Data collection | Contract components.

2

Open the record and review each tab.

3

Replace any placeholder values, complete any missing mandatory information, and select Save.

Approving the Migration in Lease Accounting

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

Select Approve Migration only when you are confident that all data has been thoroughly reviewed and validated.

To approve the migration in Lease Accounting:

1

In the Migration workspace, select Approve migration in the top right. The Approve Migration dialog is displayed:

Shows the 'Approve Migration' dialog in Lucanet Lease Accounting with the instruction to upload and migrate all required files, including the lookup file and all H2 files if the IFRS 16 data is split across multiple H2 files, the consequences after approval that contract data can no longer be edited and components remain editable only until they are calculated, the note that files with identical content to a previously uploaded file are rejected as duplicates, and the 'Cancel' and 'Proceed' buttons.
'Approve Migration' dialog
2

Review the following consequences of the approval in Lease Accounting:

  • 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).
3

Click Proceed.

When approval succeeds, Lease Accounting applies the following changes:

  • The warning icons 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.

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.

Handling a Failed Migration in Lease Accounting

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:

1

Check the uploaded files — ensure the H2 file and its corresponding lookup file are valid and not corrupted.

2

Retry the migration — you can delete the affected file entry and reupload the files before starting the migration again.

3

Contact support — if the issue persists, please contact your Lucanet administrator or Lucanet Support with the details of this error.

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 from a missing reporting entity in Lease Accounting:

1

Import or create the missing reporting entity in Lease Accounting under Settings | Reporting entities.

2

In the Migration workspace, select the Re-run icon next to the failed file.

The rerun skips records that were migrated successfully in the previous execution and only processes records that previously failed or were skipped. You do not need to upload the files again.

This content was generated using AI and reviewed by Lucanet subject matter experts before publication.

Page IDKB0557715

Last updated on Oct 8, 2026

Table of Contents
OverviewPrerequisites for the Migration to Lease AccountingOverview of the Migration Flow in Lease AccountingUploading the Migration Files in Lease AccountingStarting the Migration in Lease AccountingDownloading the Migration and Component Validation Reports in Lease AccountingMigration ReportComponent Validation ReportChecking the Migration Result in Lease AccountingValidating the Migrated Data in Lease AccountingApproving the Migration in Lease AccountingHandling a Failed Migration in Lease AccountingMissing Reporting Entity
Related Articles

Company

Legal Notice

© Copyright 2026 - Lucanet AG