Infor LN Implementation
Infor LN Migration
About us
Contact
What is the transition phase?
The transition phase is the final project phase preceding and immediately following the go-live. Once the go-ahead decision has been made and the system has reached the defined maturity level, preparations for live operation begin.
This phase focuses on ensuring the transition from the legacy system to the target system from a business, technical, and organizational perspective.
The goal is not a go-live at any cost, but rather a transition that is sustainably planned with regard to day-to-day operations, data consistency, and responsibilities.
What the final result should be
- User Training
- User Acceptance Testing
- Cutover Planning
- Final Data Migration
- Go-Live
- Supporting Users During the Start-up Phase
Why is the transition phase so critical?
During the transition phase, the project intensifies. Many issues that were previously considered separately now converge within a tight timeframe: business units must be operational, data must be fully migrated, interfaces must be converted, and the system must function stably under real-world conditions.
It is precisely at this stage that it becomes clear whether the project is merely technically complete or truly ready for production.
Typical challenges during this phase include:
- End users are working in the new system for the first time
- The cutover involves many interdependent steps
- Remaining tasks from earlier phases are competing with go-live preparations
- The time windows for data migrations and posting freezes are tight
- Finance must confirm that balances, values, and core processes are correctly mapped in the new system
For this reason, the transition phase is not merely a final acceptance process, but a transition that is highly critical from an operational standpoint.
What are the key topics during the transition phase?
Once the business processes have been defined in the system, end users are prepared for their future tasks in the live system. This involves not only learning how to use the system, but above all ensuring that processes are carried out reliably in day-to-day operations.
Important questions to consider at this stage are:
- Who needs to be trained, and when?
- Which roles will be working with which transactions later on?
- What are the differences between test and production environments?
- How will inquiries be handled after the go-live?
This is particularly evident in projects involving new target processes, where training and change management go hand in hand. When responsibilities or procedures have changed, this must be clearly communicated to users.
The User Acceptance Test is the stage at which the system’s functional usability is evaluated from the users’ perspective. Even if processes have been coordinated with key users beforehand, it is often only during this phase that it becomes clear whether the system is truly viable for day-to-day operations.
This applies, for example, to:
- Clarity of Workflows
- Completeness of Process Steps
- Practicality in Day-to-Day Operations
- Role and Authorization Perspective
- Exceptions and Special Cases
From a project perspective, the UAT is particularly important because it provides another opportunity to see whether previous decisions have gained broad support throughout the organization.
A key component of the transition phase is the cutover plan. It outlines the steps that must be taken before go-live, during the transition, and immediately afterward, along with the order in which they must be carried out.
These typically include:
- Migration or Activation of Interfaces
- Last processing times in the legacy system
- Posting stops
- Open production or logistics processes
- Final data transfers
- Inventory transfer and reconciliation
- Responsibilities and approvals for each step
A viable cutover plan depends not only on defining the tasks, but also on realistically assessing the time required, the sequence of tasks, dependencies, and responsibilities.
While test migrations have already been conducted in earlier phases, the transition phase involves preparing for the production migration. The key considerations here are which data will be migrated as of the cutoff date, which data sets must be frozen, and which transactions will need to be updated manually after the switchover.
Typical questions include:
- Until when can master data be changed in the legacy system?
- What transaction data will still be transferred?
- Which open transactions must be entered retroactively in the new system?
- How long do data runs actually take?
These points are crucial for go-live planning because they directly affect the timeline for the cutover.
Clear approvals are required before the system goes live. This includes both business and technical evaluations.
The project typically examines the following:
- Are the core processes stable?
- Are the data and balances accurate?
- Are the finance-related figures plausible?
- Are the interfaces functioning as planned?
- Are end users and key users able to perform their tasks?
Approval from a financial perspective, in particular, is often a sensitive issue. Balances, values, and posting logic must be thoroughly verified before the new system goes live.
What happens after the transition phase?
Transition
- User Training
- Benutzerakzeptanztest
- Cutover Planning
- Production Launch
Optimization
- Stabilization
- Further Development
- Performance
Once the system goes live, the next important phase begins: stabilization and targeted further development in live operation. During the optimization phase, non-critical requirements, performance issues, and other improvements are implemented in a structured manner.
FAQs About the Transition Phase
A cutover plan outlines all the steps involved in the transition from the legacy system to the target system: downtime, data migrations, interface changes, approvals, responsibilities, and time dependencies.
Most often, this is not caused by a single technical error, but rather by the interplay of many factors: data status, pending tasks, tight deadlines, unclear responsibilities, or users who are not adequately prepared.
Because a productive system must also be technically sound. The key factor is whether processes, roles, data, and follow-up activities actually work in day-to-day operations.
Key users oversee testing, provide technical support to end users, and help address questions and concerns in a structured manner after the go-live.
During the hypercare phase, live operations are closely monitored. The goal is to quickly resolve any outstanding issues, stabilize operations, and ensure a controlled transition to normal operations.
We will be happy to present solutions for your industry and your processes. Talk to the specialists for SMEs.
request now
