9 Steps to an ERP Cloud Migration That Doesn't Wreck Your Timeline

Key ERP Cloud Migration Takeaways

• What this move really counts as, and what doesn't. Swapping servers isn't the same as a routine software update. It touches your data, your integrations, your reporting, and how your whole team logs in every day, so it needs a real plan.

• The three strategies you can choose between. Rehosting, re-platforming, and re-architecting each trade speed against how much of your current process gets fixed along the way. Picking the wrong one for your business is one of the costliest mistakes to make.

• Realistic SMB timelines and budgets. Most published benchmarks are written for enterprise IT departments with six-figure budgets and a year to spare. Small businesses can expect 8 to 14 weeks, midsize businesses 3 to 6 months, and the biggest cost driver is customization, not headcount.

• How to tell if you need a partner. Some internal teams can handle a simple move alone. Most benefit from bringing in someone who's done this before and can catch a problem in week two instead of week ten.

Somewhere between "let's move to the cloud" and being live on a new system, a lot of ERP cloud migration projects quietly go sideways. Budgets creep, timelines double, the team that was supposed to be running the business instead spends three months untangling spreadsheets.

None of that is inevitable. An ERP cloud migration is a known, repeatable process, not a mystery box. The businesses that get through it cleanly tend to follow the same nine steps, in roughly the same order, whether they're a 40-person distributor or a 400-person manufacturer.

This breaks down what those steps look like in practice, with realistic timelines and costs for small and midsize businesses specifically, since most of what's written on this topic is aimed at enterprise IT departments with budgets and timelines that don't apply to a leaner team.

If you've searched around for advice already, you've probably noticed the same pattern we at A BC Consulting Group did: most published advice is written for large enterprises with dedicated IT staff and a year to spend on the project. A 30-person distributor or a 60-person healthcare group doesn't have those luxuries, and doesn't need them. The steps below work whether this is your first major system change or your second attempt at getting it right.

What Is an ERP Cloud Migration?

An ERP cloud migration is the process of moving your enterprise resource planning system, the software running your finances, inventory, and operations, off local servers and onto a cloud-hosted platform. For most small and midsize businesses today, that means leaving an on-premises system like Dynamics GP or NAV and moving to Business Central.

It's not the same as a routine software update. An ERP cloud migration touches your data, your integrations, your reporting, and how your team works every day, which is why it needs a plan instead of a weekend project mindset. See ERP Implementation Best Practices for Small and Mid-Sized Businesses for a wider view of what makes these projects succeed.

Step 1: Get Clear on Why You Want an ERP Cloud Migration

Before touching any data, write down the real business reason for the project.

Maybe your current system is losing vendor support, or your team is stuck manually reconciling reports that should be automatic, or it could even be that remote access has turned into a recurring headache.

An ERP cloud migration driven by a clear, specific pain point stays on track far better than one driven by a vague sense that "we should probably move to the cloud eventually." The reason you write down here becomes the yardstick for what's in scope later.

A few real examples we hear often from clients:

• Our current vendor is ending support for the version we're running

• Finance closes the books on a spreadsheet because the system can't produce the report they need

• Nobody can log in from home, which became a real problem the last time weather closed the office

• We just acquired another company and now we're running two disconnected systems

Any one of these is a legitimate starting point. The point is picking one and writing it down, so nobody's asking six months from now why the project ballooned into something else entirely.

Step 2: Choose the Right ERP Cloud Migration Strategy

There are three broad approaches to an ERP cloud migration, and picking the wrong one is one of the most expensive mistakes a business can make.

Rehosting

Moves your existing setup to the cloud with minimal changes. It's the fastest option, and a reasonable fit if your current processes already work and you just need out of an aging server room. The tradeoff: any inefficiency baked into your old workflows comes along for the ride.

Re-Platforming

Makes moderate adjustments during the move, cleaning up a few broken workflows without a full redesign. Most SMBs land here, since it balances speed against the chance to fix what's been bothering the team. This is usually where a business fixes the two or three workarounds everyone complains about but nobody's had time to address. Whichever approach you land on, ERP Implementation Challenges (and How Guided Self-Implementation Avoids Them) covers the common trip points to plan around.

Re-Architecting

Rebuilds processes from the ground up around what the new cloud platform can do. It takes the longest and costs the most, but it's the right call if your current processes were built around limitations your old system no longer has, or if a merger or major growth means the old process map doesn't reflect the business anymore.

If you're also deciding whether to run this in-house, Who Should Lead Your ERP Implementation? Project Manager vs. Guided Self-Implementation compares both models.

Step 3: Assess Readiness Before Your ERP Cloud Migration

Not every business is equally ready to start. A short readiness assessment, usually a few weeks, looks at your data quality, how customized your current system is, and whether your team has bandwidth to take this on alongside their regular jobs.

Skipping this step is where a lot of ERP cloud migration timelines quietly blow up. Problems that would've taken a day to fix in week one instead surface in week twelve, after they've already been built into three other parts of the project.

A good readiness assessment covers a handful of plain, practical points: how many years of historical data need to move versus what can be archived, which custom reports or fields the team has built up over time (including ones nobody remembers the purpose of), and who on staff can dedicate real hours to this without dropping their day job. Answering these honestly up front turns a rough timeline estimate into a real one.

If a self-guided approach is on the table, Distribution ERP Software: Is Guided Self-Implementation Right for Your Business? breaks down when that model fits.

Step 4: Clean Your Data Before the ERP Cloud Migration

