There are three types of Deployment strategies usually adopted by vendors:

  1. Big Bang Approach
  2. Phased Rollout Approach
  3. Parallel Rollout Approach

We usually adopt Phased Rollout approach mainly to minimized the cost and risk.

Phased Rollout Approach

In this approach, the ERP deployment is divided into a series of phases over time. It helps mitigate the risk of global failure because only a chosen activity of the firm is concerned with the lunch of the new system.

The phased rollout might be done by module, Business Unit or location.

Module wise

This is the most common phased approach. The ERP is deployed by modules, one by one. We do not recommend start with core business functions as the challenge of this approach is to guarantee the continuity of daily operations. However, we recommend to start with modules that have the minimum dependency with other modules as accounting or payroll modules.

Business Unit wise

This approach is most used by large organizations. The implementation is realized to a business unit at a time ensuring only that business functions related to the BU are deployed. This helps the team to learn smoothly and gain efficiency for subsequent phases.

Location wise

Phased rollout by location is appropriate for firms with multiple locations or subsidiaries in the world. For instance, you may choose a subsidiary as deployment pilot by implementing 80% of common business processes used by other subsidiaries. This approach helps validate business processes in one location. Thus, subsequent deployments in other locations will be more efficient and smoother because lessons learned that are gathered from the pilot location will be applied throughout the rest of subsidiaries.

In addition, this approach reduces considerably the cost and time allowed for the implementation phase and testing steps in the project. Finally, specific needs of each geography are deployed later.


  • Less risky than the big bang approach.

  • In case of unforeseen failure, there is no cascading impact on others.

  • Limited scope helps support team to be more efficient.

  • Phased rollout allows gather experience from previous deployments and lessons learned to be more prepared for subsequent phases.

  • Learning curve is smoother for employees to get familiarized with the new system.