The ERP landscape has shifted dramatically. Cloud-first deployments, AI-assisted configuration, and leaner implementation teams mean the PM you needed in 2020 is not the PM you need today. Here's how to find the right one.
Updated October 2026 with current UK salary and day-rate data from IT Jobs Watch.
ERP project management sits at the intersection of technology, organisational change, and financial risk. A failed ERP implementation doesn't just go over budget — it can destabilise operations, trigger executive departures, and in extreme cases, threaten the business itself. Yet hiring for this role is frequently treated as a box-ticking exercise: check for PMP certification, scan for SAP or Oracle on the CV, shake hands, and hope for the best.
That approach was always flawed. In 2026, it is no longer defensible. The rise of cloud-native ERP platforms, compressed implementation timelines, AI-assisted tooling, and a post-pandemic workforce comfortable working across geographies has fundamentally changed what great ERP project management looks like. The hiring process must keep pace.
This guide is written for both sides of the table: hiring managers and HR partners seeking to fill this critical role, and ERP project managers who want to understand how they should be positioning themselves and what a rigorous, modern hiring process looks like. If you are new to the role itself, start with what an ERP project manager actually does.
Why This Hire Is Uniquely Difficult
ERP project managers are a genuinely rare breed. The role demands a combination of skills that rarely coexist naturally: deep technical literacy, executive-level communication, process redesign expertise, vendor management experience, and the emotional resilience to navigate organisational politics during periods of intense change pressure.
Add to this the platform fragmentation of the modern ERP market — SAP S/4HANA, Oracle Cloud Fusion, Microsoft Dynamics 365, Workday, Infor, NetSuite, Epicor, and a dozen industry-specific players — and you have a talent pool that is broad but thin at the top. An experienced SAP PM with manufacturing domain expertise is not interchangeable with a Dynamics 365 PM who specialises in professional services. These are different skill sets wearing the same job title.
"The best ERP project managers I've ever hired couldn't tell you what a foreign key was. The worst ones could explain database normalisation beautifully and had never once sat in a room with a CFO."
The other hiring challenge is that ERP implementations are long-cycle projects, often running well over a year. This means candidates may have only two or three full implementation cycles in their entire career. A 40-year-old with five full ERP implementations is worth far more than a 35-year-old with fragments of ten.
The 2026 ERP Landscape — What's Changed
Before writing a job description, it's worth grounding yourself in how the market has shifted. The context in which your future hire will operate looks meaningfully different from even three years ago.
Cloud is now the default. On-premise ERP has not disappeared, but the major vendors now steer new implementations to the cloud. Cloud deployments typically involve less infrastructure project work, more configuration and integration management, and a heavier emphasis on vendor SLA governance. Lift-and-shift thinking has been replaced by the expectation that organisations adopt standard cloud processes wherever possible.
Support deadlines are forcing moves. SAP ECC mainstream maintenance ends in December 2027 and Microsoft Dynamics GP support ends in December 2029, so many organisations hiring an ERP PM now are hiring for a migration. Our guide to ERP support deadlines sets out the dates and what they mean for the talent market.
AI is reshaping implementation methodology. The major ERP vendors have embedded AI into their platforms and their implementation tooling. SAP's Business AI capabilities, Oracle's AI Agents, and Microsoft Copilot integration in Dynamics 365 mean that AI literacy is no longer a nice-to-have for ERP PMs. Candidates who have not engaged with this shift in the past 18 months are already behind.
Compressed timelines and leaner teams. The multi-year "big bang" ERP deployment is increasingly being replaced by phased, modular rollouts. This rewards PMs who can deliver value incrementally, manage complex dependencies across concurrent workstreams, and pivot quickly when priorities change.
Integration complexity is growing, not shrinking. Despite the "single platform" promise of modern ERP suites, most enterprise environments involve deep integration with specialist systems — CRM, e-commerce, manufacturing execution systems, payroll, BI tools, and an ever-expanding roster of SaaS applications. Your ERP PM must understand integration architecture at a meaningful level.
The UK Market in Numbers
IT Jobs Watch tracks advertised UK roles. Its latest figures for ERP project managers show demand rising while pay holds flat or slips:
— Permanent ERP Project Manager roles: 42 advertised in the six months to 31 August 2026, up from 11 a year earlier. Median salary £60,000, down 4%, with most roles between £50,000 and £75,000.
— Contract ERP Project Manager roles: 33 advertised in the six months to 10 October 2026, up from 22. Median day rate £500, down from £538, with most between £450 and £611.
— Permanent ERP Manager roles: 141 advertised in the six months to 8 September 2026, up from 52. Median salary £65,000, with the top tenth paying £100,000 or more.
These are small samples, so treat them as a guide to direction rather than precise benchmarks. They still make one point clearly: more organisations are hiring for this role than a year ago, which makes a sharp brief and a fast process more important, not less.
What to Actually Look For
Non-negotiable core skills:
— Full end-to-end ERP implementation experience (not just phase involvement)
— Stakeholder management at senior and executive level
— Budget governance and financial reporting
— Risk identification and mitigation planning
— Organisational change management
— Vendor and implementation partner management
— Business process redesign
— UAT management and go-live planning
— Integration workstream oversight
Emerging skills now actively sought:
— AI platform literacy (familiarity with AI-embedded ERP features)
— Agile and hybrid delivery methodology
— Cloud migration experience
— Data migration governance
— API and integration fluency
Soft skills that separate good from great:
— Executive presence — ability to command a steering committee room
— Constructive challenge — willing to push back on sponsors and vendors alike
— Organisational empathy — reads politics without being paralysed by them
— Narrative clarity — can explain complex programme status in plain language
A word on certifications. PMP, PRINCE2, and SAP PM certifications have their place, but treat them as evidence of commitment to the craft — not as proxies for capability. The most dangerous ERP project managers are those who are brilliant at managing process and documentation and poor at managing people and reality.
The project manager is one role among many on an ERP programme. For how it fits alongside the business analysts, solution consultants, data migration leads and test managers your hire will lead, see Roles on an ERP Project.
Writing a Job Description That Actually Works
Be specific about the platform and version. Don't write "ERP experience required." Write "SAP S/4HANA 2023 Public Cloud implementation experience preferred" or "Oracle Fusion Cloud Financials full-cycle experience required." The more specific you are, the better quality your applicant pool.
Describe the programme, not just the role. How many workstreams? How many business units? What's the budget envelope? What's the implementation partner relationship — is your hire the client-side PM overseeing an SI, or are they the SI-side delivery lead? These distinctions matter enormously.
Specify the seniority of stakeholders. An ERP PM who primarily engages with department heads is a different animal from one who manages a C-suite programme steering committee. Be explicit about the reporting line and the stakeholder map.
Essential job description checklist:
— ERP platform name and version (not just "ERP system")
— Programme scale: budget range, duration, number of sites or entities
— Relationship to implementation partner (client-side vs SI-side)
— Workstream structure and team size
— Seniority of key stakeholders (CFO-level, Board reporting, etc.)
— Industry and domain context (manufacturing, financial services, retail, etc.)
— Hybrid or remote working arrangement and travel expectations
Designing an Effective Interview Process
ERP project management is fundamentally about decision-making under pressure. Your interview process should be designed to surface this, not to reward polished presentation skills and rehearsed answers.
Stage 1: Structured screening conversation (30–45 mins). Walk the candidate through their most recent full-cycle ERP implementation. Press for specifics: What was the original go-live date? Did you hit it? If not, why not, and what did you do? Candidates who generalise or who position problems as "team issues" without describing their own response should give you pause.
Stage 2: Scenario interview (60–90 mins). Present realistic situations your actual hire would face. Cover at least four scenario types:
— Stakeholder conflict: e.g. the CFO wants to defer go-live by 6 months; the CEO wants to keep to plan. What do you do?
— Technical crisis: e.g. 48 hours before go-live, 15% of customer records have failed data migration validation. Walk me through your response.
— Vendor management: e.g. your SI's lead consultant has just resigned and the proposed replacement has no industry experience. What are your options?
— Scope management: e.g. a business unit director is demanding an out-of-scope customisation and threatening to withdraw from the programme. What do you do?
Stage 3: Stakeholder presentation (recommended for senior roles). Ask the candidate to prepare a 20-minute presentation responding to a specific brief. This tests upward communication, ability to synthesise under time pressure, and confidence under questioning.
Red Flags and Green Flags
Green flags — look for candidates who:
— Speak candidly about programmes that went wrong and their own role in it
— Use specific numbers: budget, timeline, team size, data volumes
— Can explain technical concepts in business language without condescension
— Ask sharp questions about stakeholder dynamics and programme governance
— Demonstrate genuine awareness of the human and cultural change dimension
— Reference lessons learned and apply them proactively
— Engage with AI and modern tooling without hype or fear
Red flags — be cautious of candidates who:
— Claim all previous projects "delivered on time and on budget" with no complications
— Struggle to give specifics — vague about budget, timelines, or team structure
— Frame all past problems as caused by others: the client, the SI, the business
— Are unfamiliar with current platform capabilities and AI-enabled features
— Have only ever worked SI-side or only client-side — significant blind spots may exist
— Can't articulate the difference between project management and programme management
"Never hire an ERP PM who hasn't navigated a crisis. The best candidates have scars. The dangerous ones have spotless CVs."
Compensation Benchmarks (UK, 2026)
Advertised pay for ERP project managers has softened over the past year even as the number of roles has grown. The median permanent salary for an ERP Project Manager is £60,000, with most roles between £50,000 and £75,000. Contract roles pay a median of £500 a day, with most between £450 and £611. Broader ERP Manager roles pay a median of £65,000, with the top tenth at £100,000 or more. All figures are from IT Jobs Watch for the six months to August–October 2026.
Pay rises with platform, programme scale and sector, so benchmark against the specific role rather than the averages. Our ERP salary and day rate guide breaks rates down by platform and role, and why ERP consultants are paid so much explains what drives the premium.
Where to Find Strong Candidates
The best ERP project managers are rarely actively looking. They're typically mid-programme, heads down, and not browsing job boards. Your sourcing strategy must reflect this.
LinkedIn — but do it properly. LinkedIn remains the primary channel, but generic outreach performs poorly. Personalise every approach and reference a specific aspect of the candidate's experience that is relevant to your programme. Generic "exciting opportunity" messages are immediately filtered by senior candidates.
Specialist ERP recruiters. Engage genuinely specialist ERP recruitment firms on a retained basis for senior roles, rather than bombarding ten generalist agencies with a contingency brief. Contingency recruiting for niche roles produces volume, not quality.
SAP and platform communities. The SAP Community, Oracle Customer Connect, and the Microsoft Dynamics community forums are active spaces where experienced practitioners engage. Speakers at SAP Sapphire and the Dynamics user group events are often exceptional candidates who are not actively looking.
Implementation partner alumni networks. Former Accenture, Deloitte, IBM, and Capgemini practitioners who have moved to client-side leadership roles bring both delivery discipline and a realistic understanding of what to expect from their implementation partners. This is a highly targeted and often underused talent pool.
Contractor vs Permanent — Getting It Right
A permanent hire brings greater commitment to the business beyond go-live, lower knowledge transfer risk, and lower day-rate equivalent cost. Best suited to phased, multi-year programmes and strategic IT leadership roles.
A contractor brings faster time to productivity, often very high specialist depth in a specific platform or phase, and cost flexibility. Best suited to defined-scope implementations, specific phase gaps, or backfilling permanent team capacity.
For major enterprise programmes, a hybrid model often works well: a permanent Programme Director who owns the long-term outcome, supported by contract PMs who manage specific workstreams or phases.
Onboarding and Retention
Hiring the right ERP PM is only half the battle. Retaining them through the difficult mid-programme phase — when stress peaks and headhunters circle — requires deliberate attention.
A strong onboarding should prioritise early access to key stakeholders over documentation. Within the first two weeks, your new hire needs to be building relationships with the CFO, CIO, business unit leads, and implementation partner leadership — not reading project plans in isolation. Ensure they are empowered to challenge existing decisions from day one.
Salary is hygiene, not motivation. What retains exceptional ERP PMs is the quality of the programme, active executive sponsorship, and genuine professional development opportunity. If your programme has weak governance and an absent executive sponsor, even a great PM will struggle — and the best ones will leave rather than manage a failing programme with their name on it.
The Single Most Important Interview Question
"Tell me about an ERP programme that went badly wrong. What happened, what did you do, and what would you do differently?"
The answer tells you more about a candidate than their entire CV. Listen for self-awareness, decisiveness under pressure, quality of reasoning, and the courage to say what they would genuinely do differently. A candidate who cannot answer this question clearly has either not experienced adversity or is not being honest with you. Neither is a good sign.
Summary: Hiring Checklist
— Define the programme context precisely before writing the job description — platform, scale, phase, stakeholder seniority
— Separate what is essential from what is merely preferred
— Use a structured scenario-based interview, not just competency questions
— Verify full-cycle experience with specifics — push for numbers, dates, outcomes
— Assess AI and cloud platform literacy — this is no longer optional
— Test both technical literacy and executive communication capability
— Check references rigorously — specifically ask whether they would hire this person again to run a large, politically complex programme
— Benchmark compensation against current market rates
— Consider the contractor vs permanent question on its merits, not by default
— Invest in a genuine onboarding — relationships first, documentation second
— Ensure executive sponsorship is active before the PM starts — they cannot succeed without it
The ERP project manager is one of the most consequential hires your organisation can make during a transformation programme. The due diligence you apply to selecting an ERP system — the business cases, the vendor evaluations, the reference visits — should be matched by the rigour you apply to choosing the person who will lead its delivery. Get this hire right, and you give your programme its best chance of success. Get it wrong, and no amount of technology investment will save you.