This article should explain what information is migrated from the old version (v1) to the new version (v2) of the system, so you can plan and verify your upgrade with confidence.


Ask your implementation or admin team for the migration scope document for your project. This document should list what data is moved from v1 to v2 (for example: master data, transactions, files, and settings).
After your migration window, compare a few totals between the old version and the new version. Check counts and spot-check records for these lists:
Open the same list in both versions, compare the total number of records, and then open a few individual records to verify important fields (customer, dates, amounts, statuses).
Record any differences you find and confirm whether each difference is expected due to version changes (for example, new fields, renamed statuses, or merged values). If the migration scope document states a field should be migrated, but it is empty in v2, note it clearly.

If you cannot locate the migration scope document, check the Help Center for migration articles and release notes: http://support.omikai.com. Share the link with your admin or implementation partner and request the official list of migrated data and any exceptions.