Migrating from the existing system on which currently working to the SAP system is called the legacy system. Cutover strategy that depends upon how the organizations design their data load STRATEGIES. NORMALLY, it decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then it make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon ORGANIZATIONAL setup and policies. Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly ENTERED. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of VARIOUS kinds.

Migrating from the existing system on which currently working to the SAP system is called the legacy system. Cutover strategy that depends upon how the organizations design their data load strategies. Normally, it decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then it make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies. Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.