+1 480 485 7373
Microsoft Teams
Symptoms of a stalled ERP implementation
- ✓The go-live date has moved more than once and nobody can say what the new date depends on
- ✓Test scripts pass in demos but fail when your staff run them with real documents
- ✓The team has tried data migration several times and balances still do not agree
- ✓Custom extensions keep growing, and nobody has asked whether standard features would do
- ✓Change requests arrive faster than decisions, and rework eats the budget
- ✓Your team has quietly gone back to the old system or to spreadsheets
The stalled ERP rescue review, step by step
- 1
Secure access and documents
With your admin's permission, we get read access to the Business Central environments and the source code. We also read the contract, the statement of work and the issue log. We change nothing during the review.
- 2
Compare scope with reality
In a stalled ERP implementation rescue, we check every promised requirement against what the partner configured, built and tested. Then we list the gaps plainly. That includes the ones that were never in the contract but everyone assumed.
- 3
Test the foundations
We examine the chart of accounts, dimensions, posting groups, costing method and migration mappings. After all, problems there spread into everything built on top.
- 4
Read the code
Next, we check custom AL extensions for upgrade safety, test coverage and whether you still need each one. We keep code that follows Microsoft's rules. However, we flag code that fights the product.
- 5
Write the ERP implementation rescue plan
You receive a triage report and a plan. It says what to keep, fix and drop, and which decisions you must make. It also sets the criteria to meet before go-live.
Recover, reset or restart
What we will not do
We will not blame the previous partner in writing for the sake of it. Instead, the report describes facts in the system and the documents. That is far more useful if a commercial talk with that partner follows.
We will not recommend a restart to win more work. A stalled ERP implementation rescue often works by narrowing scope and fixing a handful of foundations. We recommend a restart only when the design underneath cannot carry your business. Then the report explains why in terms your board can follow.
Stalled ERP implementation rescue questions
Can you step in while our current partner is still on the project?
Yes, a review can run alongside the current partner. Sometimes that is the best route, because the findings give both sides a shared list to work from. We will want read access and cooperation on documents, and we keep our findings factual. Whether you continue with the current partner is your decision.
What if we want to change partner completely?
Business Central online lets the customer change the partner of record and remove the old partner's delegated access through admin settings. Your environments, data and extensions stay in your tenant. What you must secure early is the source code for any custom extensions. It should sit in a repository you can access.
Our data migration keeps failing. Where do you start?
With the reconciliation, not the tool. We compare the trial balance, open customer and vendor items and inventory values between the old system and a test migration. Then we trace every difference back to a mapping or a data problem. Once we explain the differences, the fixes are usually simple.
Will we have to redo user testing?
Only for the parts that change. The rescue plan shows which tested areas still hold. It also shows which need retesting because setup or code moved underneath them. Keeping users' trust matters. So we keep retests focused and plan them around their workload.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.