What to Expect in the First 90 Days of a Business Central Implementation
- 23 hours ago
- 4 min read
Most ERP implementations don’t fail because of the software. They fail because expectations don’t match reality.
The first 90 days of a Microsoft Dynamics 365 Business Central implementation set the tone for everything that follows. Move too fast, and you build on shaky ground. Move too slow, and momentum disappears.
If you’re about to start—or you’re already in the middle of it—here’s what actually happens in those first three months, without the sugarcoating.
Days 1–30: Alignment Before Action
This is the phase most companies underestimate.
There’s a strong urge to “just start building,” especially when leadership wants quick wins. But the first 30 days are less about the system—and more about getting people, processes, and expectations aligned.
What typically happens:
Stakeholder workshops to understand how the business really operates (not just how it’s documented)
Process mapping across finance, sales, purchasing, and operations
Identifying gaps between current workflows and standard Business Central functionality
Early conversations around customization vs. configuration
This is also where tension can surface.
Different departments often have conflicting priorities. Finance wants control. Sales wants speed. Operations wants flexibility. If those differences aren’t resolved early, they show up later as delays, rework, or endless change requests.
What to watch for:
If your team is skipping detailed discussions to “save time,” you’re probably creating bigger problems for later.
Days 31–60: Build, Configure, Challenge Assumptions
Now the system starts taking shape.
This is where consultants begin configuring Business Central based on the agreed processes—setting up chart of accounts, posting groups, workflows, dimensions, and core modules.
But here’s the part many teams don’t expect:
this phase isn’t just execution—it’s confrontation.
As the system becomes real, assumptions get tested.
“Why does the system work this way?”
“This isn’t how we’ve always done it.”
“Can we customize this part?”
Some of those questions lead to better solutions. Others lead to unnecessary complexity.
The best implementations use this phase to simplify, not replicate legacy habits.
What good looks like:
Clean configuration over heavy customization
Willingness to adjust processes where it makes sense
Clear decision-making on what’s truly critical vs. “nice to have”
What goes wrong:
Trying to rebuild the old system inside Business Central
Over customizing too early
Delaying decisions, which slows everything down
Days 61–90: Testing, Training, and Reality Check
This is where everything gets real.
The system is configured (mostly), and now your team starts using it in structured testing scenarios. Data is migrated. Transactions are simulated. Reports are validated.
And this is where issues surface—because they always do.
Common challenges:
Data inconsistencies from legacy systems
Gaps in user understanding
Edge cases that weren’t considered earlier
Resistance from users who are still unsure about the change
Training becomes critical here—not just how to click buttons, but understanding why processes are changing.
This is also when confidence is built—or lost.
If users feel supported and understand the system, adoption follows. If they feel confused or overwhelmed, workarounds start creeping in before go-live even happens.
What to focus on:
Hands-on, role-based training
Real-world scenarios (not just demos)
Tight feedback loops between users and the implementation team
What Most People Get Wrong About the First 90 Days
They expect progress to be linear.
It’s not.
Some weeks feel fast. Others feel frustratingly slow. Decisions get revisited. Assumptions change. New requirements emerge.
That’s normal.
What matters is not avoiding friction—but managing it well.
The companies that succeed aren’t the ones with perfect plans. They’re the ones that:
Stay engaged at the leadership level
Make decisions quickly (even imperfect ones)
Focus on outcomes, not just tasks
The Real Goal of the First 90 Days
It’s not perfection.
It’s readiness.
By the end of this period, you should have:
A system that reflects your core business processes
A team that understands how to use it
Enough confidence to move toward go-live without hesitation
Everything else—optimization, reporting enhancements, advanced workflows—comes after.
Where The BC Team Comes In
This is exactly the phase where most ERP projects either stabilize—or start drifting.
At The BC Team, we don’t just “set up” Business Central. We help you navigate the decisions that actually determine success:
Clarifying processes early so you don’t build on assumptions
Keeping configurations clean to avoid long-term complexity
Challenging unnecessary customization before it becomes technical debt
Supporting your team during testing and training so adoption sticks
Stepping in mid-project if things already feel off-track
We’ve spent 19+ years working with Microsoft Dynamics 365 Business Central and NAV, and we’ve seen how small missteps in the first 90 days can turn into expensive problems later.
Our role is simple:
keep your implementation practical, focused, and moving forward.
Final Thought
The first 90 days of a Business Central implementation are less about technology and more about discipline.
Discipline in decision-making.
Discipline in process design.
Discipline in resisting unnecessary complexity.
Get that right, and the system becomes an accelerator.
Get it wrong, and it becomes another problem to manage.
Need a Second Opinion?
If you’re in the middle of an implementation—or about to start—and want a clear, experienced perspective, we’re happy to help.
Whether it’s a quick sanity check, a structured ERP health review, or hands-on support, we’ll meet you where you are and help you move forward with confidence.
Reach out to The BC Team to start the conversation.
Comments