How to implement an ERP? Steps and Methodology

An ERP implementation involves important steps such as software installation, moving financial data to the new software, configuring its users and processes, and training users to use the ERP. In this article we will see in more detail how to implement an ERP.

ERP implementation methodology

As in project management, there is no single valid ERP implementation methodology. Depending on the partner you choose, it will offer you one type of project or another.

Broadly speaking there are the following ERP implementation methodologies:

  • Waterfall Methodology: also known as waterfall methodology. It is the most traditional ERP implementation methodology. At the beginning of the project an exhaustive analysis of all the prerequisites is carried out, and once detected, the project adheres to that plan and the functionalities described in the analysis . It is not expected to deviate from that initial roadmap. The great disadvantage of this methodology is that you will not be able to see the progress until the end of the project (and it does not allow adding changes that may have occurred during the months of project start-up).
  • Agile Methodology: Usually the Agile methodology uses its Scrum version for ERP implementation. The Agile methodology is committed to making progressive start-ups of the functionality to be implemented, so that the client can start working as soon as possible with the tool and with the knowledge of it, decide how to build the rest of the ERP It is a much more flexible methodology since budget and calendar are set and the requirements form the variable part. This methodology is optimal not to eternalize deliveries and control costs and risks.

Although the two methodologies are popularly known and used, in Triangle for years we opted for and worked with Scrum methodology.

What phases does an ERP implementation have?

In Scrum methodology, the functionality to be implemented is divided into ‘Sprints’, which are small, bootable functional units independently. Each sprint usually lasts between 3 and 4 weeks and allows the client to see the progress of the work. Each sprint typically has the following phases:

  1. Analysis: Once the functionality to be included in the sprint is prioritized, an analysis is carried out to draw the circuit to be started with the customer and the configurations and settings that are derived from each decision . Typically it would be the functional and technical consulting phase.
  2. Training: The purpose of any ERP implementation is that users can work comfortably with the software passed the project. For this reason the formations are of vital importance. Receiving a good training will give users autonomy both before and after startup. We say before, since the users involved in the project must validate the circuits launched and, to achieve this, must have previously received training . In ERP implementations with more than 10-15 users, differentiated training is usually carried out for project key users and non-key users.
  3. Data migration: Depending on the type of boot you do and the circuits that you are going to start up in the ERP, the data you must provide will vary. It must also be differentiated if it is your first ERP startup and you do not have historical data yet or if it is a migration from one ERP to another . Typically, migration of master data, balances and live items to start date is performed.
  4. Validations and tests: Users have to validate throughout the project that both the functional circuits and the data are correct. Your partner must provide you with instructions to perform these tests.
  5. Custom developments: In those options where the ERP standard does not completely meet your needs, custom developments will come into play. You have to be very careful with Don’t abuse customizations. If you need too many, it is possible that you have not chosen the ERP indicated for your business casuistry.When developments are necessary, it especially requires that they be carried out through the latest developments in development and, in addition, that the code of these developments be your property.
  6. Project coordination: It will be essential that there is a person coordinating and managing the project to coordinate agendas, organize resources and ensure the good progress of the project. </ li>
  7. Start-up support: During the first weeks you start working in the production environment it is important that you have a dedicated support so that your doubts and queries are not constantly blocking your work.

How to survive the implementation of an ERP?

What figures are involved in the implementation of an ERP

Various profiles will interact during the implementation of an ERP. Typically you should have a relationship with:

  • Analysts and consultants: are responsible for performing the analysis tasks. They should understand your business casuistry and work circuits to propose optimizations and seek translation in the chosen ERP.
  • Validation support and boot support agents: During validation sessions and boot support, implementation consultants and support team agents will support and resolve your doubts.
  • Project Director: is the figure that ensures the correct progress of the project, prioritizes with you the functionalities to be implemented in each sprint and has the global vision of the entire project. < / li>
  • Developers: in cases where customizations are necessary, developers will intervene to make the code as you need and thus create your functionality.


You may also be interested