A Dynamics AX migration project needs a dedicated internal program owner, typically a senior IT or operations director, supported by a steering committee with executive sponsorship. That person coordinates workstreams across IT, finance, supply chain, and HR while acting as the bridge between day-to-day delivery and board-level accountability. Below, we unpack the specific roles involved, how to structure ownership, and what changes when you reach go-live.
What roles are important in a Dynamics AX migration project?
A Dynamics AX migration project requires several distinct roles to function well: an executive sponsor, a program or project manager, workstream leads from each affected business area, a data migration lead, a test manager, and a change manager. Each role covers a different part of the delivery, and gaps in any one of them tend to surface as delays or quality issues later.
Here is a practical overview of the core roles and what they own:
- Executive sponsor: Owns the business case, removes organisational blockers, and maintains board-level visibility
- Program or project manager: Manages scope, timeline, budget, and cross-workstream dependencies day to day
- Workstream leads (finance, supply chain, HR, IT): Own requirements, process decisions, and user acceptance within their domain
- Data migration lead: Responsible for data quality, mapping, and validation before cutover
- Test manager: Plans and executes testing cycles, tracks defects, and signs off on business readiness
- Change manager: Drives communication, training, and adoption across the organisation
Smaller organisations sometimes combine roles, for example, having one person cover both test management and data migration oversight. That can work if the individual has the bandwidth, but it increases delivery risk. On a Dynamics AX migration of any real scale, these functions are distinct enough that they benefit from dedicated ownership. You can explore program management for ERP transformations to understand how these roles fit together structurally.
Who should own the overall Dynamics AX migration program?
Overall ownership of a Dynamics AX migration program should sit with a senior leader who has both business authority and operational credibility, typically a CIO, IT Director, or Head of Operations. This person needs enough seniority to make decisions, resolve conflicts between workstreams, and hold the organisation accountable to the agreed scope and timeline.
The program owner is not the same as the day-to-day project manager. The program owner sets direction, manages stakeholder relationships at a senior level, and is ultimately accountable for the business outcome. The project manager handles execution. Conflating these two roles is one of the more common structural mistakes in large ERP migrations, and it tends to result in either strategic drift or operational overload.
If your organisation does not have someone with the right combination of availability, ERP experience, and seniority to fill this role internally, that is worth addressing before the project starts, not after the first missed milestone.
Should the migration be led internally or by an external partner?
Most organisations benefit from a combination: internal leadership for business ownership and decision-making, supported by an external partner for programme delivery expertise and hands-on ERP experience. Purely internal teams often lack the specialised knowledge to manage a Dynamics AX migration end to end, while a purely external team lacks the organisational context to drive adoption and sustain change.
The practical question is where to draw the line. Internal ownership of the business case, process decisions, and stakeholder relationships is important because those require organisational authority that no external party can substitute. Delivery roles such as project management, data migration, test management, and cutover planning are areas where external specialists add significant value, particularly when they have done comparable migrations before.
When evaluating an external partner, look for consultants who have worked on real ERP migrations at comparable organisations, not just those who know the methodology. We work on-site and remotely, across the Netherlands, Belgium, and internationally, embedding directly into client teams rather than operating at arm’s length.
What does the executive sponsor actually do in a Dynamics AX migration?
The executive sponsor in a Dynamics AX migration owns the business case, champions the project at board level, and acts as the final decision-maker when the program hits issues that cannot be resolved within the delivery team. This role is active, not ceremonial. A sponsor who only attends monthly steering meetings is not fulfilling the function.
In practice, the executive sponsor does several things throughout the project:
- Secures and protects budget and resources when competing priorities emerge
- Removes organisational blockers that the project manager cannot resolve alone
- Maintains alignment between the transformation and the broader business strategy
- Communicates the importance of the migration to senior stakeholders and business unit leads
- Makes or escalates decisions on scope changes that affect cost, timeline, or business outcomes
On a Dynamics AX migration, the executive sponsor is also the person who sets the tone for change management. If the sponsor is visibly committed, the rest of the organisation tends to follow. If the sponsor is disengaged, change fatigue sets in faster and adoption suffers after go-live.
How should leadership responsibilities shift at go-live?
At go-live, leadership responsibilities shift from project delivery to operational stabilisation. The project manager’s role reduces, the executive sponsor moves into a monitoring function, and business unit leads take on primary accountability for day-to-day system usage and issue resolution within their domains.
This transition is often underplanned. Teams that have spent months focused on delivery suddenly need to operate in a different mode, one that prioritises rapid issue resolution, user support, and process stabilisation rather than milestone tracking. The change manager becomes more important at this point, not less, because this is when adoption either takes hold or starts to erode.
The period immediately after go-live, often called hypercare, typically runs for four to eight weeks depending on the complexity of the migration. During hypercare, the external partner should remain closely involved to resolve technical issues quickly and support the internal team. After hypercare, the goal is a clean handover to business-as-usual operations with the internal team fully capable of managing the system independently.
How Optinus helps with Dynamics AX migration leadership
We help organisations structure and run their Dynamics AX migration from the ground up, covering the roles and responsibilities that are hardest to staff internally. Here is what that looks like in practice:
- Program and project management: We embed experienced program managers who have run real ERP migrations at leading multinationals, managing scope, timelines, and stakeholder expectations across workstreams
- Data migration and test management: We own the technical delivery phases that carry the highest risk, using rigorous As-Is/To-Be analysis and structured testing to protect data integrity before go-live
- Cutover management: We plan and execute the cutover in detail, with real-time monitoring and hypercare included so operational continuity is never at risk
- Change management: We address the human side of the migration, driving genuine adoption rather than just delivering training sessions
- Full-spectrum coverage: We cover our full range of services under one roof, from maturity assessment through to post-go-live support, so there are no handover gaps between specialisms
If you are planning a Dynamics AX migration and want to talk through how to structure the team around it, get in touch with our team for a practical conversation. You can also learn more about what we do and how we work with organisations across Europe and beyond.
