What Is an ERP Implementation?An ERP system integrates many functions across the business, such as financial management, human resources, sales and manufacturing, to deliver benefits such as increased productivity and efficiency. ERP implementation describes the process of planning, configuring and deploying an ERP. The process typically continues for a few months—and it’s complex, because an ERP system supports and automates many different functions. To ensure a successful implementation, the organization needs to carefully define its requirements, determine how to redesign processes to take advantage of the system, configure the ERP system to support those processes and rigorously test it before deploying it to users. Successfully navigating all those steps on schedule requires careful planning and a structured, phased implementation approach.
What Are the Phases of an ERP Implementation Plan?
A typical ERP implementation plan can be divided into six phases, each with specific objectives. Every business is unique, so the phases may vary somewhat depending on the company, and they also may overlap. The six-part ERP implementation phase lifecycle includes discovery and planning, design, development, testing, deployment and support.
1. Discovery & Planning
What is the first phase of ERP implementation? This includes researching and selecting a system, setting up a project team and defining detailed system requirements.
The project team will handle a broad range of roles related to the implementation, including laying out the project plan and target dates, ensuring adequate resources are allocated, making product and design decisions, and day-to-day project management.
The ERP project team typically includes an executive sponsor, a project manager and representatives from the departments that will use the system. Involving senior management is critical to ensure the project gets the resources it needs and to provide the backing needed to implement change across the organization. The team also may hire an external consultant or ERP implementation partner to provide expertise in designing and configuring the system. It should also include any internal specialists involved in implementing the system, such as a representative from IT and a report writer who will develop customized reports for users across the organization.
One of the team’s early goals will be to develop a detailed understanding of current issues, including process inefficiencies and requirements for the ERP system. If the organization has previously developed an ERP business case, it may have already defined broad business issues and goals for the implementation, which may include a faster financial close, improved insight into operations or preparing for an IPO. These can be used to direct more detailed analysis, including documentation of existing workflows, and to focus development of the system.
The team may select and acquire an ERP system during this phase, as the organization develops a clear idea of its requirements. One major decision is whether to use an ERP system that runs on-premises or in the cloud. For an on-premises system, you buy and install hardware and software in your organization’s data center. In contrast, cloud-based ERP is generally provided as a subscription service accessed via the internet, so it can be faster to implement and requires fewer in-house IT skills.
The design phase works from detailed requirements and an understanding of current workflows to develop a detailed design for the new ERP system. This includes designing new, more efficient workflows and other business processes that take advantage of the system. It’s important to involve users in the design phase, since they have the most intimate understanding of current business processes. Involving them in the design also helps to ensure that they’ll welcome the new system and take full advantage of it.
Gap analysis can be used to identify process intricacies and unique quirks that may require customization of the ERP software or changes to workflow or processes to more closely align with the ERP system itself. The team can present the gaps to its implementation partner or supplier and ask them to identify potential solutions.
Armed with clear design requirements, the development phase can begin. This involves configuring and, where necessary, customizing the software to support the redesigned processes. It may also include developing integration with any of the organization’s other existing business applications that won’t be replaced by the ERP system. If you’re using an on-premises ERP system, the organization will need to install the necessary hardware and software.
In parallel with software development, the team should develop training materials to help users adjust to the new system. It also needs to begin planning data migration, which can be complex since it often involves extracting, transforming and loading data from multiple systems, each of which may use different formats and may hold duplicate or inconsistent information. The project team should determine which data to migrate in this phase, avoiding the blanket migration of all historical data, lots of which is likely irrelevant. (See more on data migration below.)
Testing and development may occur concurrently. For example, the project team may test specific modules and features, develop fixes or adjustments based on the results, and retest. Or, it may test one ERP module while another is still in development. Initial testing of the basic functions of the software should be followed by rigorous testing of the full capabilities of the system, including allowing some employees to test the system for all their day-to-day activities. This phase should also encompass testing of the migrated data and include introductory end-user training.
Most vendors can supply pre- and post-deployment tools to begin user training. But in addition to vendor support, the organization should make good use of the training materials created in the development phase. There is real value in resources that specifically cater to your end-users’ day-to-day responsibilities.
This is what you’ve been striving toward: the day the system goes live. Be prepared for potential issues, since there may be a lot of moving parts and possibly some befuddled employees, despite your best efforts to prepare them for the change. The project team should be readily available to answer questions, help users understand the system and attempt to fix any issues. Your implementation partner should be able to help with troubleshooting if necessary. It may take time for users to adapt to the system and achieve the anticipated productivity gains.
Some data can be migrated ahead of deployment, while other information—such as current transactions—should be migrated immediately before going live.
Some organizations aim to deploy all the modules of the ERP system concurrently, while others focus first on specific high-priority modules or processes and add others later in stages. To minimize risk, some organizations also continue to run older systems in parallel with the new ERP implementation for a time, although this can add to the overall project cost and reduce user productivity.
6. Support & Updates
Nurturing your ERP implementation after deployment helps to keep users happy and ensure the business achieves the desired benefits. The project team may still be responsible for the ERP system during this phase, but its focus will shift to listening for user feedback and adjusting the system accordingly. Some additional development and configuration may be needed as new features are added to the system. New staff will also need to be trained on the system.
If you have an on-premises ERP system, you’ll need to install periodic software updates and may even need to upgrade hardware over time. If you’re using a cloud-based ERP system, your vendor may update the software automatically.