Last updated: November 20, 2026
By Devin Hornick, KORE1
An ERP project manager job description has to name the platform, the program phase, and who signs change orders, with 2026 base pay of $105,000 to $195,000 depending on scope. A generic project manager posting names none of the three. The copy-ready template sits in the middle of this page, with swap-in blocks for each phase.
Pull up the last three ERP project manager postings you can find and count the platform names. Usually the count is zero. Sometimes it’s five suites joined by slashes, which comes to the same thing.
I’m Devin Hornick, a co-founder of KORE1, and I’ve watched a lot of ERP programs lose a quarter to a seat that was posted as something else. The posting said project manager, while the program needed somebody to hold an integrator to a signed statement of work, decide which of the incoming changes were cost events, and run a cutover weekend that nobody had rehearsed. Three different people, really. Which one are you hiring?
KORE1 runs an ERP implementation project manager staffing desk and we bill a fee when a search closes, so weigh what follows accordingly. The template is yours either way. If the seat never touches an ERP program, our project manager job description template fits better, and migrations and infrastructure work have an IT project manager version. This page covers ERP program scope and nothing else. The interview side lives in our guide to hiring an ERP project manager.

One Title, Four Different Jobs
ERP project management changes character four times across a program. The person who thrives in requirements workshops gets restless at cutover. The cutover specialist, dropped into twelve weeks of fit-gap sessions, would tell you by week three that they’re in the wrong building. Neither one is flawed. It’s a single title covering four jobs, and a posting that tries to cover all four attracts generalists and repels the specialist you actually need.
Pick the phase the program will be in on the day the new person starts. Then lead with the sentence that matches it. Just one.
| Phase on Day One | First Sentence the Posting Should Carry | What Breaks Without It |
|---|---|---|
| Selection and requirements | “Run requirements and vendor evaluation for [shortlist], ending in an approved, baselined specification.” | Applicants are build and cutover people who leave when the workshops start dragging |
| Design and build | “Hold [integrator] to a signed statement of work through design, build, and integration testing.” | Reads as coordination, so nobody can tell who decides what counts as a change |
| Testing and cutover | “Own the go or no-go for the [month] cutover, including mock loads and the rollback call.” | The weekend work surfaces at offer stage and the finalist withdraws |
| Hypercare and steady state | “Carry the first 90 days after go-live and hand a documented system to whoever inherits it.” | A seat that is really triage and handover gets filled by someone expecting program work |
Hypercare is the row people get wrong most. Different job. Triage and handover is real work, but it isn’t an implementation PM job, and whoever takes it expecting a program to run tends to leave after a few months of wondering where the program went.
Some programs need a different seat altogether. Program manager, cutover and go-live lead, data migration PM, change management lead, and PMO and governance lead are all separate searches on our desk, and our ERP program team staffing page shows how they fit around each other. If the posting is secretly for the people who build the system, read ERP implementation team structure before you write another word.
Swap These Lines Before You Paste
Most ERP postings start life as a generic PM posting with the letters ERP dropped in somewhere. You can spot them from across the room. These are the lines that give it away, and what belongs in their place.
| Generic Line | What an ERP Posting Says Instead |
|---|---|
| Manage cross-functional stakeholders | Name the executive sponsor, the integrator’s PM, and the finance and operations leads who sign off on design |
| Lead Agile ceremonies | State the lifecycle, phase-gated with the vendor’s methodology or hybrid, in one sentence |
| Manage project budget | Give the number under management and say whether it includes partner fees, licenses, and backfill |
| Strong communication skills | Writes the steering committee update and the change order summary, and will show a redacted sample |
| PMP required | PMP preferred, required only if a client contract or an auditor demands it |
| Fast-paced environment | The cutover weekend, its dates, and whether it’s on site |
| Technical aptitude | Can read an integration inventory and challenge an estimate. Does not configure anything. |
Look at what the right-hand column has in common. Every cell is a fact somebody on your side has to go and find out, usually by walking down the hall and asking a finance director who would rather not say. That’s the point. Uncomfortable, and useful. If nobody can fill in “the number under management,” you’ve learned something before the first interview instead of after the third.

