Post-Go-Live Support Structure: Staffing and Escalation Paths for ERP Migrations

Building a Robust Post-Go-Live Support Structure for ERP Migrations

A well-defined post-go-live support structure is critical for the success of any ERP migration or upgrade. This structure ensures that issues are resolved quickly, business operations continue smoothly, and the new system stabilizes effectively. The recommended approach involves establishing a dedicated support team with clear roles, responsibilities, and escalation paths. This team should include internal IT staff, business process owners, and external vendors or system integrators. The main risks to control include data integrity issues, system performance degradation, user adoption challenges, and integration failures. By proactively addressing these risks through a structured support model, organizations can minimize downtime, reduce operational disruptions, and ensure a successful transition to the new ERP system.

Defining the Support Team Structure

The support team structure should be designed to handle the volume and complexity of issues expected during the post-go-live period. This typically involves a tiered support model, where different levels of support handle different types of issues. Tier 1 support is usually handled by the service desk or help desk, which provides initial troubleshooting and resolution for common issues. Tier 2 support involves more specialized IT staff who handle more complex technical issues. Tier 3 support is provided by the system integrator or vendor, who handle critical issues that require deep technical expertise or access to the core system.

Tier 1: Service Desk and Help Desk

The service desk or help desk is the first point of contact for users experiencing issues with the new ERP system. This team should be well-versed in the basic functionalities of the system and should be able to resolve common issues such as login problems, user access issues, and basic configuration errors. The service desk should also be responsible for logging all issues in a ticketing system, tracking their status, and providing regular updates to users.

Tier 2: Specialized IT Staff

Tier 2 support involves more specialized IT staff who have deeper knowledge of the ERP system and its integrations. This team should be responsible for handling issues that require more in-depth troubleshooting, such as data mapping errors, integration failures, and performance issues. Tier 2 staff should also be responsible for coordinating with Tier 3 support when necessary and for providing regular reports on the status of open issues.

Establishing Clear Escalation Paths

Clear escalation paths are essential for ensuring that critical issues are resolved quickly and efficiently. These paths should define the criteria for escalating issues from one tier of support to the next, as well as the roles and responsibilities of each tier. For example, an issue that cannot be resolved by Tier 1 support within a specified timeframe should be escalated to Tier 2 support. Similarly, an issue that cannot be resolved by Tier 2 support within a specified timeframe should be escalated to Tier 3 support.

Managing the Hypercare Period

The hypercare period is a critical phase in the post-go-live support structure, during which the support team provides intensive support to ensure the stability of the new ERP system. This period typically lasts for a few weeks to a few months, depending on the complexity of the migration and the number of issues encountered. During the hypercare period, the support team should be available on an extended basis, including weekends and holidays, to address any issues that arise.

Defining Hypercare Objectives

The objectives of the hypercare period should be clearly defined and communicated to all stakeholders. These objectives may include reducing the number of open issues, improving system performance, and ensuring user adoption. The support team should track progress against these objectives and provide regular updates to stakeholders.

Monitoring System Performance

Monitoring system performance is a critical aspect of the hypercare period. The support team should use monitoring tools to track key performance indicators (KPIs) such as system uptime, response time, and error rates. Any deviations from expected performance levels should be investigated and addressed promptly.

Coordinating with Vendors and System Integrators

Coordinating with vendors and system integrators is essential for resolving critical issues that require deep technical expertise. The support team should establish clear communication channels with vendors and system integrators, including regular meetings and a dedicated point of contact. This coordination should also include sharing relevant information, such as error logs and system configurations, to help vendors and system integrators diagnose and resolve issues.

Handling Critical Defects and Incidents

Critical defects and incidents can have a significant impact on business operations and must be handled with urgency. The support team should have a well-defined process for handling critical defects and incidents, including immediate escalation, communication with stakeholders, and implementation of workarounds or fixes. The team should also document all critical defects and incidents, including their root cause and resolution, to help prevent similar issues in the future.

Ensuring User Adoption and Support

User adoption is a critical factor in the success of an ERP migration. The support team should provide ongoing support and training to users to help them become proficient with the new system. This may include providing user guides, conducting training sessions, and offering one-on-one support. The team should also gather feedback from users to identify areas for improvement and to address any concerns or issues.

Transitioning to Business-as-Usual Support

The transition from project support to business-as-usual support is a critical step in the post-go-live support structure. This transition should be planned carefully to ensure a smooth handover of responsibilities. The support team should document all processes, procedures, and knowledge gained during the hypercare period and transfer this information to the business-as-usual support team. The team should also provide training to the business-as-usual support team to ensure they are prepared to handle ongoing support requests.

Measuring Success and Continuous Improvement

Measuring the success of the post-go-live support structure is essential for identifying areas for improvement and ensuring continuous improvement. The support team should track key metrics such as the number of open issues, average resolution time, and user satisfaction. These metrics should be reviewed regularly and used to make data-driven decisions about improvements to the support structure.

• Define clear roles and responsibilities for each tier of support.
• Establish clear escalation paths and response times.
• Monitor system performance and address deviations promptly.
• Coordinate effectively with vendors and system integrators.
• Provide ongoing support and training to users.
• Plan a smooth transition to business-as-usual support.
• Track key metrics and use them for continuous improvement.