You championed this project. You signed off on the partner. You presented the business case to your board. And now your Dynamics 365 Finance & Supply Chain Management implementation is live. The D365 F&O post go-live period is about to become the most important phase of the entire project.
Congratulations. But now the real work starts.
Because go-live is the moment the entire company turns to IT and asks: so what now? And as the VP of IT or CIO, that question lands on your desk. Not the project manager’s. Not the partner’s. Yours. After all, “ERP is IT”, right?!
After 14 years placing D365 contractors into manufacturing companies across the US, I can tell you this: the D365 F&O post go-live period, specifically the first 6 months, is where ROI is either captured or lost. And most IT leaders aren’t ready for it because nobody told them to plan for it.
Go-live is when the spotlight shifts to you
During the implementation, the partner ran the show. They managed the milestones, led the steering committees, and presented the status reports. Your job was to keep the project funded, remove blockers, and shield your team from the noise.
After go-live, that dynamic flips completely.
The partner starts rolling off. Your project team goes back to their day jobs. Budget gets redirected. And the system, which is technically live but not yet mature, becomes your responsibility.
This is the moment that defines your reputation as an IT leader. If D365 is seen as a success at the 6 month mark, you’re the person who modernised the business. If it’s seen as a struggle, that sticks to you. Not to the partner who left. Not to the project manager who moved on. To you.
The good news: you can control this outcome. But only if you plan for D365 F&O post go-live stabilisation the same way you planned the implementation itself.
Need D365 expertise your internal team doesn’t have yet? Or some independent advice? Our vetted contractors are ready to jump in. Let’s talk:
What actually happens in the D365 F&O post go-live period
Here’s what Monday morning looks like after go-live in a manufacturing company. I’ve seen this pattern dozens of times.
The warehouse team is back on spreadsheets by noon because the pick logic doesn’t match their actual process. Finance is manually adjusting transactions that were supposed to be automated. Production orders are stuck and nobody is sure why. The reporting that looked great in UAT doesn’t reconcile against real data.
Hopefully, you nodded to no more than ONE of those.
Your CFO calls. Month-end close is going to take an extra week. Your operations director is in your office asking why the production schedule in D365 doesn’t match what’s happening on the plant floor. Your warehouse manager has already built a workaround in Excel.
This is normal. Every D365 F&O go-live has a stabilisation period. The system at go-live is maybe 70% of what it needs to be. The core processes work, but the edge cases, the exceptions, the things that only surface when real users run real transactions at real volume, those haven’t been found yet.
In manufacturing, those edge cases matter enormously. Your warehouse team knows within the first week. Your finance team knows at the first month-end close. Your production planners know at the first demand spike.
If nobody is there to catch and fix these issues quickly, users lose confidence. And once they lose confidence in D365, they build shadow systems. Spreadsheets come back. Manual processes appear. Within 3 months, you’re running two systems: D365 and whatever your people trust more.
That’s where your ROI goes to die. And that’s the story your board hears.
And if you’re still running AX 2012 and thinking go-live can wait, the hidden costs are already stacking up. We broke that down in detail here: The Hidden Costs of Staying on AX 2012 for Food & Beverage Manufacturers
The D365 F&O post go-live plan that nobody writes
Here’s what I see consistently: IT leaders spend months planning the implementation and almost no time planning what happens after go-live.
The implementation plan is detailed. Phases, milestones, resource plans, testing schedules, cutover checklists. Hundreds of pages.
The post go-live plan? A slide that says “hypercare: 4 weeks” with a vague description of ticket triage and a reduced partner team.
Four weeks isn’t enough. Not for a manufacturing company running D365 Finance and Supply Chain Management across multiple plants, warehouses, and legal entities. The first month-end close alone will surface issues nobody anticipated. The first quarter-end will surface more. The first physical inventory count, the first peak season, the first year-end. Each of these is a test of your D365 configuration, and each one will reveal gaps.
As the IT leader, you need to own this plan. Not delegate it. Own it.
What a VP of IT or CIO should put in place before go-live
The IT leaders who get the best D365 F&O post go-live outcomes tend to do the same things. None of this is complicated. It just requires you to make decisions that only someone in your seat can make.
Appoint permanent module owners. Today. Not the project team. Permanent owners. Someone in Finance who owns the D365 Finance configuration. Someone in Supply Chain who owns warehouse and/or production. Someone in IT who owns integrations and data. These are your people now. They need time carved out of their regular responsibilities.
Secure a dedicated stabilisation resource for 90 days. Minimum. This is the single highest-ROI decision you’ll make in the entire D365 F&O post go-live period. One experienced person (or a small team), fully dedicated, embedded in the business. Not splitting time with other projects. Not ramping down after week 4. Their only job is stabilisation. This can be an internal resource, an independent contractor, or a partner resource. But you need to budget for it and protect it. When your CFO pushes back on the cost, show them what a 3-month project delay costs in partner fees and lost productivity.
Run daily triage for the first 30 days. A 15-minute standup every morning. Finance, Supply Chain, Warehouse, Production. What broke yesterday? What’s the workaround? What’s the fix? Who owns it? You don’t need to attend every one of these. But you need to create them, resource them, and read the output. This cadence keeps issues from festering and gives users confidence that IT is on top of it.
Shift to weekly reviews from day 31 to day 90. The daily standup is intense and you can’t sustain it forever. After the first month, move to weekly reviews. Track issues by module, severity, and resolution time. Look for patterns. If the same process keeps breaking, the design probably needs revisiting. Escalate that to the partner if needed, or your independent D365 contractor, but you make the call.
Define your 30/60/90 day scorecard. This is for your board, your CFO, and yourself. Be specific. “Month-end close completed in 5 business days.” “Warehouse pick accuracy above 98%.” “Zero manual journal entries for intercompany transactions.” If you don’t define what success looks like, leadership will assume everything is fine until it very clearly isn’t. And by then, the narrative is already set.
The budget conversation with your CFO
This is the part nobody wants to deal with. You’ve already spent $3M to $10M. Maybe more. Now you need to go back to your CFO and ask for more money for D365 F&O post go-live stabilisation.
Here’s how to frame it.
Don’t ask for “more implementation budget.” That sounds like the project failed. Instead, frame it as “ROI protection.” You’ve made a $5M investment. Allocating 10-15% of that for stabilisation and optimisation is what ensures the business actually gets the value it was promised. It’s the difference between a $5M system that transforms operations and a $5M system that everyone works around.
If your CFO needs a number: budget $500K-$750K for post go-live stabilisation on a $5M implementation. Dedicated resources, extended support, configuration fixes, additional training. That’s the highest-ROI line item in the entire project, and it’s the one that gets cut first.
You are the only person in the organisation who can make this case. The partner won’t make it for you. The project manager can’t. This is a leadership conversation between you and your CFO. Have it before go-live, not after.
Driving the partner relationship after go-live
You (probably) chose this partner. Your name is on that decision. After go-live, make sure you’re driving the relationship, not the other way around.
Good implementation partners understand that go-live isn’t the end. Many offer structured hypercare and D365 F&O post go-live support packages. Take them seriously.
But understand the dynamic. After go-live, your partner is balancing your support needs against new project commitments. Their best people are being pulled toward the next implementation. The resources you get in month 3 may not be the same ones who built your system.
This is where having your own stabilisation plan, your own module owners, and your own dedicated resource makes the difference. You’re not dependent on the partner to tell you what’s working and what isn’t. You already know, because your people are living in the system every day and reporting back through the structure you built.
The best D365 F&O post go-live relationships I’ve seen are ones where the IT leader is driving the agenda. Specific asks. Clear priorities. Fast decisions. Partners do their best work when the client knows what they want. Be that client.
The 6-month window that defines your reputation
Six months. That’s roughly how long you have before the organisation’s opinion of D365 becomes fixed.
If users are productive and confident by month 6, the system becomes “the way we work.” Adoption sticks. Improvements build on a solid foundation. Your board sees the ROI starting to materialise. And you’re the IT leader who delivered.
If users are frustrated and working around the system by month 6, that perception is very hard to reverse. People will say “D365 doesn’t work” long after it actually does. And the person they associate with that outcome is you.
The difference between these two outcomes is rarely about the software or even the implementation quality. It’s about what happened in the D365 F&O post go-live period. Did someone own it? Did issues get fixed quickly? Did users feel heard? Did IT show up?
That’s where the ROI lives. And that’s your window.
Three D365 F&O post go-live decisions to make this week
If you’re approaching go-live, or if you went live recently and don’t have a stabilisation plan in place, here are three decisions that only you can make:
1. Name your module owners. Who internally owns D365 Finance? Who owns Supply Chain? Who owns the warehouse configuration? If the answer is “the project team” or “we’ll figure it out after go-live,” you have a gap that needs filling now. Today.
2. Secure and protect the stabilisation budget. 10-15% of total implementation cost. Have the conversation with your CFO before go-live. Frame it as ROI protection, not cost overrun.
3. Write your own 30/60/90 day scorecard. Don’t let the partner define what success looks like. You define it. Based on what your business needs. Based on what your board expects. Measure against it publicly.
The implementation gets the system live. The D365 F&O post go-live period determines whether it was worth it. And that part is entirely on you. Go get em’.
Want to understand how dependent your organisation is on external support after go-live?
We built a quick Partner Dependency Assessment that shows you where you stand.
