Data migration is the process of transferring data from one system to another while ensuring accuracy, security, and minimal disruption to business operations. A well-planned migration ensures that critical data is preserved, remains accessible, and functions properly within the new system. To achieve this, following a structured approach is essential for success.
RIVO provides businesses with a comprehensive migration solution for key financial instruments, including:
- Outgoing Guarantee (Not syndicated/ Corp Consortium)
- Outgoing Standby LC
- Incoming Guarantee
- Incoming Standby LC
- Import LC
- Attachments
By enabling the migration of these critical data sets, RIVO ensures a seamless transition while maintaining compliance and operational efficiency.
Parent Company Guarantees – Migration Guidelines
When migrating parent company guarantees, the values entered in the My Bank fields depend on whether the guarantor is a Headquarter or a Sub-Unit.
Case 1: Sub-Unit Acting as Guarantor
My Bank (Name*): Name of the Headquarter
My Bank (Unit Name): Name of the Guarantor (Sub-Unit)
Case 2: Headquarter Acting as Guarantor
My Bank (Name*): Name of the Headquarter
My Bank (Unit Name): Name of the Guarantor (Headquarter)
For Parent Company Guarantees, a BIC is not required, as the guarantor is a corporate entity and not a bank.
Issuance Status During Migration
If Bank Reference and Effective Release Date are not filled, the migrated record will be created with status Issuance Approved.
If Bank Reference and Effective Release Date are filled, the migrated record will be created with status Issued.
How to Migrate
- From the Dashboard of Rivo, go to the
(Please note only the RIVO admin users have access to this menu.)
- Navigate to the Data Migration tab, where you can select the available products for migration and initiate the migration process.
- After selecting the product, you want to migrate, proceed by starting the Start Migration Process.
- Download the Migration Template, complete it with all the essential information, and then start uploading that file to Rivo.
Understanding Migration Log Errors and Warnings During File UploadWhen uploading files during a data migration, the system generates a migration log that captures important details, including any errors or warnings encountered.
Error: A critical issue that prevents the record from being processed. Errors must be resolved before successful migration.
Warning: A non-critical issue. The record is processed, but the system flags potential inconsistencies or recommendations.
How to Access the Migration Log
- If issues occur, a log file will be generated as shown in the below GIF.
Click the
“xls file”
Open the log to review all warnings and errors line by line.
Migration HistoryThe Migration History section provides a comprehensive overview of all data uploads performed within the system. It helps you track and verify past migrations, see processing outcomes, and download detailed logs for analysis.
Fields in Migration History
Here’s a breakdown of the key columns you'll see in the Migration History dashboard:
| Field | Description |
|---|---|
| Upload Date | The exact date the file was uploaded |
| Uploaded By | The username of the person who performed the upload |
| Data | The type or category of data being migrated (e.g., Outgoing guarantee, attachments) |
| Total Items | The total number of records included in the uploaded file |
| Processed Items | Number of records that were successfully processed |
| Status | The final result of the upload: Completed, Cancelled |
| Download Log | 3 Dots- Context menu to download the log file, showing all errors and warnings related to the upload |
Comments
0 comments
Please sign in to leave a comment.