Building an Internal D365 ERP Team For Your Implementation

Building an internal D365 ERP team is the part of implementation planning that most IT leaders struggle with. Yes: they name the people, commit the headcount, and check the box. But there is a massive difference between assigning people to a project and building an internal D365 ERP team that can actually own a multi-million dollar transformation.

This blog is for the IT leader who has been told “you need internal resources on this project” and is now trying to figure out what that actually means. Not simply how many people. What capabilities. Because the difference between assigning people to a project and building an internal D365 ERP team that can actually own the outcome is where most implementations quietly start to drift.

The 5 capabilities your internal D365 ERP team actually needs

Building an internal D365 ERP team is more about quality than quantity. You can have 10 people internally on the project, but if none of them have the right capabilities, you are still not ready. Here are the five that matter most.

1. Business process ownership. Someone on your internal team needs to be the authority on how your business actually operates. Not how it is documented. How it actually runs. The person who knows that your receiving process has 4 unofficial steps that nobody wrote down. The person who can explain why finance closes the books the way they do and what breaks if that changes. Your implementation partner will configure D365 based on what your team tells them. If your team cannot articulate the real processes, the configuration will reflect the documented ones, which are almost never the same thing at a manufacturing company.

2. Decision-making authority. ERP implementations generate hundreds of decisions. Which costing method? How many legal entities? Standard or advanced warehousing? Should catch-weight apply to these product lines? Your internal D365 ERP team needs people who can make these decisions quickly, or who have a direct line to someone who can. If every decision has to go through three layers of approval, the project stalls. If decisions get made without the right people in the room, they get made wrong. I wrote about this exact dynamic in 5 early warning signs your D365 F&O implementation is drifting.

3. Data knowledge. Someone on your team needs to understand your data landscape. Not at a theoretical level. At the “I know where the vendor master lives, I know it has 4,000 duplicate records, and I know which system is the source of truth for customer addresses” level. Data readiness is the number one project killer, and it is entirely an internal responsibility. We covered this in depth in why D365 F&O data readiness is the #1 project killer.

4. Change management credibility. You need someone who can stand in front of the warehouse team and the finance team and be believed. Not someone from corporate with a slide deck. Someone the teams trust. Someone who has been in the building long enough to understand the culture, the informal power structures, and the real reasons people resist change. External change management consultants can provide frameworks. But the best change practitioners are the ones who have actually done the job.

Many of the change management experts in the d365contractors.com community spent years working in operations, on the plant floor, or in the warehouse before they moved into consulting. When they stand in front of your warehouse team and talk about what is changing, they are not reading from a playbook. They have lived it. And your team can tell the difference.

5. Time. This is the simplest capability and the one most often missing. Your best people are your best people because they are good at their current jobs. Pulling them onto a D365 project means someone else has to do their current job for 12 to 18 months. If you have not solved the backfill problem, you do not have this capability. You have a name on an org chart and a person who is going to burn out trying to do two full-time jobs.

How to assess whether your internal D365 team is ready

Here is a quick exercise that takes 15 minutes and will tell you more about whether your internal D365 ERP team is ready than any formal resource plan.

Step 1: Name the person. For each of the five capabilities above, write down the name of the person who owns it. Not “Finance team” or “IT department.” A name. One person. If you cannot name someone for all five, you have a gap. This kinda information is what you need before the project starts, not information you discover in month 4 when the partner is waiting on decisions that nobody has the authority or knowledge to make.

Step 2: Check their capacity. For each name you wrote down, answer this: can that person dedicate at least 60% of their time to this project for the next 12 to 18 months? If the answer is no, you still have a gap. Having the right person at 20% capacity is almost worse than not having them at all. They will be consulted on decisions but not present for the context behind them. They will review configurations they did not help build. They will sign off on testing they did not participate in. And when something goes wrong post go-live, it’s hard (or unfair!) to hold them accountable.

