ERP Project Rescue Staffing for Stalled Implementations
Independent contract consultants who recount what your partner actually finished, then stay on billing through go-live.
Reported86%Verified31%Same project, same week. Composite example.
ERP project rescue staffing from KORE1 puts independent contract consultants into a stalled Dynamics 365, SAP, Oracle, Epicor, Acumatica, Sage or Infor implementation, and keeps them on billing through go-live and hypercare.
Last updated: October 3, 2026
- This page
- An implementation that hasn’t gone live, where the partner has stalled, shrunk the team or walked out, on any of the platforms above.
- Not this page
- A NetSuite project goes to our NetSuite consultant practice. A healthy build that only needs bodies for cutover weekend is go-live and hypercare staffing, and a system that is already live and needs tuning is ERP optimization work.
Most stalled projects don’t look stalled from the steering committee. That’s the trap. The status report still comes in on Friday. The percentages still go up every week, just slower than they did in the spring, and the go-live date has moved twice without anybody in the room ever using the word late.
Then the partner rotates its senior functional lead onto a bigger account, or the change orders start arriving faster than the deliverables. Or both. That’s when the CFO calls. KORE1 has staffed technology projects since 2005, and the people who take these projects over come from our ERP consultant staffing bench, on contract, with no reseller relationship or licence margin to protect.
ERP Project Rescue Starts With a Recount
Here’s the last report a partner sent before a rescue team arrived. Outline is what it claimed. Green is what survived two weeks of somebody opening each item and running it.
Weekly status report, week 31
Prepared by the implementation partner. Overall status On track
Reported completeVerified in the recount
- Finance (GL, AP, AR) On track 9580 Configured and tested. Against the sample chart of accounts from week two, not yours.
- Inventory and costing On track 9045 Standard costs loaded. Nobody has run a cost roll with real bills of material.
- Production On track 8530 Routings exist for 40 of roughly 1,900 manufactured items.
- Data conversion On track 8020 The scripts ran once, in a sandbox, against a March extract. Nothing was reconciled.
- Integrations On track 7525 Inbound EDI orders work. Invoices, ship notices and the 3PL feed are specs, not code.
- Reports and forms On track 7035 Financial statements are fine. Invoice, pick ticket and packing list layouts were never started.
- Testing On track 9015 Test scripts are written. The partner’s own consultants executed them, not your users.
- Cutover plan On track 1000 A one-page template with your company’s name typed into the header.
86% complete, as reported31% complete, as verified8 of 8 workstreams on track
Nobody lied on that report. It counted what was built, not what was proven.
Partners measure percent complete by configuration done and objects delivered. A controller measures it by whether last month would close. Different numbers. Those numbers drift apart quietly for months, and a rescue is mostly the moment somebody insists on the second one.
So the first two weeks belong to the rescue lead. They open every row and run it with your data, which is slower than reading the partner’s deck and a lot less pleasant for whoever wrote it. It has to be somebody independent, because a replacement team from the same partner ends up grading its colleagues’ homework and a new partner is usually hoping to sell you a fresh implementation, and neither is in a hurry to publish 31%. Somebody has to.
Get These From the Old Partner Before They Leave
Most of what a rescue needs is already yours on paper. You paid for it in the first two invoices. In practice it sits in the partner’s tenant, the partner’s repository and on three consultants’ laptops, one of whom left in June, and it’s far easier to collect while everyone is still being polite.
- Admin access, in your nameEnvironments, the code repository, the integration platform. The classic miss is a sandbox sitting in the partner’s own cloud subscription, which quietly disappears with their billing.
- Source codeFor every extension. A compiled package installs fine and can’t be fixed by anyone but its author, which is an odd position to be in with your own invoicing logic.
- Configuration exports and design documentsThen ask who chose the costing method. If nobody can point to a page, that decision gets made again in week three. Properly.
- Conversion scripts and the field mappingPlus a copy of the legacy extract they last ran against, if it still exists anywhere.
- The defect logClosed items too. Especially the ones closed as “works as designed.”
- Test scripts and evidenceResults and screenshots. A script with nothing attached is a plan, not a test.
Check the licences too. If they were bought through that partner, moving them is a separate conversation with the publisher, and starting it during the recount beats finding a renewal date in the middle of UAT.
Where a Stalled ERP Implementation Hides
Every platform keeps unfinished work in a different drawer. A rescue lead who has run your platform before knows which drawer to open first.
| Platform | Where the partner’s work lives | What the rescue lead opens first |
|---|---|---|
| Dynamics 365 Finance and Supply Chain | X++ extensions in an Azure DevOps repository, data entities for conversion, environments in Lifecycle Services or the Power Platform admin center | Who owns the DevOps project and the environments |
| Dynamics 365 Business Central | AL per-tenant extensions and configuration packages | Whether you hold the source for every extension, or only the compiled .app file |
| SAP S/4HANA | Transports, plus the fit-to-standard decisions from the Explore phase, often tracked in SAP Cloud ALM or Solution Manager | The open transport list, and which gaps were closed with custom code instead of configuration |
| SAP Business One | User-defined fields and tables, add-ons, Service Layer or DI API integrations | Which add-ons are licensed through the partner |
| Oracle Fusion Cloud ERP | Setup in Functional Setup Manager, FBDI loads, integrations in Oracle Integration | The configuration export, and which quarterly update the testing actually ran on |
| Epicor Kinetic | BPMs, BAQs, Application Studio layers, DMT load files | The BPM list, because logic hiding in a BPM never shows up on a status report |
| Acumatica | Customization projects, import scenarios, generic inquiries | Whether the published customization project matches source you can open |
| Sage Intacct and Sage X3 | Intacct dimensions, Smart Rules and Platform Services objects, or X3 specific developments | The dimension structure, since every report and every approval leans on it |
| Infor CloudSuite | ION workflows and BODs, Mongoose extensions on CloudSuite Industrial | The ION connection points, and who holds tenant administration |
Platform depth matters more than rescue experience in general. By a lot. When the recount turns up a gap, we staff it from the bench that knows that product, whether that’s Dynamics 365 consultants, S/4HANA consultants, Oracle Fusion specialists, Epicor consultants, Acumatica consultants or Sage Intacct consultants.
Re-Baselining a Rescued ERP Project
Once the true number exists, the plan gets rebuilt around it. New dates. New scope. New budget.
Three rules keep the second plan from drifting the way the first one did.
- Restate the scope every timeThe agreed scope is everything originally signed plus each approved change, written out in full on each new change order. Nobody reconstructs it from email.
- Split rework from waitingEvery slipped week gets labelled one or the other before anyone talks about money. That habit ends most change-order arguments before they start.
- Never bundle changesEach one gets assessed on its own, so a big change can’t ride through inside a small one.
Those three come straight out of the change control process Foretopia uses on regulated ERP work, written by Colin Boothe, its CIO and a KORE1 contributor. The same documents put specialist delivery at about $215 an hour blended in 2026, with the independent validation lead billed higher, around $275. The rule on slipped weeks is one sentence long. Here it is.
“Waiting time attracts schedule relief; only rework attracts cost.”
Starting over looks cleaner. It almost never is. Birmingham City Council’s Oracle Fusion system went live in April 2022 against an estimate of about £20 million, and the rebuilt version didn’t go live until August 2026, by which point The Register reports the program had cost £144.4 million. Government-appointed commissioners, reporting in January 2025, still called the rebuild stabilised but fragile, almost three years after the first go-live.
$215
an hour, blended, for specialist ERP partner delivery in 2026
$85 to $220
an hour, KORE1’s published contract range for ERP consultants
17 days
on average, from search kickoff to a KORE1 IT hire
92%
of KORE1 hires are still there after twelve months
Partner rate from Foretopia’s 2026 delivery benchmarks. Contract range from KORE1’s ERP rate tables. Time to hire and retention are from KORE1’s own placement data.
Four Seats a Rescue Puts Back on the Project
A stalled project rarely needs a whole new team. It needs the four seats the partner thinned out first.
Owns the true number
Rescue lead
Runs the recount, rebuilds the plan, and chairs every change decision until hypercare ends.
ERP project manager staffingOwns the process
Functional leads
Finance, supply chain or manufacturing leads who redo design decisions the business never actually signed.
ERP program team staffingOwns the data
Conversion developer
Rewrites the load scripts and reconciles every mock conversion against the legacy trial balance.
ERP data migration staffingOwns the interfaces
Integration developer
Finishes the EDI, ecommerce, warehouse and payroll feeds that were still a spec at week 31.
Contract staffing
Our ERP project manager page puts contract program leads at $90 to $175 an hour in 2026, with rescue engagements at the top of that band. Functional and technical rates follow the platform. SAP runs $130 to $220 an hour on our published tables, Dynamics 365 runs $85 to $165, and the scarce combinations, like a manufacturing costing lead who has also written conversion scripts, sit at the high end of each.
None works for a partner. They’re independents on a KORE1 contract, so nobody above them resells licences or earns more when the timeline slips.
How an ERP Rescue Team Stays Through Go-Live
Four stages. The order isn’t negotiable, and skipping the first is exactly how a second plan ends up looking like the first one.
- RecountTwo weeks, roughly. Every workstream gets opened and run with your own data instead of the demo company, and the verified number goes to the steering committee even if somebody in the room signed off on the old one.
- Take custodyAccess, code, scripts and documents move into your name while the old partner still answers email. Some partners stay on in a smaller role after that. Plenty don’t, and that’s fine.
- Re-baseline and staff the gapsThe plan gets rebuilt on the verified number. Then we fill whichever functional and developer seats the recount says are empty, which is rarely all of them.
- Run it to hypercareSame people through testing, conversion, cutover and hypercare. They come off the project when the ticket queue goes quiet. Not on a date somebody picked in March.
If you’re on Dynamics 365, Microsoft’s Success by Design framework makes the Solution Blueprint Review and the Go live Readiness Review mandatory, and a rescued project should sit both again even though the partner probably ran them already. SAP projects get the same treatment through a second round of fit-to-standard on whatever the recount flagged.
Billing is hourly through KORE1, and if a stage has a fixed scope and you’d rather buy the outcome, we write that piece as a statement of work. Hypercare itself is a well-worn handoff to our go-live support team, and when the rescue lead turns out to be the ERP owner you never hired, a direct hire conversion is on the table.
Common Questions
What is ERP project rescue?
ERP project rescue means taking over an implementation that has stopped converging, establishing how much of it really works, and rebuilding the plan so it can go live. The work is mostly verification and decisions. Technology problems are usually the smaller share.
Should we fix our ERP implementation or start over?
Fix it, in most cases. A restart only makes sense when the software itself was the wrong choice for how the business runs, and a recount will tell you that within two weeks. Restarting throws away whatever the recount verified, and the Birmingham Oracle program shows how long a rebuild can take.
How much does ERP project rescue cost?
$85 to $220 an hour is the 2026 range we publish for contract ERP consultants, and a rescue lead bills close to the top of it. Four of them full time still come in under a partner’s blended $215, though not by as much as people hope. What actually moves the budget is the rework the recount finds. Plan for it.
Can we replace our implementation partner partway through?
Yes, and partners rotate out of stalled projects more often than any of them would admit on a sales call. Before the last invoice, get admin access, source code, configuration exports, conversion scripts, the defect log and test evidence moved to you. Licences bought through that partner are a separate thread with the publisher. Start it the same week.
How fast can you staff an ERP rescue team?
17 days is KORE1’s average for an IT hire, and the rescue lead is the seat we fill first. We hold the other seats until the recount says which ones you need, because hiring a costing lead for a project whose real hole is EDI is an expensive way to feel busy. Infor plus manufacturing costing is the slow combination.
Do the rescue consultants stay through go-live?
Staying is the reason to hire them on contract instead of buying another fixed bid. The people who recount the project are the ones who test it, convert it and answer the phone during hypercare. They roll off once the ticket queue goes quiet, not before. Every so often one of them stays on as the ERP owner you never got around to hiring.
Do you rescue NetSuite implementations too?
Different bench, same method. NetSuite rescues go through our NetSuite practice, because the places a stalled NetSuite build hides, mostly SuiteScript, saved searches and workflows, need people who live in that product every day.
Forward the Last Status Report
The most recent one your partner sent is enough. Any format works. Tell us the platform, the original go-live date and the current one. We’ll tell you which rows we’d recount first and who we’d put on them.
Forward Your Last Status Report →Or call 949-706-6990
