A Dynamics NAV migration project should be owned by a dedicated NAV migration project manager who holds overall accountability for scope, timeline, and budget. This person is typically supported by a business-side owner, an IT lead, and key functional stakeholders from finance, operations, and supply chain. In practice, the most successful migrations involve a clearly defined governance structure rather than shared or undefined ownership. The sections below unpack each role in detail and help you decide how to structure your team.
What roles are typically involved in a Dynamics NAV migration?
A Dynamics NAV migration project draws on a core team of five to seven roles, each covering a distinct area of responsibility. These typically include a project manager, a business owner or sponsor, an IT lead, functional consultants per module, a data migration specialist, a test manager, and a change manager. Together, these roles cover the full lifecycle from design through to go-live and aftercare.
Here is a breakdown of the most common roles and what each one contributes:
- Project manager: Coordinates the overall plan, manages risks and dependencies, and keeps the project on track against scope and budget.
- Business owner / executive sponsor: Provides strategic direction, resolves escalations, and ensures the migration aligns with business priorities.
- IT lead: Oversees the technical infrastructure, system integrations, and environment management throughout the migration.
- Functional consultants: Translate business requirements into system configuration, covering areas such as finance, logistics, and purchasing.
- Data migration specialist: Manages the extraction, cleansing, transformation, and loading of data from NAV into the target system.
- Test manager: Plans and coordinates testing cycles to validate that the new system behaves as expected before go-live.
- Change manager: Prepares the organisation for the transition, focusing on communication, training, and user adoption.
Not every organisation fills all these roles with separate individuals. In smaller migrations, one person may cover both project management and change management. What matters is that each area of responsibility is clearly assigned to someone accountable, with no gaps between specialisms. If you are looking at the full range of ERP transformation services available, this role coverage is a useful checklist for assessing your own team’s readiness.
Who should own overall accountability for a NAV migration project?
Overall accountability for a Dynamics NAV migration project should sit with a single, named project manager who has the authority to make decisions across workstreams. This person must have hands-on experience with ERP migrations, not just general project management credentials. Without a clear owner, responsibility diffuses across teams and decisions slow down at exactly the moments when speed matters most.
The project manager is not simply an administrator. In a NAV migration context, this role involves active risk management, stakeholder alignment, scope control, and real-time problem-solving during critical phases such as data migration and cutover. A strong project manager understands both the technical constraints of the system and the operational realities of the business.
The executive sponsor supports the project manager by providing organisational authority and removing blockers that sit above the project level. However, the sponsor does not run the day-to-day migration. Confusing these two roles is one of the most common governance mistakes in ERP projects. The project manager owns delivery; the sponsor owns strategic commitment.
When should you bring in an external migration specialist?
You should bring in an external Dynamics NAV migration specialist when your internal team lacks hands-on experience with NAV or Business Central migrations, when the project scope is large enough to carry real operational risk, or when the timeline is tight and there is no room for a learning curve. External specialists bring pattern recognition from comparable migrations that internal teams simply cannot replicate without having done it before.
Several signals suggest external support is the right call:
- Your IT team manages day-to-day NAV operations but has never led a full migration or upgrade.
- The migration involves complex data cleansing, custom code remediation, or integrations with third-party systems.
- You are moving from NAV to Business Central and need guidance on what changes in the process and data model.
- Key internal staff are already stretched across existing responsibilities and cannot dedicate sufficient time to the project.
- Previous ERP projects in your organisation went over budget or missed go-live dates.
Bringing in an external specialist does not mean handing over control. The most effective model is a collaboration where external consultants embed alongside your internal team, transferring knowledge as the project progresses. This approach protects you during the migration and builds internal capability for the long term. For organisations based in the Netherlands, Belgium, or internationally, on-site and remote engagement with an experienced partner makes this model practical regardless of location.
What’s the difference between a project manager and a programme manager in a NAV migration?
In a NAV migration, a project manager manages a single, defined project with a clear start and end point, while a programme manager coordinates multiple related projects or workstreams that together deliver a broader business transformation. The distinction matters because NAV migrations often exist within a larger change programme that includes process redesign, organisational restructuring, or parallel system rollouts across business units.
A project manager focuses on delivering the migration itself: the plan, the tasks, the risks, and the go-live. A programme manager operates at a higher level, ensuring that the NAV migration aligns with other initiatives, that dependencies between workstreams are managed, and that the overall business outcome is achieved rather than just the technical deliverable.
For a straightforward NAV to Business Central migration within a single business unit, a project manager is usually sufficient. When the migration is one of several concurrent changes, or when it spans multiple countries, legal entities, or business processes, programme management becomes necessary to maintain coherence and prevent workstreams from working at cross-purposes.
How should responsibility be divided between IT and business stakeholders?
In a Dynamics NAV migration, IT and business stakeholders share responsibility but in distinct areas. IT owns the technical execution: infrastructure, environments, integrations, data extraction, and system performance. Business stakeholders own the process and outcome: defining requirements, validating data, approving testing results, and confirming that the new system supports how the organisation actually works. Neither side can substitute for the other.
A common failure mode is for IT to drive the migration without sufficient business involvement, resulting in a technically successful go-live that does not reflect how people actually work. The reverse is also possible: business teams that are too removed from technical decisions create unrealistic expectations about what the system can deliver and when.
Effective responsibility division looks like this in practice:
- IT responsibilities: Environment setup and management, data extraction and loading, integration development, performance testing, and technical cutover execution.
- Business responsibilities: Process documentation, data cleansing and sign-off, user acceptance testing, training participation, and go-live readiness confirmation.
- Shared responsibilities: Risk assessment, issue escalation, go/no-go decisions, and post-go-live hypercare monitoring.
The project manager’s job is to hold both sides accountable to their respective areas and to facilitate the handoffs between them. When this governance is clear from the start, the migration runs more smoothly and decisions get made faster at every stage.
How Optinus helps with Dynamics NAV migration project ownership
We work with organisations at every stage of a NAV migration, from the initial governance design through to post-go-live support. Whether you need a dedicated NAV migration project manager to lead the full delivery, a programme manager to coordinate across workstreams, or specialist support in data migration, test management, or change management, we cover the complete transformation journey under one roof.
- Project and programme management with consultants who have hands-on experience from real ERP migrations at leading multinationals, not just theoretical frameworks.
- Data migration management using rigorous As-Is/To-Be analysis and structured testing procedures to prevent data loss and errors during the transition.
- Cutover management handled end-to-end, including hypercare and aftercare, so operational continuity is never at risk during go-live.
- Change management that addresses the human side of the migration, driving genuine adoption rather than just delivering training sessions.
- Flexible engagement available on-site and remotely, across the Netherlands, Belgium, and internationally.
If you want to understand where your organisation stands before committing to a migration roadmap, we typically start with a maturity assessment that gives you a clear baseline and concrete recommendations. Explore our ERP transformation services to see how each service area fits into your migration. Or, if you already have a specific challenge in mind, get in touch with us and we will help you work out the right approach for your project.
