RMS - Migration Data

Owned by Patrick Bui (Unlicensed)
Last updated: Nov 13, 2023
2 min read

General

This guide is for BA or PM who is in charge of migrating data for customers from Magestore legacy functions (Inventory Count, PO, Inventory Transfer,…) to RMS functions.

Stage 1: Backup Data

To make sure that there will be no conflict between backend data and RMS data, all RMS data will be removed during the data migration phase. Therefore, we have to backup data so that we can restore it later.

You can define to backup data or not for each function.

Dev will run the console for “Backup RMS data” in the link below to backup the data

https://git.magestore.com/magestore-product/rms-data-migration/-/tree/develop?ref_type=heads#backup-rms-data

The system will create tables for backup data in the database of the server with the prefix “rms_backup”

Stage 2: Migrate Data

Step 1: Select which function to migrate

We can define which for each function if they are migrated or not in an xml file in the server. Currently there are functions to migrate:

  • Inventory Count

  • Inventory Adjustment

  • Inventory Movement

  • Inventory Transfer

  • Purchase Orders

Step 2: Define migrate source for POs

Before running the console to migrate (if you want to migrate Purchase Orders), we have to config for the migration of POs first. You will run the command for “Pre-check Purchase order”. The system will check all the current POs to see if there is any POs that needs to select source to migrate manually.

https://git.magestore.com/magestore-product/rms-data-migration/-/tree/develop?ref_type=heads#backup-rms-data

(The PO on backend can be transferred to any source, while the PO on RMS is assigned to a source only).

There will be POs that is Pending or In-progress, but haven’t transferred product to any source, so they will need to be assign manually.

→ The system will auto-generate a file that contains all those POs.

You can read more about this function in this document.

https://docs.google.com/spreadsheets/d/1xO5Mu5x29VRP7oR-5U0vHY8ZKPZIZWB_JBQ-Exu-QuA/edit#gid=254153794

After that you can send the file as CSV to the customer so that they can fill in the Source Code for all POs in the CSV, then you can import back to the system

(The file in assign_source_code_to_purchase_order_csv_file option)

Note: As a BA or PM, you have to check if:

+ All the POs has been filled in Source Code.

+ No POs from the file has been deleted or modified in the CSV by the customer. (make sure they only fill in Source Code)

+ The filled in Source Code(s) are the right one.

Step 3: Migrate Data

After all those above step. Dev can run the command for “Migrate data” in the link below to start the migration.

https://git.magestore.com/magestore-product/rms-data-migration/-/tree/develop?ref_type=heads#backup-rms-data

The current data will RMS will be removed to be replaced with data from Backend. The data will be migrate as the following documents

The function data structure may be different from Backend, therefore many data may not be migrated, so please check the document carefully.

Please check if the data has been migrated successfully and accurately or not.