Data Migration in Upgrade Project

Hi @manjunath.rao01,

first of all it should be clarified if the upgrade is a technical upgrade or planned as a data migration.
Technical upgrade means that a database copy will be performed and on this cloned database upgrade scripts are running to uplift the core from old version to new version. All data will be transferred since it’s based on a cloned database and “only the meta structures” are lifted to the new version.
A migration project means that you start with an empty database and migrate the needed data into the environment. But this means that e.g. historical data like closed customer orders, payed invoices and so on will not be transferred and remain in the old IFS version.
Is it already decided that it should be performed as a migration project?

BR
Martina

Yes, if you are doing a new install nothing else than what you explicitly migrates will be moved from the older version. It doesn’t matter what type of data it is. (Transactional, historical, basic data or whatever you call it.).

However if you migrate inventory parts, new records will be there for InventoryPartConfig but not with the data from old database of course.

LotBatchMaster, LotBatch History and Part Serial History might also be filled in with new data when you migrate inventory stock if the parts are lot batch or serial tracked. But same thing here, nothing old is migrated automatically.

@Tomas Ruderfelt 

How about migrating the data into the Part Serial screen.

I understand that it could be required for the Equipment Serial Object data migration. What shall be the value for “Current Position” field when we try migrating the data in Part Serial window?

Regards,

Manju