Senior ERP Project Manager
Technology
Job Description
Key Responsibilities
\n
- \n
- Lead the end-to-end delivery of the Epicor 10.2 to Oracle EBS R12 migration, from November 2026 mobilization through the August 1, 2027 target go-live and approximately one month of hypercare.
- Build, baseline, and manage the integrated project schedule, critical path, milestones, dependencies, deliverables, resource plan, and project budget.
- Coordinate business and IT workstreams across order management, planning, sourcing, manufacturing, engineering, warehouse and logistics, finance, master data, reporting, integrations, security, testing, training, and cutover.
- Partner with business and IT leaders to clarify scope, define accountable owners, secure resource commitments, and establish practical governance and decision rights.
- Facilitate project kickoff, weekly delivery reviews, leadership updates, stage-gate readiness reviews, and working sessions needed to keep execution on track.
- Maintain disciplined project controls, including risks, actions, issues, decisions, assumptions, dependencies, change requests, and milestone status.
- Drive completion and approval of key project deliverables, including current-state and future-state process documentation, solution decisions, gap dispositions, test plans, cutover plans, training readiness, and operational handoff.
- Lead cross-functional planning for data cleansing, conversion, reconciliation, and validation, including clear ownership and business sign-off.
- Ensure test cycles are planned and executed with entry and exit criteria, business participation, defect triage, readiness reporting, and formal approvals.
- Develop and manage an integrated cutover and contingency plan, including command-center governance, go-live readiness, stabilization, and transition to support.
- Manage external partners and consultants against agreed scope, deliverables, schedule, quality expectations, and commercial commitments.
- Communicate complex project information in clear, concise, actionable terms for executives, project leaders, workstream teams, and site stakeholders.
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Required Qualifications
\n
- \n
- At least 7 years of IT project management experience, including significant responsibility for full-lifecycle ERP implementations in a manufacturing environment.
- Demonstrated success leading a large, cross-functional Oracle EBS implementation or migration. Experience with on-premises Oracle EBS is strongly preferred.
- Strong understanding of manufacturing ERP processes, including order-to-cash, plan-to-produce, procure-to-pay, inventory, warehouse and logistics, and record-to-report.
- Proven experience managing data conversion, application integrations, system and business testing, cutover, go-live, and hypercare.
- Ability to create and manage detailed integrated schedules, identify critical-path impacts, and convert executive milestones into owned workstream plans.
- Strong financial and vendor-management skills, including budget tracking, forecast management, scope control, and partner accountability.
- Excellent facilitation, executive communication, negotiation, and conflict-resolution skills.
- Ability to work effectively with plant leadership, business process owners, functional and technical teams, and external implementation partners.
- Bachelor's degree in Information Systems, Computer Science, Business, Engineering, or a related discipline, or equivalent relevant experience.
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Preferred Qualifications
\n
- \n
- Direct experience migrating from Epicor 10.2 or another legacy manufacturing ERP to Oracle EBS.
- Experience with multi-site manufacturing, inventory organizations, intercompany processes, and complex data-conversion programs.
- PMP or comparable project management certification.
- Experience using enterprise project management and collaboration tools such as Workfront, Microsoft Project, Microsoft Teams, and SharePoint.
- Change-management experience supporting business readiness, communications, training, adoption, and post-go-live stabilization.
\n
\n
\n
\n
\n
\n