Step 3: Confirm they actually know. Does each of these people know they are on the project? Not “has been told” but “has accepted the role, understands what it means, and has had their day job reallocated.” You would be surprised how often IT leaders commit people to an ERP project without ever having a direct conversation about what that commitment actually involves. “I figured they knew” is not gonna fly!

What happens when your internal ERP team has gaps nobody addressed

You’ll probably start the project with a capable team that is stretched too thin. But in the first few weeks, it works. Everyone is energized. Workshops are productive. The partner is impressed with how much your team knows about the business. Then month 2 hits. Quarter-end close pulls your finance lead off the project for two weeks. A major customer audit takes your supply chain person out for 10 days. Your warehouse supervisor’s replacement calls in sick for a week and suddenly they are back on the floor full time.

Each absence is temporary. Each one is justified. And each one creates a gap in the project that gets filled by one of two things: the partner making assumptions, or the decision getting deferred. Neither of those is good. Assumptions lead to configuration that does not match how your business works. Deferred decisions pile up and create a wall of rework in the final months of the project when you can least afford it.

By month 6, your project is technically “on track” but the internal D365 ERP team feels like they are barely keeping up. The partner is doing more of the heavy lifting than planned. Knowledge transfer is not happening because your people are not in the room consistently enough to absorb it. And you are building a growing dependency on external consultants that will be very expensive to unwind after go-live. I wrote about what this dependency looks like long term in how to build your internal D365 F&O team whilst using external consultants.

How to close the gaps in your D365 ERP team without delaying the project

Gaps in your internal D365 ERP team do not mean you should delay the project. They mean you should fill the gaps strategically before or during the early stages of the implementation.

For business process ownership gaps: Run a structured process discovery exercise internally before the partner kicks off. This does not require D365 knowledge. It requires your operations, finance, and warehouse leaders to sit down and document how things actually work. Not the process maps from 2009. How things work today, including the workarounds. Three to four weeks of focused internal workshops can give your team the foundation they need to show up to partner sessions with confidence instead of confusion.

For decision-making authority gaps: Create a decision rights matrix before the project starts. It sounds corporate, but it saves weeks of delays. For every major decision category (chart of accounts structure, costing method, warehouse configuration, integration approach), name the person who decides and the person who approves. Two names per decision. If you cannot fill in the matrix, you have found your gap. Fix it before kickoff.

For data knowledge gaps: Hire a data owner. Internal if you have someone capable. But definitely an independent contractor if you do not. This person needs to live inside your data for 60-90 days before the implementation starts and own it through go-live. It is one of the highest-ROI hires you can make on the entire project.

For change management credibility gaps: Identify your super users early. Not the most technical people. The most respected people in each department. Give them visibility into the project from month 1 and empower them to be the bridge between the project team and the rest of the organization. An engaged super user with credibility on the shop floor is worth more than any external change management consultant.

For time gaps: Backfill. There is no shortcut here. If your best people are on the D365 project, someone else has to do their jobs. Budget for it. Plan for it. Protect it. Every dollar you spend on backfill saves you three dollars in project delays, rework, and post go-live firefighting.

Building your D365 team is a leadership process, not just staffing

The manufacturing companies that run the best D365 implementations are not the ones with the biggest internal teams. They are the ones who honestly assessed what their team could handle, filled the gaps before they became problems, and protected their people’s time throughout the project.

Building an internal D365 ERP team that works is a leadership responsibility. It means having the uncomfortable conversations early about capability and budgets. It means telling your CFO that the finance lead needs to be backfilled, not split between the project and month-end close. It means telling your COO that the warehouse supervisor cannot run the warehouse and own the WMS configuration at the same time. It means budgeting for the unglamorous work of process documentation, data cleanup, and backfill hires before you spend a dollar on partner fees.

If you are about to start a D365 F&O implementation and you have not done this assessment, do it now. If you are already mid-project and recognizing some of these gaps, it is not too late to address them. But every week you wait makes the gaps harder and more expensive to close. The questions in 5 questions to answer before you talk to any D365 F&O vendor are a good place to start if you want a broader readiness check beyond just team capability.