Construction Phase of the Infor Migration

During the construction phase of the Infor migration, the agreed-upon business and solution designs are transformed into a fully operational system. Configuration, development, interfaces, and data migration are implemented and tested to ensure that the defined target processes run reliably within the system. It is precisely during this phase that it becomes clear how thorough the preliminary business analysis was and how consistently mandatory requirements were separated from later optimization topics.

Schedule a Free Initial Consultation

What is the construction phase?

The Construction Phase is the implementation phase of the Infor migration. Based on the target processes, requirements, and system boundaries defined in the Elaboration Phase, the target system is built, configured, and equipped with the necessary developments, interfaces, and data.

At the end of this phase, the system is ready for go-live and reliably supports the defined core processes.

What the final result should be

Development of the business model
Configuration of the required functions and packages
Implementation of developments
Development and testing of interfaces
Execution of data migration
Functional and technical testing

Why is the construction phase so crucial?

The construction phase is the point at which technical decisions must prove their worth within the system. Processes that appear sound on paper must now function effectively in conjunction with data, roles, interfaces, and posting logic.

In projects, this is often where it becomes clear which issues were actually prepared thoroughly and where unresolved details from earlier phases continue to have an impact.

This applies primarily to:

Interfaces whose business logic is more complex than initially assumed
Data structures that must be managed differently in the target system
End-to-end processes that only reveal their weaknesses during testing
Requirements that are desired from a business perspective but are not critical for the go-live

That is precisely why this phase requires clear priorities. It is crucial for the project’s progress to determine early on what must function reliably by the go-live date and which issues can be deliberately deferred to a later optimization phase.

What topics are addressed during the construction phase?

Business Model and System Framework

At the start of the construction phase, the basic structure of the target system is established. This primarily involves defining the enterprise model: Which companies will be managed in the system? Which units represent locations, plants, or organizational responsibilities? Which modules and functions are actually needed?

These decisions are critical for the subsequent implementation because processes, master data, authorizations, and later testing procedures are based on them.

Configuring Target Processes

In the next step, the defined target processes are configured in the system. In doing so, the target state from the elaboration phase is mapped in the system in such a way that the intended workflows function under the customer’s actual operating conditions.

This applies, for example, to:

Process parameters and control logic
Relevant LN packages and functions
Organizational assignments
Transaction-related processes in Logistics, Manufacturing, and Finance

Not every available standard feature is automatically used in this process. In practice, the system is specifically tailored to the project's requirements.

Developments and Interfaces

When standard functions and configurations are insufficient, extensions and interfaces are implemented during this phase. This applies to both functional gaps and the integration of existing third-party systems.

Typical areas of application include:

Custom developments
Integrations with PLM, CRM, MES, or other subsystems
Data flows between ERP and related applications
Technical and business interface logic

From a project perspective, interfaces are often the area that takes up more time than originally planned. The reason usually lies less in the technical connection itself and more in the business coordination: What data is transferred and when, which systems take the lead, and how are errors handled?

Data Migration to the Project Environment

Data migration is also implemented during the construction phase. Master data and—depending on the migration strategy—relevant transaction data are transferred to the designated project and test environments.

This isn't just about importing data, but also about whether the data works correctly in the target model:

Are the structures complete?
Is all required information present?
Can the defined processes be executed properly using the migrated data?
Does the data need to be cleaned up or supplemented before the next migration?

In many projects, several migration runs and simulations are scheduled for this purpose.

Making Targeted Use of Project Environments

In more complex projects, a clear separation of project environments has proven effective. Content that has been technically reviewed and approved is gradually transferred to a stable “Golden Company” environment. Based on this, separate environments are created for training and testing, as well as for technical development.

This separation facilitates:

controlled further development
transparent adoption of approved content
structured training preparation
targeted testing using realistic data

Especially when multiple teams are working in parallel, this structure provides the necessary stability throughout the project.

What tests are included in this phase?

Simulation tests verify whether configurations, developments, and processes within the system generally function as intended. They are used to run through defined workflows under controlled conditions and identify outstanding issues early on.

This involves, among other things:

correct process steps
data completeness
proper program logic
consistent results for individual transactions

Once the individual modules are running stably, their interaction across process and system boundaries is tested. This is particularly important in Infor projects because logistics processes often have a direct impact on finance and controlling.

Typical audit questions include:

Do business transactions trigger the correct follow-up actions?
Are integration attributes transferred correctly?
Are posting schemas and account assignments correct?
Do data transfers between departments work reliably?
Are values and production costs business-wise plausible?

In this phase, end-to-end processes are tested under realistic conditions—from operational posting to the impact on accounting.

The closer the project gets to go-live, the more important it becomes to involve key users. Later simulations and the user acceptance test are used to verify whether the system actually provides viable support for the agreed-upon processes in day-to-day operations.

It is often at this point that it becomes clear whether business decisions made in earlier phases work in practice or whether adjustments are still needed.

What challenges typically arise during the construction phase?

The construction phase is usually the most intensive phase of the project. Typical challenges include:

01	Interfaces require more coordination than expected
02	Processes work individually, but not end-to-end
03	Data migration is more than just a one-time import
04	There are still too many issues that need to be resolved before the go-live.

What happens after the construction phase?

Construction

System
Processes
Tests

Transition

Training Courses
Cutover
Production Launch
Hypercare

Once the system, processes, and tests have reached the defined maturity level, the transition phase begins. This phase focuses on training, cutover, going live, and hypercare.

FAQs About the Construction Phase

When individual steps work, but the process still has gaps across departmental boundaries. Typical indicators include unclear handoffs, incorrect integration postings, incomplete master data, or manual workarounds in testing.

All functions and processes that directly support operational workflows. Depending on the project, these may include, for example, core processes in purchasing, manufacturing, logistics, and finance, as well as critical interfaces and relevant posting logic. Convenience features or future optimizations should be evaluated separately.

Because a single test does not indicate whether the entire process runs stably under real-world conditions. Only end-to-end tests can show whether data, roles, follow-on processes, and financial implications function correctly when working together.

In this phase, key users are more than just testers. They help validate business processes within the system, prioritize outstanding issues, and assess the system’s future usability from an operational perspective. This feedback is especially crucial right before the go-live.

Talk to us!

We will be happy to present solutions for your industry and your processes. Talk to the specialists for SMEs.

request now