Step 1: Preparing & Planning

The first stage is to gather information from all the key stakeholders including front-line users to understand the processes in play and determine how the proposed implementation will help in specific areas.  

All processes need to be mapped out to ensure that the overall needs of the business are defined. These processes then need to be prioritized to start to create the plan of attack.

Step 2: Process Review

This stage involves reviewing the process needs against the capabilities of the ERP software to ensure that all points are catered to. Needs can be addressed by either intrinsic functionality through configuration, customer configuration, or the creation of bespoke modules or bespoke software bolt-ons.

Once defined, each process solution should be discussed and demonstrated to key users to ensure it meets their specific needs and delivers the process gains being sought. This stage will also help to identify where training will be needed.

Step 3: Data Management & Preparation

The next stage is concerned with the current situation in terms of data management and determining a plan that will allow for some or all to be converted over to the new platform. This stage can also be used to sanitize data and reduce the retention of unnecessary data.  

This process needs to consider the timings of data transfer and be aware that some integration with legacy systems may be necessary to allow for continued operation during the changeover process.

Step 4: Testing & Training

Once the data for all or a specific area of the business has been populated testing can begin. This will involve running the system in parallel for a period to ensure there are no issues that haven’t previously been identified. This allows staff to get familiar with the system before go-live which minimised disruption post switchover.  

Testing is normally tiered and only moves on if successful: 

• Project team testing 
• Key user testing 
• Wider user testing

Step 5: Rollout & System Hardening

This stage is the most exciting part. This is where part or all the system comes into play and replaces existing systems.  This is potentially the most disruptive part so needs to be effectively planned considering the below as a minimum: 

• System testing process defined post-go live.
• Issue feedback process defined.
• Adequate technical and managerial resources. allocated for time-sensitive changes.  
• Issue manage the process to prioritise any required updates or changes. A solid fallback position for data management.