Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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.

Note that there will be some data you have to confirm with your customer to migrate successfully.

Why do we need to migrate data?

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

We can define which for each function if they are migrated or not. Currently there are functions to migrate:

  • Inventory Count

  • Inventory Adjustment

  • Inventory Movement

  • Inventory Transfer

  • Purchase Orders

Before running the console to migrate, 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.

There will be POs that is Pending or Inprogress, but haven’t transferred product to any source

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

  • No labels