ERP Implementation Planning: What Your Vendor Won't Walk You Through
ERP Implementation Planning Key Takeaways
ERP implementation planning for a small or midsize business typically runs 3 to 9 months, depending on scope and data complexity.
Data migration is where most implementation timelines slip, not software configuration.
A realistic ERP implementation planning budget includes software, partner fees, internal staff time, and training, not just the license cost.
Change management, not technology, is the single biggest predictor of a smooth go-live.
Most articles on ERP implementation planning read like they were written for a company that doesn't exist. A company with an unlimited budget, a dedicated IT department, and a project timeline nobody's watching too closely, but thats not the business you run, if you're here now.
If you're a manufacturer, distributor, healthcare provider, or growing organization looking at a new system, planning needs to answer a much smaller, much more practical set of questions.
How long will this take with the team you have?
What will it really cost?
Where do these projects usually go sideways?
We've sat inside enough Business Central rollouts, including transitions off Dynamics GP, to know where ERP implementation planning succeeds and where it quietly falls apart. This article was put together by a Microsoft MVP-led team that's run these rollouts firsthand. It walks through both the successes and the failures, along with the specific decisions that separated one from the other.
What ERP Implementation Planning Involves
ERP implementation planning is the work you do before a single screen gets configured. It's the process of defining what your new system needs to do, who needs to be involved, what your current data looks like, and how you'll measure whether the project worked.
Done well, this stage answers a handful of questions before the contract gets signed:
What business problems is this system solving, specifically?
Which processes need to be redesigned instead of just copied over?
Who owns each decision during the project?
What does a realistic go-live date look like, and what happens if it slips?
Skip this stage, or rush through it, and you're not planning at all. You're scheduling meetings and hoping the software figures itself out.
A short definition, since it's the kind of thing people search for directly: ERP implementation planning is the pre-build phase of an ERP project where scope, timeline, budget, team roles, and data readiness get defined before configuration starts. Part of that definition phase usually includes confirming the platform itself is the right fit. If you're still weighing options, our breakdown of Business Central vs SAP: Which ERP Is Right for Mid-Market Companies? is a useful starting point.
Discover What ERP Implementation Planning Could Look Like for Your BusinessOur team offers a no-cost discovery session to walk through your current processes and where a Business Central rollout would fit. |
Why Most ERP Implementation Planning Falls Apart Before Go-Live
Here's a claim we'll stand behind: in our experience, the software did not fail most ERP projects that run over. They failed by planning that never accounted for the messiness of real business data and real internal politics.
A few patterns show up again and again.
Nobody owns the decision. When the process treats every choice as a group decision, projects stall waiting for consensus that never arrives. Somebody, usually a project sponsor with real authority, needs to make the call and move forward without a second round of approvals.
The scope keeps growing. Every department wants "just one more feature" added mid-project. Good ERP implementation planning locks scope early and routes new requests into a phase two list instead of the current build.
Legacy data gets underestimated. Old systems, especially systems like Dynamics GP that have been customized for years, carry more data debt than anyone remembers. Solid planning has to include an honest data audit, not a guess based on how clean the last export looked.
These aren't hypothetical risks. Here's what happened when one operations director brought us in after a Business Central rollout had already gone off track.
"We engaged Shannon Mullins to help us decide how to proceed with our Business Central implementation. We contacted her and within hours we were on the phone discussing details with her and her team. Shannon was able to quickly assess the situation and come up with a game plan to get us back on track. She is a consummate professional and her knowledge of Business Central is truly impressive. Thanks to her we were put back on track within days." John, Director of Operations |
That's what solid ERP implementation planning looks like even mid-project: a clear assessment and a real path back to a working timeline.
Nobody plans for the plateau. Even a well-run project sees a dip in productivity right after go-live, as staff relearn how to do familiar tasks. Teams that don't plan for this dip tend to panic and blame the software instead of riding out a normal adjustment period.
There's a quieter pattern too, one that's harder to spot from the outside. Vendors sell software. Consultants sell hours. Neither one is automatically incentivized to slow down and ask whether your business is really ready to change how it works, which is what an ERP rollout ultimately asks of an organization.
For a rundown of what tends to separate the smooth projects from the stalled ones, our post on ERP implementation best practices for small and mid-sized businesses covers the patterns we see most. Look for a partner who pushes back on an unrealistic timeline instead of one who agrees to whatever date makes the sale easier.
The ERP Implementation Planning Timeline for a Growing Business
Enterprise vendors love to describe this process in six clean phases, as if every company moves through them at the same pace. Growing businesses don't work that way.
For a company in the 25 to 250 employee range implementing Business Central, here's a more honest timeline.
Weeks 1 to 3: ERP Implementation Planning Discovery and Scoping
This is where the real work starts. Your implementation partner should be interviewing department heads, mapping current workflows, and identifying which processes are truly broken versus which just feel unfamiliar.
Weeks 4 to 8: ERP Implementation Planning Design and Configuration
The system gets built around your real processes, not a generic template. This is also when decisions around integrations, like payment processors, e-commerce platforms, and industry-specific tools, get finalized, along with whether a gap gets closed with a built-in feature or something custom. Our post on Business Central Extensions: When to Use Extensions vs. Customizations walks through that decision in more depth.
Weeks 9 to 16: Data Migration and Testing
The longest and most unpredictable phase. Financial history, customer records, vendor data, and inventory counts all need to be cleaned, mapped, and validated before go-live.
Weeks 17 to 20: ERP Implementation Planning Training and Go-Live Prep
Your team needs hands-on time in the new system before launch day, not a single overview session the week before.
Weeks 20 to 24: Go-Live and Stabilization
A well-run rollout still assumes a few weeks of adjustment after launch. Budget for it instead of being surprised by it.
That's a realistic 5 to 6 month window for a mid-size Business Central rollout. The 3-month end of the range applies to a narrower case: a single-entity company with clean data and a small user base, running standard functionality with no major customizations. Multi-entity, multi-currency, or heavily customized environments often need closer to 9 months, and pretending otherwise just sets everyone up for a missed deadline.
Building Your ERP Implementation Planning Team
Planning fails fast when it's treated as an IT-only project. The businesses that see the smoothest rollouts build a team that spans the organization from the start.
At minimum, your internal team should include a project sponsor with budget authority, a project lead who can dedicate real hours each week and not just attend meetings, a finance representative who understands your chart of accounts and reporting needs, and a super user from each major department who will help train the rest of the staff after go-live.
If you're deciding whether that project lead should come from inside your company or from your implementation partner, our post on Who Should Lead Your ERP Implementation? Project Manager vs. Guided Self-Implementation lays out both paths.
On the partner side, ERP implementation planning should be led by a consultant who asks about your business before talking about the software. If your first conversation with a potential implementation partner is entirely about features, that's a signal their planning process may be thinner than it should be. Our post on How to Choose an ERP Consulting Firm: 7 Questions to Ask First gives you the questions to bring to that first call.
This is usually where organizations start comparing implementation partners in earnest, and it deserves a careful comparison before you commit to a scope of work. Our guide on how to choose a Microsoft Dynamics 365 partner covers eight questions to bring to that conversation before you sign anything.
Part of that evaluation is getting a feel for who's behind the partner you're considering. Here's A BC's founder and CEO, Shannon Mullins, a Microsoft MVP, talking through the vision and services she brings to Dynamics 365 clients.
Budgeting for ERP Implementation Planning: Realistic Cost Ranges
Software license cost is the number everyone focuses on during the budgeting conversation, and it's usually the smallest piece of the total investment.
A more complete budget includes the Business Central license itself, implementation partner fees for discovery, configuration, and data migration, internal staff time (which is real cost even though it doesn't show up on an invoice), third-party integration or customization work, and training for your team once the system is live. Licensing alone has more nuance than most people expect, and our post on Business Central Licensing & Pricing Explained breaks down how those tiers really work.
For small businesses with straightforward processes, total ERP implementation planning and rollout costs often land in the $30,000 to $75,000 range.
Mid-market companies with multiple entities, custom workflows, or significant data migration needs frequently land between $100,000 and $250,000 or more.
These are directional numbers, not quotes. Your actual figure depends heavily on data complexity and how much of your current process needs to be rebuilt rather than reused. For a closer look at where those numbers come from, see How Much Does a Business Central Implementation Really Cost?
If your business is small enough that a full consulting engagement feels heavier than you need, lighter options exist. Our post on ERP Self Implementation: Take the Lead on Your Dynamics 365 Journey walks through what that lighter-weight model looks like for small businesses.
Data Migration in ERP Implementation Planning (Where Projects Stall)
If there's one section of this article to read twice, it's this one. Data migration causes more delays than any other single factor in a typical rollout.
Here's why. Most companies underestimate how much of their historical data is inconsistent, duplicated, or simply wrong. Customer records with three different spellings of the same company name. Inventory counts that haven't matched a physical count in years. Vendor terms that were manually overridden so often nobody remembers the original agreement.
Good ERP implementation planning treats data cleanup as its own phase, not a task squeezed in during configuration. That means auditing your data early, deciding what needs to migrate versus what can be archived, and running test migrations well before go-live rather than discovering problems in the final week. Data issues are just one of several recurring headaches we cover in ERP Implementation Challenges (and How Guided Self-Implementation Avoids Them).
ERP Implementation Planning for Industry-Specific Needs
Generic advice on this topic tends to ignore how different implementations look depending on your industry, and that's a real gap in most of what's published on the subject.
A manufacturer needs to think through bill of materials complexity, shop floor data capture, and production scheduling from day one. Our post on Best ERP Software for Manufacturing Companies: How to Evaluate Your Options walks through what to prioritize before you plan around a specific system. A distributor needs a plan that accounts for warehouse workflows, multi-location inventory, and vendor lead times, and Distribution ERP Software: Is Guided Self-Implementation Right for Your Business? is a good next read if your team is small enough to consider a lighter rollout model.
Healthcare organizations have compliance and reporting requirements that need to be built into the plan from the beginning, not bolted on afterward. Our post on Best ERP for Healthcare Organizations: What to Look for in Billing, Compliance, and Reporting goes deeper into those requirements, and Healthcare ERP Implementation Services: How to Go Live in 8–12 Weeks shows what a compressed timeline can look like for a smaller practice.
Even less obvious industries carry real nuance. Performing arts organizations and sports organizations often run on a mix of donor management, ticketing, and event-based revenue that generic frameworks simply don't address.
The takeaway for anyone starting ERP implementation planning: if a partner doesn't reference your specific industry's workflows within the first few conversations, that's a reason to keep asking questions before you move forward. A discovery process built on a template deck tends to produce a system that fits the software's assumptions better than it fits yours.
Change Management: The Most Skipped Step in ERP Implementation Planning
Software gets configured. Data gets migrated. On launch day, half your staff logs in and reverts to old workarounds because nobody explained why the new process exists.
That's a change management failure, and it's one of the most common gaps we see. Teams plan the technical build in detail and treat adoption as an afterthought.
Strong ERP implementation planning builds change management from the start. That includes naming super users early so they can champion the new system among their peers, communicating the "why" behind the change and not just the "how," running hands-on training instead of passive demos, and setting realistic expectations that the first few weeks after go-live will feel slower before they feel faster.
Communication carries as much weight here as configuration does. A short weekly update to staff, even a two-line email, keeps the rollout from feeling like something that's happening to people instead of with them.
Still Working Through What ERP Implementation Planning Looks Like for Your Specific Business?Let's talk through your current systems, your timeline, and what a realistic Business Central rollout would involve. |
ERP Implementation Planning Checklist for Business Central Rollouts
Before you start evaluating vendors, run through this shortlist as a gut check on your own readiness.
Confirm executive sponsorship with real budget authority behind it.
Identify your internal project lead and protect their time on the calendar, not just on paper.
Audit your current data for accuracy before assuming it will migrate cleanly.
Define what success looks like in measurable terms, not just "better reporting."
Build a training plan that starts weeks before go-live, not the week of.
Set a realistic go-live window with a buffer for stabilization afterward.
Decide now which processes you're willing to redesign, since clinging to old workflows inside new software tends to recreate old problems.
If more than one of these is missing, that's not a reason to delay. It's exactly what the planning phase is for. And if the partner you're evaluating can't help you close these gaps before signing, our post on Top ERP Consulting Companies: How to Choose the Right Partner can help you compare notes.
A BC Consulting is here to guide you through what ERP Implementation Planning can look like for your business, and how the right one can change everything. Book a free consultation today!
Frequently Asked Questions
What is ERP implementation planning?
It's the process of defining scope, timeline, budget, team roles, and data readiness before an ERP system gets configured and deployed. It's the foundation that determines whether the rest of the project runs smoothly.
How long does ERP implementation planning take?
For a small or midsize business, the full process typically takes 3 to 9 months. Simpler, single-entity Business Central implementations move faster; multi-entity or heavily customized environments take longer.
What does ERP implementation planning cost?
Costs vary widely, but small businesses often see total project costs, including software, partner fees, and internal time, land between $30,000 and $75,000. Mid-market companies with more complexity frequently invest $100,000 to $250,000 or more.
Who should be involved in the planning process?
At minimum, a project sponsor with budget authority, a dedicated internal project lead, a finance representative, and department-level super users. On the partner side, a consultant who understands your industry, not just the software.
What's the biggest risk during ERP implementation planning?
Underestimating data migration and skipping change management. Both are addressed early in a strong plan, and both are frequently the reason projects run over budget or past deadline when they're not.
Comments