Migration Settings

The migration tool can be used to migrate objects created in another system (e.g., Nakisa Lease Accounting Suite versions 2022.R2.SPx) into the latest Nakisa Lease Accounting Suite and Nakisa General Ledger. You can also migrate historically transactions posted in another system via API. You can perform the migration with a single cut-over date in one phase, or migrate objects in multiple phases using multiple cut-over dates.

All migrated objects (master agreements down to units) are identified with a "Migrated" flag so that they can always be identified or separated via filtering options. This also applies to objects created manually directly in Nakisa Lease Accounting Suite, or objects created via an integrated Nakisa Portfolio Management Suite. Note that only transactions imported via API have the "Migrated" flag. Transactions posted for migrated activation groups will not have the "Migrated" flag. To identify, filter, and group information related to migrated objects, all job filters include a Migrated Filter Type, and the landing pages have the Data Source as a filter option. The Consolidated Transaction Report in Nakisa General Ledger also has a Migrated column to identify the transactions migrated via API.

When Migration Mode is active, users in Nakisa Lease Accounting Suite are notified by the message "Migration Mode is ON" in the header.

Note: There can only be one active migration period setting at any time, and settings cannot be deleted.

To set up a migration period:

Click Main Menu > Settings > Migration Settings.
Click to add a new migration period.
Enter the following information:
- The Type field is automatically set to "Migration".
- Set the ID Generation Type to one of the following options:
  - Auto: The application automatically generates display IDs based on the Number Range Configuration.
  - Manual: You must provide the display IDs for master agreements, contracts, lease components, activation groups, and units. These objects can only be created in Nakisa Lease Accounting Suite via Excel import or API calls. Note that if you do not provide Display IDs, the import will fail.
- Enter the Source of the data migration.
- If you already know when the migration period should end, select the date and time in UTC timezone in the End Date Time field. Otherwise, come back and set it later when the date and time are known.
Click Save.

To manage your migration periods:

To edit any of the fields in an active period, click in the Actions column.
To add notes about an active migration period, click in the Actions column.
To deactivate the Migration Mode, click in the Actions column. The End Date Time is automatically updated to the current time (in UTC).