ERP Project Manager Job Description Template
Copy the block, replace every bracket with something true, and delete the italic notes before posting. It’s written for a client-side seat, meaning the PM works for you and not for the integrator. Say that out loud in the posting, because candidates ask. Every time.
Job Title: ERP Project Manager [Senior ERP Project Manager above $135K, ERP Program Manager above $165K. Title deflation costs you applicants.]
Platform and Edition: [NetSuite, SAP S/4HANA, Dynamics 365, or Oracle Fusion, plus the release] [One platform per posting.]
Implementation Partner: [Integrator name, or “selection under way”]
Program Phase on Day One: [Requirements / Design and build / Testing and cutover / Hypercare]
Go-Live Target: [Month and year, and whether it moves for quarter-end]
Budget Under Management: [Total, and whether it includes partner fees and licenses]
Location: [City, State / Remote / Hybrid, and which days]
Employment Type: [Contract / Contract-to-Hire / Full-time]
Reports To: [CFO / COO / CIO / Transformation Sponsor]
About the Role
We are hiring an ERP project manager to represent [Company] on our [platform] implementation, from [current phase] through [end point]. You work for us, not for the integrator. You own scope, schedule, budget, and the change log, and you decide in writing which changes touch scope or cost before anyone signs. You will not configure the system.
What You Will Own
- The change log, including who classified each change, why, and who approved it
- Every change order from [integrator], reviewed on our side before [executive sponsor] sees it
- The baseline. Approved requirements, signed design, and the date each was frozen.
- The integration inventory, with volumes tracked against licensed limits
- Cutover readiness, meaning mock loads, the go or no-go criteria, and the rollback call [delete if the program is still in requirements]
- The steering committee update, in plain language, including the weeks the news is bad
What We Need to See
- [4+] years running ERP implementations from the buyer’s side, with [two] full lifecycles on [platform family]
- A change log or change order you managed, redacted however you need
- Enough technical depth to read an integration inventory and question an estimate
- Time spent holding an integrator to a statement of work when it was uncomfortable
- Writing that executives read voluntarily
Nice to Have
- PMP or PMI-ACP [keep it here unless a client contract or auditor forces it into requirements]
- Experience on the integrator side. People who have sat across that table negotiate better statements of work.
- Depth in [month-end close / manufacturing / distribution / life sciences]
Compensation
$[105,000] to $[135,000] base, or $[95] to $[120] an hour on contract, depending on scope and level, plus [benefits summary]. The bands behind these numbers are in the pay section below.
Then paste in the block that matches your phase, under What You Will Own. One block. Pasting all of them is how you get a posting that describes four people.
Block A, Requirements and Selection
- Authors requirements as individually numbered, testable statements
- Runs vendor demos against our scripted scenarios, never the vendor’s favorites
- Drives approval and baseline of the specification before the build is priced firm
Block B, Design and Build
- Classifies every change after baseline as no effect on scope, cost, or schedule, as affecting one of them, or as touching a validated state, and records the reasoning next to the outcome
- Confirms which revision of the vendor’s documentation each estimate was built on
- Keeps sandbox and integration testing on a published cadence
Block C, Testing and Cutover
- Schedules mock cutovers and data migration dress rehearsals, then reports the honest results
- Owns the written go or no-go criteria, agreed before anyone is tired
- On call for the cutover weekend of [dates]. Our ERP cutover plan template shows the task list this seat runs.
Block D, Hypercare and Steady State
- Runs triage through [30 / 60 / 90] days, using a plan like our ERP hypercare plan template
- Transfers knowledge to the named owner of each module
- Plans regression for every vendor release, not just the first one
Add-On, Regulated Environments
- Has worked under a formal validation lifecycle, GAMP 5 or equivalent
- Keeps the person who assesses a change separate from the person who implements it
- Names the quality approver for validated changes, in writing, at kickoff
What to Print for Pay in 2026
ERP project managers earn $105,000 to $195,000 in base pay in 2026 and $95 to $175 an hour on contract, with the top of each band reserved for multi-entity rollouts and validated environments.
For a floor, the Bureau of Labor Statistics’ May 2025 occupational wage data puts project management specialists at a $102,320 median and a $110,740 mean across every industry. That’s the floor of the market. It isn’t the market. Public salary sites disagree with each other on this exact title by $24,000 to $30,000 between their averages, depending on which sites you read, and our hiring guide and salary guide walk through the sources one by one. None of them can see the difference between a lead on a single-entity finance rollout and someone carrying a multi-country program.
| Level | 2026 Base Range | Contract Rate | What Moves It to the Top |
|---|---|---|---|
| Mid-level implementation PM | $105,000 to $135,000 | $95 to $120 per hour | Two full lifecycles on one platform family |
| Senior ERP PM | $135,000 to $170,000 | $120 to $150 per hour | Multi-entity rollout, data migration ownership |
| ERP program manager | $165,000 to $190,000 | $145 to $165 per hour | Several workstreams, third-party vendors, an executive steering committee |
| Regulated-environment PM | $150,000 to $195,000 | $140 to $175 per hour | Has lived through an inspection and can defend a traceability matrix out loud |
Pick one currency per posting. An annual figure suits the direct hire version and an hourly figure suits contract staffing, and a posting that prints both reads like it hasn’t decided what it’s buying. Our contract rate card carries the hourly side across ERP and finance roles, and the salary benchmark assistant will check a specific city in about a minute.
One more reason to print the range. If the seat is remote, a Washington resident can apply, and Washington’s Department of Labor and Industries says in Administrative Policy ES.E.2 that employers must disclose a wage scale or salary range on postings for remote work that a Washington-based employee could perform. Saying you won’t accept Washington applicants doesn’t get you out of it. Colorado, California, and New York have similar rules, and a remote ERP seat reaches all four. Plan for that.

