Cut-over activities need to be planned from MM side.

The process of transitioning from an old system to a new one requires a delivery called Cutover.The Cutover Plan document covers all the activities related to planning, preparing and executing the tasks and describes how to lock down the system from a technical perspective.The plan should be based on previous migrations that the client has already done.

A cutover plan describes all required tasks that must be performed before the go-live.

The key areas are Technical, Functional, Development, Authorizations, Data Cleansing & Data migration, Organization Change Management and Project Management.

There are some examples to be considered in the cutover plan.

Simulation of cutover activities is recommended to document the sequence and estimated times.Sequence migrations must be executed according to planning with control points.

The cutover checks and post-cutover activities are provided by the focused build for the solution manager.

The cutover approach is an organization specific strategy, so please be aware of it.

The number of people in this forum will be helped by your information.

Is period closing mandatory before the conversion to S/4?

There are 2 company codes that have a calendar year variant, but we have 11 with 9 set in September to August.

We are currently working on a project that will go live at the end of June.On a period closing day, S4 migration is to be done.

I'm sure there are other companies that have the same requirement, so I would appreciate any help on this.