D365 F&O data readiness is the single most underestimated factor in ERP implementations.
Despite what you see on LinkedIn: nobody ever killed an entire implementation with a bad configuration decision. Configurations can be fixed. Workflows can be adjusted. Security roles can be rebuilt. But when your data is wrong? That breaks everything, and it breaks it in ways that are almost impossible to fix quickly.
After 14 years in D365 staffing, I’ve placed hundreds of contractors into manufacturing implementations across the US. And the pattern is always the same. The project plan has a line item for “data migration.” It sits somewhere between “testing” and “cutover.” It gets a few weeks of attention near the end. And then it can blow up the entire timeline.
D365 F&O data readiness isn’t a task you check off. It’s the foundation everything else sits on. Get it wrong and your configuration doesn’t work, your testing is meaningless, your users don’t trust the system, and your go-live becomes a disaster recovery exercise.
And if you plan to board the Microsoft ERP AI train, this stuff has never been more important.
Why D365 F&O data readiness is YOUR responsibility, not your partner’s
Here’s something worth understanding early. Your implementation partner’s SOW almost certainly includes a line that says something like: “Client is responsible for providing clean, validated data in the agreed format by the agreed date.”
Read that again. That’s your partner being clear about where their scope ends. D365 F&O data readiness sits with you.
Partners scope their projects assuming your data will arrive clean, on time, and in the right format. Their timelines, their resource plans, their testing schedules — all of it assumes the data is ready when they need it. When it isn’t, and it almost never is, the project slips. But the partner isn’t absorbing that cost. You are.
This isn’t a criticism of partners. It’s just how the commercial model works. The partner can’t price the risk of your data being a disaster, because they don’t know the state of your data until they’re already deep into the project. So the SOW places responsibility with you, and most IT leaders sign it without realizing what they’ve just agreed to.
Data readiness starts 6 months before you think it does
Most manufacturing companies don’t start thinking about their data until the implementation partner asks for it. By then, you’re already behind.
For a mid-market manufacturer running a legacy ERP, or worse, running critical processes on spreadsheets alongside the ERP, the data landscape is usually a mess. You’ve got customer records in three different formats across two systems. Vendor master data that hasn’t been cleaned since the last ERP migration. Item masters with duplicate records, inconsistent units of measure, and descriptions that mean different things to different departments.
And that’s just master data. When you get into transactional data — open purchase orders, open sales orders, inventory balances, work-in-progress, open AR and AP — the complexity multiplies. Every one of those transactions has to be accurate on day one of go-live, because your finance team can’t close the month if the opening balances are wrong.
D365 F&O data readiness means starting the assessment and cleanup months before your implementation kicks off. Not weeks. Months. If you’re planning a January go-live, the data conversation should be happening in the spring of the prior year. That sounds aggressive. It isn’t. It’s realistic.
The 5 data problems that kill D365 F&O projects at manufacturing companies
In 14 years of placing D365 contractors into these exact projects, I see the same five D365 F&O data readiness failures over and over again. Every single one of them is preventable. None of them are surprising. And yet they keep happening.
1. Nobody owns the data. The project has a project manager. It has functional consultants. It has a steering committee. But who owns the data? Usually the answer is “everyone,” which really means nobody. D365 F&O data readiness requires a named person, ideally someone internal, who owns the entire data workstream end to end. Extraction, cleanup, validation, mapping, testing, cutover. One person. Full accountability.
2. The item master is a disaster. For manufacturers, the item master is the most critical and most neglected data set. You’ve got thousands of SKUs, many of them duplicated, many with incomplete Bills of Materials, many with incorrect units of measure. Some items are active. Some haven’t been ordered in 5 years but nobody marked them inactive. Your D365 configuration for Supply Chain Management depends entirely on the item master being accurate. Production planning, inventory valuation, procurement — all of it breaks if the item data is wrong.
3. Chart of Accounts doesn’t map cleanly. Your legacy chart of accounts was designed for a different system and a different era of the business. D365 F&O uses financial dimensions differently than most legacy ERPs. Mapping the old chart of accounts to the new structure is a design decision, not a copy-paste exercise. When this gets treated as a last-minute data task instead of a strategic finance decision, you end up with a chart of accounts that technically works but makes reporting a nightmare for years.
4. Historical data scope is undefined. How much history are you bringing over? All of it? 2 years? 5 years? Just open transactions? This decision affects timeline, testing complexity, and storage. And it’s usually not made until someone asks, which is usually too late. Every manufacturing company wants “all the history” until they realise what that actually means in terms of data cleanup, validation, and cutover time.
5. Nobody tested the data until UAT. This is the killer. The team extracts the data, transforms it, loads it into D365, and then doesn’t validate it properly until User Acceptance Testing. By that point, you’re weeks from go-live. The users start testing and immediately find that half the item records are wrong, opening balances don’t match, vendor payment terms are missing, and warehouse locations don’t exist. Suddenly the entire go-live timeline is at risk because of data issues that could have been caught 3 months earlier with a simple mock migration.
What good D365 F&O data readiness actually looks like
The companies that get this right do something very simple. They treat data as its own workstream with its own timeline, its own resources, and its own checkpoints. Not bolted onto the end of configuration. Not somebody’s side project. A proper workstream.
Good D365 F&O data readiness follows a pattern. First, you assess what you have. That means pulling every data source into the light — the ERP, the spreadsheets (YES finance team: that means EVERY spreadsheet you use!!), the Access databases somebody built 10 years ago, the warehouse system that doesn’t talk to anything else. You document what’s there, what’s missing, what’s duplicated, and what’s flat-out wrong.
Then you make decisions. What data migrates to D365? What gets archived? What gets cleaned up versus rebuilt from scratch? These are business decisions, not technical ones. Your finance team decides the chart of accounts mapping. Your supply chain team decides which items are active. Your operations team decides how much production history matters. The IT team coordinates, but the business owns the decisions.
Then you test early and test often. Run a mock migration in month 2 or 3 of the project, not month 8. Load the data into a sandbox environment and let users actually look at it. They’ll find problems immediately. Good. That’s the point. Find the problems early when you have time to fix them. Not during UAT when you don’t.
And you run the full mock cutover at least twice before the real thing. The first time will be ugly. The second time will be smoother. By the time you do it for real, the team has done it before and knows exactly what to expect.
Why your internal team has to own D365 F&O data readiness
Your partner can build the data migration templates. They can help you map fields from legacy to D365. They can run the technical import process. But they cannot clean your data for you. They don’t know your business well enough to decide whether item #4592 is the same as item #4592-A, or whether customer “ABC Industries” and “ABC Industries Inc” are the same entity, or whether that open PO from 2021 should be migrated or written off.
These are decisions that require deep business knowledge. The kind of knowledge that only exists inside your organisation, usually in the heads of people who have been there for years. Or a highly-skilled contractor who can come in, ask the right questions and get smart decisions made. Those people are the ones who need to be driving D365 F&O data readiness. Not the partner. Not the project manager. Your people.
This connects directly to something I wrote about in how to build your internal D365 F&O team. Data ownership is one of the earliest and most important capabilities your internal team should develop. If your team can’t own the data during implementation, they definitely can’t own it after go-live. And if nobody owns the data after go-live, the system degrades steadily from day one.
The real cost of poor D365 F&O data readiness
I’ve seen implementations delayed by 3-6 months because of data issues alone. That’s not 3-6 months of waiting. That’s 3-6 months of paying for partner resources who can’t move forward until the data is ready. That’s 3-6 months of your internal team being stretched across both the legacy system and the new one. That’s 3-6 months of change fatigue eroding user confidence before the system even goes live.
And the financial impact goes beyond the obvious. A delayed go-live means the ROI clock doesn’t start ticking. If you budgeted for 12 months to payback and the project is 6 months late, your finance team is now explaining to the board why the ERP investment isn’t delivering returns on the original schedule. That’s a career conversation nobody wants to have. I covered the mechanics of this in detail in why the first 6 months after go-live define your ROI.
Then there’s the hidden cost: user trust. When users log into D365 on day one and their data is wrong — the item descriptions don’t match, the inventory quantities are off, the customer addresses are outdated — they stop trusting the system immediately. And once users lose trust in an ERP, it is incredibly difficult to get it back. They revert to spreadsheets. They build workarounds. They stop entering data properly because “the system is wrong anyway.” That’s the death spiral that turns a recoverable data issue into a permanent adoption problem.
ERP data readiness is a leadership decision
If you’re a VP of IT or an ERP Program Manager reading this, the message is simple. Data readiness isn’t a task for someone on the project team to figure out. It’s a decision you need to make early, resource properly, and protect throughout the implementation.
That means assigning a dedicated data owner before the project starts. It means getting your finance, supply chain, and operations leaders to commit time — real time, not “squeeze it in between your day job” time — to data cleanup and validation. It means budgeting for data resources, whether that’s internal headcount, a contractor who specialises in D365 data migration, or both. And it means running mock migrations early enough that problems surface when there’s still time to fix them.
If you haven’t had the internal data conversation yet, the questions in 5 questions to answer before you talk to any D365 F&O vendor will help you figure out where you stand. Particularly question 4, which asks directly: how clean is your data? Your vendor might assume it’s fine. It probably isn’t.
The companies that nail D365 F&O data readiness don’t do anything magical. They just start early, assign ownership, test relentlessly, and treat data as a first-class workstream instead of an afterthought. It’s not glamorous. It doesn’t show up in any demo. But it’s the single biggest factor in whether your D365 implementation delivers real value or becomes an expensive lesson in what happens when nobody owns the data.
I’ll make a bet now: that starting in 2026 those companies that get data right will also flourish in the agentic ERP world we are without doubt transitioning to.
