Differences between Omikai 1 and Omikai 2

Differences between Omikai 1 and Omikai 2

Goal

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.

Warning
The provided transcript does not include the detailed list of items that are migrated. Because of this, we cannot publish the exact migration scope here.
Idea
For official migration notes and checklists, visit the Help Center: http://support.omikai.com.

Procedure

Step 1: Confirm the migration scope document

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

Step 2: Validate key lists after migration

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

Step 3: Capture differences and confirm expected behavior

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.

Idea
Keep a copy of your migration scope and your validation notes with your project documents. This makes future audits quick and simple.

Step 4: Get the official list if you do not have it

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.

    • Related Articles

    • What is migrated from Omikai 1 to Omikai 2

      Goal This article explains what data is migrated when moving from Version 1 to Version 2 of the system. It also shows how to review the results and handle items that are not migrated. Procedure Step 1 — Review what is migrated The lists below show ...

    • API documentation

      Goal Open the API documentation for the system. Procedure Step 1: Open the API documentation Open your web browser and go to http://api.omikai.com. Bookmark the page so you can find the API documentation quickly in the future. If the page does not ...

    • Email/SMTP Configuration

      Goal Set up email sending through Microsoft 365 using SMTP. Optionally, add an SPF record if needed. This lets users send emails from the system with their own Microsoft 365 mailboxes. Procedure Step 1: Enable SMTP Authentication in Microsoft 365 In ...

    • Update project

      Goal Update a project in the system. Changes are saved automatically, so you do not need to click Save. Procedure Step 1: Open CRM From the main menu, click CRM. Step 2: Open the projects list Click Project to open the list. You can also go directly ...

    • Add project

      Goal Create a project to connect related items in the system. A project can group records such as orders, quotations, activities, and product templates. Use it to organize campaigns or any work that involves several records. Procedure Step 1: Click ...