Some companies search for an ERP fixer because they know the project is in trouble, even if they are not sure what kind of help they need. What they know is that the project feels stuck. The implementation may be behind schedule. Costs may be increasing. Business users may be losing confidence. The partner may be struggling to explain the path forward. Executives may be asking whether the problem is Microsoft Dynamics 365, the implementation approach, the project team, or a combination of all three.
When a implementation needs a fix, the first question should not be whether to abandon the software. The better question is whether the implementation partner, governance model, scope, design decisions, and project execution are still aligned to the business outcome. In many cases, the software decision has already been made. The company has selected Dynamics 365. The license path is in motion. Internal teams have invested time in discovery, design, and planning. The decision now is whether the current implementation structure can deliver, or whether the company needs to reset the project and select a new partner who can lead the work with more discipline. That is where ERP project recovery and partner replacement become critical.
Why the software may not be the real problem
When an ERP implementation is off track, it is easy for frustration to turn toward the system. Users say the software does not fit. Leaders question whether the original ERP decision was wrong. The implementation partner points to scope, data, decisions, or change management. The client points to missed expectations, unclear design, weak communication, or a lack of practical industry understanding. Sometimes the software is truly a poor fit. But often, the larger issue is how the implementation has been structured and led.
Dynamics 365 Finance and Supply Chain is a broad and capable platform. That is part of its value, but it also creates risk. A flexible system still needs the right implementation leadership. It needs clear requirements, practical design decisions, strong data discipline, integrated testing, realistic cutover planning, and client-side governance that keeps the project grounded in how the business actually operates.
When those pieces are weak, the project can look like a software problem even when the real issue is execution.
Signs a Dynamics 365 implementation may need recovery support
Not every difficult project needs a partner change. ERP implementations are complex, and every project has pressure points. But there are warning signs that should be taken seriously.
Leadership cannot clearly explain what has been completed, what remains, and what decisions are blocking progress.
The partner relies heavily on methodology language but cannot translate the plan into practical next steps the business understands.
Key design decisions are unclear, undocumented, or repeatedly reopened.
Requirements, gaps, configurations, integrations, and test scenarios are not traceable.
The same issues appear in status meetings week after week without resolution.
Business users are losing confidence because the solution does not reflect real operating scenarios.
The project team is preparing for go-live without enough evidence that end-to-end processes, data, integrations, reporting, roles, devices, labels, scanners, printers, or site readiness have been tested.
Commercial assumptions have changed, but the client does not have a clear view of the full cost to finish.
At that point, the company may not simply need another project manager. It may need an independent review of what is broken, what is recoverable, and what type of partner is needed to move forward.
Partner replacement is different from a normal partner selection
A normal asks who is best equipped to implement the system. A replacement partner selection asks a harder question. Who can step into an active or partially completed implementation, understand what has been done, separate good work from risky work, reset the plan, regain business confidence, and finish the project without creating unnecessary rework? That is a different skill set.
The replacement partner needs to understand Dynamics 365, but product knowledge alone is not enough. They also need recovery judgment. They need to know how to assess prior decisions, review configuration, evaluate data and integrations, challenge assumptions, and determine where the project should continue, pause, redesign, or simplify. They also need to work well inside a client-side governance model. A recovery project cannot succeed if the new partner simply takes control and asks the business to trust the process again. The client needs transparency, decision rights, and a clear system of record for what is being corrected and why.
Start with a project recovery assessment
Before selecting a replacement partner or signing a new implementation statement of work, John Hannan LLC usually recommend a structured recovery assessment with a fact-based view of the project. A recovery assessment should look at several areas:
Project scope and original business objectives
Current design decisions and open gaps
Requirements and whether they are still valid
Configuration completed to date
Customizations, extensions, and ISV assumptions
Integration design and ownership
Data migration status and reconciliation approach
Testing strategy and real end-to-end scenario coverage
Reporting and analytics expectations
Change management, training, and business readiness
Cutover planning and go-live risk
Partner staffing, governance, and commercial assumptions
Leadership needs to know what is working, what is at risk, what should be corrected, what decisions are needed, and whether the current partner can still deliver. If the answer is no, then the company is ready to run a focused replacement partner selection.
What a replacement Dynamics 365 partner must prove
When selecting a new Dynamics 365 implementation partner for a recovery situation, John Hannan LLC want to see evidence in several areas.
Industry and operating model understanding
The partner should be able to speak in the language of the business, not just the language of Dynamics 365. For a distributor, that may include order-to-cash, pricing, rebates, inventory visibility, warehouse movement, counter sales, shipping, EDI, eCommerce, tax, returns, and multi-entity reporting. For a manufacturer, that may include planning, scheduling, shop floor execution, quality, traceability, outside processing, costing, procurement, inventory, and production reporting. The partner should understand the operating realities that created the project risk in the first place.
Recovery experience
A recovery partner needs to show more than successful greenfield implementations. They should be able to explain how they have taken over difficult projects, assessed prior work, reset governance, managed client concerns, and rebuilt momentum. Ask how they approach a project that is already in motion. Ask what they review first. Ask how they decide whether to keep, revise, or replace prior design work. Ask how they manage unfinished configuration, unresolved gaps, and business trust issues.
Named delivery leadership
The sales team will not rescue the project. The replacement partner should identify who will actually lead the work, how much time they will commit, and what similar situations they have handled before. The most important roles often include the engagement lead, solution architect, project manager, functional leads, technical architect, integration lead, data migration lead, testing lead, and change or training lead. Vague staffing language is a risk. In a recovery situation, the client needs to know who is showing up.
A practical first 30 to 60 day plan
A replacement partner should be able to explain the first phase of work in practical terms.
What will they review?
Who will they interview?
How will they validate the current design?
How will they assess configuration?
How will they review open gaps and unresolved decisions?
How will they evaluate data, integrations, testing, and reporting?
How will they create a revised plan to finish?
A partner that cannot explain the first 30 to 60 days is not ready to take over a struggling implementation.
Transparency in the project system of record
For Dynamics 365 programs, Azure DevOps (ADO) is often used to manage requirements, backlog items, configurations, enhancements, integrations, test cases, bugs, defects, and release readiness. In a recovery project, the project system of record becomes even more important. The partner should not treat ADO or any project tool as an internal technical workspace only. The client needs visibility into what is being tracked, what is changing, what is open, and what is ready. Executives do not need to live in the detail, but status reporting should be based on traceable work, not optimistic slides.
Commercial realism
Replacement partner situations are commercially sensitive. There may be prior sunk cost, unfinished work, unclear deliverables, license timing, internal fatigue, and pressure to keep moving.
A strong replacement selection process should force commercial clarity.
What work is included?
What prior work will be reviewed?
What assumptions are being made about rework?
What is excluded?
How will change orders be handled?
What rate card applies?
What is fixed fee, milestone-based, or time and materials?
What is the estimated cost to stabilize, reset, and finish?
The lowest price is not always the safest choice. The goal is a partner whose commercial model reflects the real risk of the project.
What leaders should remember
A troubled ERP implementation does not always mean the original software decision was wrong. Sometimes the issue is partner fit. Sometimes it is weak governance. Sometimes it is unclear requirements, incomplete design, poor testing, unrealistic scope, limited client readiness, or commercial assumptions that were never fully understood. Before replacing the system, companies should understand whether the implementation can be recovered. That requires an independent, client-side view of the project. It requires someone who can separate symptoms from root causes, challenge both the client and the partner when needed, and help leadership make a decision based on evidence.
That is what companies are often really looking for when they search for an ERP fixer. They are not looking for someone to patch a system screen. They are looking for someone who can help them regain control of an ERP decision that matters to the business.
How John Hannan LLC helps
John Hannan LLC provides client-side, vendor-neutral , , , partner selection, and ERP project recovery support. We do not sell software, represent ERP vendors, or accept referral fees. Our role is to protect the client’s interests and help leadership make informed decisions about the system, partner, scope, plan, and path to go-live. For companies that have already selected Dynamics 365 Finance and Supply Chain but are questioning the implementation partner, we help assess the current state, identify project risks, define recovery options, evaluate replacement partners, structure decision criteria, and support a practical path forward. If your Dynamics 365 implementation is off track, the next decision should not be rushed. It should be structured, fact-based, and grounded in what the business needs the ERP system to do.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
