ERP Implementation Plans: 9 Steps That Get You to Go-Live on Schedule
Key Takeaways
ERP implementation plans follow nine core stages, from team building through post-launch support.
Most small and midsize projects take four to nine months, depending on data complexity and customization.
Budgets typically range from a few thousand dollars for a guided self-implementation to six figures for a full-service, multi-department rollout.
The most common reason ERP implementation plans fail isn't the software. It's skipped discovery, rushed data migration, or training that gets treated as an afterthought.
If you've started researching ERP implementation plans, you've probably noticed most of what's out there reads like a textbook. Long paragraphs, vague phases, and not much you can put to use this week.
This one is different. Below are the nine steps every solid ERP implementation plan needs, in the order they happen, along with realistic timelines, real costs, and the mistakes that most often knock a project off schedule. Whether you're moving off Dynamics GP, replacing a patchwork of spreadsheets, or evaluating Business Central for the first time, this is the version of ERP implementation plans written for someone who has to build one, not just read about one.
What Belongs in ERP Implementation Plans Before You Start
Before you touch a single step, it helps to know what you're building. This is the document, or set of documents, that lays out your goals, your timeline, your team, and the order of operations for moving from your current systems to your new one. It isn't a Gantt chart alone, and it isn't a vendor's sales deck dressed up as a project outline. It's the working reference your team and your implementation partner return to whenever a decision needs to get made.
Good ERP implementation plans answer a few questions up front:
What business outcomes are we trying to achieve, and how will we measure them?
Who owns each part of the project, internally and with the implementation partner?
What's our realistic go-live date, and what happens if we miss it?
What data are we bringing with us, and what are we leaving behind?
If you can't answer those four questions yet, that's fine. Steps one and two below are designed to get you there.
See What an ERP Implementation Plan Looks Like for Your BusinessTalk to an A BC Consulting Group expert about what your ERP implementation plan would involve, based on your systems, your team, and your timeline. |
ERP Implementation Plans Step 1: Build Your Team and Define Your Goals
Every implementation lives or dies on who's running it. ERP implementation plans need a small, dedicated core team rather than a long list of stakeholders who show up occasionally.
At minimum, that team should include a project sponsor with real authority to make decisions, a project manager who owns the day-to-day schedule, and a representative from each department the new system touches (finance, operations, sales, whatever applies to you). If you're weighing whether to run this internally or lean on an outside partner, Who Should Lead Your ERP Implementation? Project Manager vs. Guided Self-Implementation lays out the tradeoffs between the two.
Once the team is in place, write down what you want out of this. "Faster financial close," "one system instead of five spreadsheets," and "better inventory visibility" are all fair goals, but they need to be specific enough that you can tell, six months from now, whether you hit them. If hiring or reassigning people into implementation roles is part of the plan, 10 Business Central Consultants Facts That Help Your Hiring Process is a useful read before you post the job description.
ERP Implementation Plans Step 2: Choose the Right System and Partner
This step gets rushed more than any other, usually because companies pick software first and think about the implementation partner later. That order causes problems. The partner you choose will shape your timeline, your budget, and how much support you get after go-live, sometimes more than the software itself does. How to Choose an ERP Consulting Firm: 7 Questions to Ask First is a good starting checklist before you sign anything, and The Microsoft Dynamics 365 Business Central Partner Checklist for Growing Companies narrows that down further if you already know Business Central is the platform.
For small and midsize businesses, this is also where the on-premises versus cloud decision gets made. If you're currently running Dynamics GP or NAV, this step usually means evaluating whether Dynamics 365 Business Central fits your industry, your data volume, and your growth plans over the next several years. Support for GP is winding down on a fixed timeline, which The Clock Is Ticking on Dynamics GP End of Life covers in detail. Sit down with a partner who has handled that specific migration before, since GP and NAV data structures don't map cleanly to Business Central without some planning. Manufacturers weighing several consulting firms against each other can see how that comparison played out in a specific market in Top 10 ERP Consulting Companies for Manufacturing in Houston.
This is also where it helps to know who's on the other end of that call. A BC Consulting Group is led by Shannon Mullins, a Microsoft MVP of Business Applications with more than 20 years of ERP and CRM implementation experience, backed by a staff averaging 18 years in accounting and technical development work. That combination gives clients a boutique team with senior-level expertise on every project, not a rotating cast of junior consultants.
ERP Implementation Plans Step 3: Map Your Current Processes
Before you can redesign anything, you need an honest picture of how work gets done today, not how the org chart says it should get done. This step in ERP implementation plans is where a lot of hidden complexity surfaces: manual workarounds, undocumented approval chains, spreadsheets nobody admits to using.
Walk through each core process (order to cash, procure to pay, financial close) with the people who do it daily. Document where data comes from, who touches it, and where it currently breaks down. This becomes the baseline your new system gets measured against. Regulated industries tend to surface the most hidden complexity here; Enterprise Resource Planning in Healthcare: What It Solves, What It Costs, What It Takes breaks down what that looks like for healthcare providers specifically.
ERP Implementation Plans Step 4: Design Your Future State Workflows
With current processes mapped, you can design how things should work inside the new system. Good ERP implementation plans lean toward the software's out-of-the-box functionality wherever possible, and reserve customization for the handful of processes that genuinely set your business apart.
This carries more weight than it sounds like it should. Heavy customization slows down implementation, adds cost, and complicates every future update, since custom code has to be re-tested and sometimes rebuilt each time the software gets upgraded. If a process can be redesigned to fit standard functionality without hurting the business, that's usually the better trade.
Gap analysis happens here too. Wherever the software doesn't naturally support what you need, your implementation partner can propose a configuration change, a workaround, or in rare cases, a small extension. Distributors tend to need a few specific workflow adjustments around lot tracking, bin management, and multi-warehouse fulfillment; Distribution Management System Software: A Buyer's Playbook for Growing Distributors walks through the ones that come up most.
ERP Implementation Plans Step 5: Clean and Migrate Your Data
Data migration is where a lot of ERP implementation plans quietly go sideways. It's tempting to move everything from the old system into the new one, but that just carries your bad data forward into a fresh environment.
A cleaner approach:
Decide how much historical data you need (most companies keep one to two years).
Remove duplicate records, inactive customers, and discontinued products before migration, not after.
Map fields from the old system to the new one and test the migration on a small batch first.
Validate the migrated data against the source before you trust it in production.
Set aside more time for this step than feels necessary. Underestimating data cleanup is one of the most common reasons ERP implementation plans slip past their original go-live date.
ERP Implementation Plans Step 6: Configure and Test the System
With workflows designed and data ready, configuration begins. This is where the theoretical parts of ERP implementation plans become a working system: setting up modules, permissions, approval workflows, and reports.
Testing should happen in layers. Start with individual features to confirm they work as configured, then move to full end-to-end testing where real users run through their actual daily tasks in the new system. This final round, often called user acceptance testing, is where you find out whether the system holds up under real workloads rather than a controlled demo. Don't skip this step to save time. A configuration issue caught in testing costs a few hours to fix. The same issue caught after go-live can cost days, plus the trust of the team who just found it the hard way.
ERP Implementation Plans Step 7: Train Your Team Before Go-Live
Training gets treated as an afterthought in a lot of ERP implementation plans, squeezed into the final week before launch. That's backwards. People need enough time with the new system to build real comfort before it becomes the only option.
Mix training formats where you can: live sessions for the workflows people use daily, short recorded videos for reference later, and hands-on practice in a test environment that mirrors production. Build training around each person's role rather than a single generic walkthrough for the whole company.
Identify a handful of power users in each department before go-live, and give them extra time with the system. They'll end up answering more day-to-day questions than your project team once things are live, simply because they're sitting next to their colleagues.
ERP Implementation Plans Step 8: Go Live With a Realistic Timeline
Go-live day is less of a finish line and more of a controlled handoff. Most ERP implementation plans use one of two approaches: a phased rollout, where you launch by department or business unit, or a full cutover, where everyone switches at once.
Phased rollouts lower risk and give you room to fix issues before they affect the whole business. Full cutovers are faster overall but leave less margin for error. The right choice depends on your team's size, how interconnected your departments are, and how much risk your business can tolerate.
Whichever route you take, keep your implementation team fully available in the days immediately following launch. Questions and small issues are normal. What counts is how quickly they get resolved.
ERP Implementation Plans Step 9: Support, Optimize, and Measure Results
The most overlooked step in ERP implementation plans is what happens after everyone's declared victory and gone back to their regular jobs. Go-live isn't the end of the project. It's the point where you start measuring whether the project delivered what you set out to achieve back in step one.
Revisit the goals you defined at the start. Are financial close times shorter? Is inventory visibility better? Are the reports your team relies on faster to pull and easier to trust? Use this feedback to fine-tune configuration, add features gradually rather than all at once, and keep training available for new hires long after the original launch date has passed.
Unsure If Your Data Is Ready to Migrate with ERP Implementation Plans?Our team at A BC Consulting Group can review your current data and flag cleanup issues before they turn into delays during your ERP implementation. |
What ERP Implementation Plans Cost and How Long They Take
There's no single number here, but ranges are useful for budgeting. Based on A BC Consulting Group's own project history, guided self-implementations, where a small business gets expert-led setup with a lighter touch than a full consulting engagement, often run in the low five figures and can be done in a few weeks. Distribution ERP Software: Is Guided Self-Implementation Right for Your Business? walks through who that lighter-touch model fits.
Full-service implementations with dedicated project management, data migration, and custom training typically run several months and scale from the mid five figures into six figures depending on company size, number of modules, and how much customization is involved. Licensing is a separate line item from implementation cost, and Business Central Licensing & Pricing Explained breaks down how Microsoft structures that piece.
For context, Panorama Consulting Group's ERP benchmark research puts average implementation costs across companies of every size well into six figures once software and services are combined, spanning everything from small-business rollouts to large enterprise deployments. That spread is exactly why a company-size-specific range carries more weight than a single industry average.
Timeline follows a similar pattern. A straightforward, single-entity Business Central implementation with clean data might take four to five months. A multi-entity company with legacy data from an older system like Dynamics GP or NAV should plan for six to nine months, sometimes longer if multiple departments are going live in phases.
A few factors tend to push the budget up regardless of company size: the number of legacy systems being replaced, industry-specific compliance requirements, and how many third-party integrations the new system needs to support, such as tax software, payroll, or ecommerce platforms.
If you want a firmer number, a Dynamics 365 Discovery session is the fastest way to get one. It reviews your current systems and processes before anything is quoted, so the estimate reflects your business rather than an industry average.
Common Mistakes That Derail ERP Implementation Plans
A few patterns show up again and again in stalled or over-budget projects. None of them are about the software failing. They're almost always about a step in the plan getting skipped, rushed, or handed off without enough attention. ERP Implementation Best Practices for Small and Mid-Sized Businesses covers the practices that head off most of the list below, and ERP Implementation Challenges (and How Guided Self-Implementation Avoids Them) goes deeper on how a lighter-touch model sidesteps a few of them entirely.
Treating the software choice as the whole decision. The implementation partner's experience with your industry and company size affects the outcome as much as the platform does.
Skipping or rushing process mapping. Without an honest look at current workflows, the new system ends up automating the same inefficiencies.
Underestimating data cleanup. Migrating messy data into a new system just gives you a cleaner-looking version of the same problems.
Compressing the training schedule. Adoption struggles are rarely about the software. They're usually about people not having enough time to get comfortable with it.
No plan for what happens after go-live. Projects that stop at launch day miss the chance to measure and improve on what they built, and the goals set back in step one never get revisited.
Don’t let mistakes or questions hold you back. If you’re ready to build your ERP implementation plans, a BC Consulting Group helps Nashville-area and US businesses plan and execute Dynamics 365 Business Central implementations from discovery through go-live. Book a Free Consultation →
Frequently Asked Questions
What is an ERP implementation plan?
An ERP implementation plan is a structured roadmap for moving a business from its current systems to a new ERP platform. It covers team roles, timeline, data migration, testing, training, and go-live strategy from start to finish.
How long does an ERP implementation plan usually take?
Most small and midsize ERP implementation plans take four to nine months. Simpler, single-entity projects with clean data land on the shorter end, while multi-entity companies migrating from older systems typically need more time.
How much does an ERP implementation plan cost?
Costs vary widely based on company size and scope. Guided self-implementations for small businesses can start in the low five figures, while full-service implementations with dedicated project management often run into six figures.
What's the difference between a phased and a big-bang implementation?
A phased approach rolls the new system out by department or business unit over time, which lowers risk but extends the overall timeline. A big-bang approach launches everyone at once, which is faster but leaves less room to catch issues before they affect the whole business.
Do small businesses need a formal ERP implementation plan?
Yes, even a lighter one. Skipping formal planning is one of the most common reasons small business implementations run over budget or over schedule, since undocumented data and processes tend to surface as expensive surprises mid-project instead of being caught early. A guided self-implementation still benefits from the same nine steps; they're just scaled down and move faster because the scope is smaller.
Comments