Moving messy data to a new system just gives you the same problems in a shinier interface. Before migration, someone needs to go through your customer records, vendor lists, and inventory data and decide what's accurate, what's duplicated, and what's simply dead weight from a system you stopped using years ago.

This is tedious work, and it's also the single highest-leverage thing you can do to make the rest of your ERP cloud migration go smoothly. Clean data now means fewer support tickets and fewer "why doesn't this number match" conversations after go-live.

Healthcare organizations often carry extra data governance requirements on top of the basics above, covered in Enterprise Resource Planning in Healthcare: What It Solves, What It Costs, What It Takes.

Step 5: Set a Realistic ERP Cloud Migration Timeline

Most of the timelines published online are written for enterprise companies with dedicated IT departments, and they don't translate well to a smaller team. For a small business with a straightforward setup, plan on 8 to 14 weeks. A midsize business with a few custom workflows or integrations is usually looking at 3 to 6 months.

Businesses with heavy customization, multiple locations, or industry-specific compliance needs (healthcare is a common example) should plan for 6 months or longer. If a vendor promises a company-wide ERP cloud migration in two weeks flat, that's a claim to question rather than one to trust. Healthcare organizations should read Healthcare ERP Implementation Services: How to Go Live in 8–12 Weeks, since compliance tends to stretch the timeline.

Budget follows a similar pattern. A lean rehosting project for a small business sits at the lower end of what most partners quote, while a re-architected project for a 200-person company with several integrations sits much higher. The biggest cost driver isn't company size on its own, it's how much custom code and how many third-party integrations the old system has accumulated. Two companies the same size can see very different price tags for that reason, a point covered in How Much Does a Business Central Implementation Really Cost?

What Our Clients Say

Budget concerns come up in almost every conversation we have about a move like this, so we'll let a client speak to that directly instead of us. Lou Krupp, CFO of Denver Wholesale Florist, a distribution business that went through this exact process with our team, shares what the investment looked like on the finance side.

Step 6: Build Change Management Into the ERP Cloud Migration

The software is rarely the part that fails. People are. A team that's used their old system for a decade needs real training, not a single afternoon webinar, and they need to understand what's improving for them, not just what's changing.

Identify a couple of internal champions early, people on the finance or operations team who pick up the new system quickly and can answer their coworkers' questions in real time. That informal support does more for adoption than any amount of official documentation.

Step 7: Test Before You Finish the ERP Cloud Migration

Testing isn't a formality tucked in at the end. It should run in parallel with the rest of the project. Have real users run real transactions in the new system before go-live: process an actual invoice, close an actual month, run an actual report someone depends on.

Anything that breaks during this phase is cheap to fix. The same problem discovered after go-live, when the whole company is depending on the new system, is expensive and stressful to fix instead.

Step 8: Plan for Life After the ERP Cloud Migration

Go-live isn't the finish line. Budget time and support for the first 60 to 90 days after launch, since that's when small gaps in training or configuration surface. Set up a clear channel for staff to report issues, and check in on adoption, not just whether people are logging in, but whether they're using the features that were the point of the project.

An ERP cloud migration that's declared "done" the day the system goes live tends to lose momentum right when it needs the most attention.

Step 9: Choose an ERP Cloud Migration Partner

Some businesses have the internal expertise to run this alone. Most don't, and that's not a knock on their team, it's a specialized skill set most companies don't need year-round. A good partner has done this migration path before and can flag a problem in week two instead of week ten.

When evaluating an ERP cloud migration partner, ask for references from businesses your size, not just their biggest logo. A partner who's migrated a dozen 500-person enterprises may not be the right fit for a 30-person distributor, and vice versa. How to Choose an ERP Consulting Firm: 7 Questions to Ask First lays out the core questions to ask, and The Microsoft Dynamics 365 Business Central Partner Checklist for Growing Companies gives you a structured way to compare candidates.

In a regulated field, How to Evaluate a Healthcare ERP Consulting Firm: 7 Questions to Ask Before You Sign covers compliance-specific criteria, and manufacturers can start with Top 10 ERP Consulting Companies for Manufacturing in Houston as a regional comparison.

What an ERP Cloud Migration Looks Like in Practice

A Nashville-area manufacturer we worked with was still running Dynamics GP on an aging in-house server, with monthly close taking finance the better part of two weeks. Their ERP cloud migration to Business Central followed a re-platforming approach: core processes stayed intact, but a few manual workarounds built up over the years got rebuilt as automated workflows.

The project ran just under four months, in line with the midsize timeline above. Close time dropped from roughly two weeks to a few days, and the team gained real-time visibility into inventory across their distribution operation for the first time. None of that came from the software alone. It came from the data cleanup in step 4 and the change management work in step 6.

That inventory visibility isn't unique to this one client. It's a standard reporting capability in Business Central once you're migrated, and it holds up well in a short demo:

Inventory on Hand Reporting in Business Central: Tips and Tricks

A BC Consulting Group’s founder and CEO, Shannon Mullins, walks through how to set up item ledger entry views to see real-time inventory on hand, filter by location, and save the view for repeat use. It's the same reporting capability that gave the Nashville manufacturer above visibility they didn't have on their old system.

If your business looks more like a distributor, Distribution Management System Software: A Buyer's Playbook for Growing Distributors covers that side in more depth. Manufacturers should see Best ERP Software for Manufacturing Companies: How to Evaluate Your Options. Talk to team that has done this before. From Dynamics GP to Business Central, we've guided SMBs across manufacturing, distribution, and healthcare through their migration. Book a Free Consultation.

ERP Cloud Migration Frequently Asked Questions