Three Lines That Make Strong Applicants Lean In
Here’s a benchmark engagement, details changed and the buyer left unnamed. A mid-market pharma manufacturer asked for bids on a NetSuite integration, and its request pointed bidders at a revision of the vendor’s interface specification more than three years old. A newer revision sat in the same data room. It had closed several of the manufacturer’s own open design questions. One bidder noticed, costed against the new one, and said so on page two. The rest priced a design around gaps that no longer existed. Nobody had told them.
That’s the first line worth printing. The PM confirms which revision of the vendor’s documentation every estimate was built on. Anyone who has been burned will read it twice. Good.
Second, call volume. The same manufacturer held a licensed allowance of 130,000 API calls a year. A design that touched the API for every unit shipped would have burned roughly 1.35 million, about ten times the allowance, while a design that batched by document used under a quarter of it. Arithmetic, not judgment. It’s the sort of arithmetic a PM should be able to ask a partner for in week two, and “tracks integration volumes against licensed limits” is a duty that tells the right candidate somebody here knows the question exists.
Third is the line almost nobody writes. When a change order is raised because the client’s own information turned out to be wrong, or because a third party was late, the written process we benchmark against separates rework from waiting, so that waiting earns schedule relief and only rework earns cost. A PM who has never had to draw that distinction tends to let idle time get billed as rework, quietly, one small invoice at a time. Expensive habit by month seven.
None of this is exotic, and all of it is invisible in a posting that says “manage cross-functional stakeholders,” which is the posting most programs are still running on the day the partner’s statement of work gets signed.
Name the Suite and the Deadline
The platform line does more work than any other. A NetSuite posting should name the release the program targets, since NetSuite ships twice a year and every regression plan has to absorb both. A SAP posting should say whether the program is a brownfield conversion from ECC or a greenfield build, because SAP’s own maintenance strategy page says mainstream maintenance for SAP Business Suite 7 core applications runs until the end of 2027, followed by optional extended maintenance until the end of 2030. That date shapes the calendar whether anyone likes it or not. Dynamics 365 and Oracle Fusion postings should say whether the rollout is a single-entity finance deployment or multi-entity with supply chain attached, because those are different pools of people. Same title. Different hires.
Already past a missed milestone? Then the posting is a different one, and our ERP project rescue staffing page is where that conversation starts, usually with a candidate who has already taken over a program that was behind schedule.
Once the posting is out, the next problem is the screen. Our ERP project manager interview questions cover that stage, from the first call to the offer.
Before You Post It
One posting for SAP, NetSuite, and Dynamics, or three?
Write one posting per platform family. The governance skills transfer between suites, but a candidate decides in about ten seconds whether the posting names their suite.
If you truly would hire from any of them, write one posting with a clear primary platform and say the others are acceptable, while naming the one you’d choose if all four candidates walked in on the same Tuesday. The version with five logos and no preference gets applicants who have touched none of them in earnest. Slashes aren’t a strategy. Pick a primary.
How many go-lives should the posting require?
Two full lifecycles on the same platform family for a mid-level seat, plus at least one cutover the candidate personally ran. Asking for five go-lives shrinks the pool without improving the hire.
Count lifecycles, not go-lives. A candidate who has taken one program from requirements through hypercare has seen more than someone who joined four programs at the cutover weekend and left on Monday without ever seeing the data migration go wrong.
Does the cutover weekend belong in the posting?
Yes, with the dates if you have them. Candidates withdraw at offer stage when they discover quarter-end weekends were part of the deal.
Say whether the work is on site, how many weekends it covers, and what the comp time looks like afterward, because the candidate who has done this twice is already running that math in their head. It reads as honest, and it filters in the person who has already done it twice and doesn’t flinch. Simple.
Who should the ERP PM report to?
Whoever owns the budget and has the standing to overrule the integrator, which is usually the CFO or COO on a finance-led rollout and the CIO on a platform consolidation.
A PM who reports to a mid-level IT manager can’t tell an executive sponsor no, and a program where nobody can tell the sponsor no tends to learn about its overruns at the steering committee in month eight. Print the reporting line. Strong candidates read it as a measure of how much the program is allowed to hear the truth. Believe them.
Annual salary or hourly rate, which one goes on the posting?
Whichever matches the engagement. Annual for direct hire, hourly for contract, and never both on the same page.
Contract rates for this work run $95 to $175 an hour in 2026 depending on level and environment, and the ERP consultant hourly rates breakdown shows the neighboring seats. Contract-to-hire needs both numbers stated separately, with the conversion terms, so the candidate can see what the seat pays today and what it pays after conversion.
We posted six weeks ago and got two hundred applicants, none usable. Now what?
Rewrite the first two lines before you spend another dollar on boards. The platform and the program phase belong there, and a generic opening is why the wrong two hundred showed up.
Our average time-to-hire across IT roles is 17 days, and the hiring guide puts a properly scoped ERP PM search at three to six weeks. Searches that drift past that are usually still running the original posting. Check yours. Bring it to a recruiter and the rewrite is often the whole conversation.
We’ve placed technical and program talent since 2005 and we track retention closely, since filling the same seat twice helps nobody, so here is where it stands. Twelve months on, 92% of placements are still in seat. The template above is close to what our recruiters use on an ERP intake call. Take it.

