So You’re Getting Business Central.
Now What?
A plain-language guide to what the journey looks like — before, during, and after go-live — from someone who has lived it.
“Deciding to implement a new ERP system is a big deal. It’s exciting, a little terrifying, and — if nobody warns you what’s coming — it can feel like you’re building the plane while flying it. Let’s fix that.”
Before We Dive In: Why Business Central?
Dynamics 365 Business Central — BC, as we’ll call it — is Microsoft’s ERP solution designed specifically for small to mid-sized businesses. Think of it as the system that finally brings your finances, your inventory, your purchasing, your projects, and your reporting under one roof, connected, and talking to each other.
If you’ve been running your business on QuickBooks, Sage, or — bless your heart — a patchwork of spreadsheets with a side of sticky notes, Business Central is going to feel like a significant upgrade. And it absolutely is. But like most significant upgrades in life, it comes with a learning curve and a process. And that process goes a lot better when you know what you’re walking into.
So let’s walk through it together.
Part 1: Things to Think About Before You Sign Anything
Here’s something the sales pitch won’t always tell you: the technology is rarely the hardest part of an ERP implementation. The decisions you make before the project even starts will shape everything that comes after. Here are the big ones.
Know Your Processes First
Before anyone configures a single thing, you need to understand how your business actually runs today. Not how the policy manual says it runs — how it actually runs. Those two things are often very different, and both matter.
Get Honest About Your Data
Whatever data lives in your old system is coming with you — and old data has a way of being messier than you remembered. Don’t wait until migration week to start cleaning it up. Start now. Seriously. Start now.
Pick Your Internal Champion
Every successful implementation has at least one person on the client side who owns it. Someone who asks the hard questions, makes decisions, and keeps their team engaged. Figure out who that is before day one.
A few other questions worth asking yourself before you get started: How many companies or legal entities will be on this system? Do you have inventory, and how complex is it? Are you doing project billing? Do you sell across state lines or internationally? These answers shape your license type, your configuration, and your timeline more than most people realize going in.
A word on scope: One of the most common implementation mistakes I see is trying to do everything at once. BC can handle a lot. You don’t have to implement it all on day one. Go live with your core financial processes, get stable, and then layer in the rest. Slow and steady wins this particular race.
Part 2: What an Implementation Actually Looks Like
Every implementation is a little different, but most follow a similar arc. Here’s the honest version of what you’ll move through:
01 Discovery & Design
This is where your implementation partner gets to know your business. You’ll walk through your processes, document your requirements, and make decisions about how BC will be configured to fit the way you operate. This phase sets the foundation for everything — and cutting it short is one of the fastest routes to a troubled go-live.
02 Configuration & Build
Your consultant takes all those decisions from discovery and starts building your system. Chart of accounts gets set up. Payment terms. Vendor records. Customer groups. Posting groups. (Don’t worry — I’ll do a whole post on posting groups. They deserve their own spotlight.) This phase is behind-the-scenes-heavy, but you should still be involved in review cycles.
03 Data Migration
Your opening balances, vendor and customer master records, historical data — this all needs to move from the old system into BC. Data migration is one of those things that looks easy on a project plan and is almost never easy in practice. Plan extra time here. Extra time and a whole lot of reconciliation.
04 Testing
You’ll test the system before go-live — and I mean really test it. Not “click around and see if it looks right” testing. Walk through your actual day-to-day transactions, end to end, in a sandbox environment. This is the phase where you find the gaps before they find you. Use it.
05 Training
Your team needs to know how to use this thing before you flip the switch — not on the day you flip the switch, and definitely not after. Good training is role-based (the AP clerk doesn’t need to learn everything the Controller needs to know) and hands-on. Watching someone else click through screens is not training. Doing it yourself is.
06 Go-Live & Hypercare
You flip the switch. The first few weeks in production are called hypercare — your partner should be very close, questions should be answered fast, and everyone should expect a higher-than-normal level of chaos. That’s normal. It settles. I promise it settles.
Part 3: The Pitfalls — Let’s Just Call Them What They Are
I’ve seen a lot of implementations. Great ones, rough ones, and a few that really tested everyone’s sense of humor. The same pitfalls show up over and over again. Here’s your early warning system.
Underestimating the Chart of Accounts Redesign
Moving to a new system is your chance to finally fix that chart of accounts that’s been duct-taped together for fifteen years. But restructuring it takes more thought and time than most organizations budget for. Your COA is the foundation of every report you’ll ever run.
→ Start the COA conversation early. Involve finance leadership. Don’t migrate the old structure just because it’s familiar.
Skipping the “Why” on Configuration Decisions
BC gets configured in hundreds of tiny ways that all add up. When decisions get made without documenting the reasoning behind them, you end up with a system that works — sort of — and a team that can’t explain why it’s set up the way it is. Future-you will be frustrated by past-you’s lack of notes.
→ Document configuration decisions as you go. A simple decision log goes a long way six months post-go-live.
The “We’ll Figure Out Training Later” Trap
Training always seems like the thing that can be pushed to the back of the timeline — right up until go-live week, when suddenly it’s a five-alarm problem. Undertrained users make mistakes in live data. Mistakes in live data are really not fun to fix.
→ Lock training into the project plan early and treat it as non-negotiable. Build in practice time in the sandbox before production access is granted.
Assuming BC Will Work Exactly Like Your Old System
It won’t. And honestly, some of the ways it works differently are genuinely better — but only if you give yourself time to understand the new approach instead of trying to force BC to behave like the thing you’re replacing. This is one of the hardest mindset shifts, especially for long-tenured staff.
→ Go in with curiosity, not comparison. Ask “why does it work this way?” before deciding it’s wrong.
Weak Executive Sponsorship
Implementations stall when decisions can’t get made and when resistance doesn’t have a counter-force. If leadership isn’t visibly invested and empowered to make calls, the project drags, the team disengages, and scope creep quietly takes over.
→ Executive sponsorship isn’t a title on a project plan. It’s active, ongoing participation. Make sure leadership knows what that means before the project kicks off.
Part 4: What Microsoft Is Building — The Exciting Stuff
Here’s what I genuinely love about Business Central right now: Microsoft is investing in it heavily and thoughtfully. The roadmap for 2025 and into 2026 is packed with features that are going to meaningfully change how people work in this system every day. Let me walk you through the highlights.
AI · Now -> Copilot — Built Right In
Copilot is included with your BC license at no additional cost, and it’s already doing real work. Bank reconciliation assistance, AI-generated record summaries on customers and vendors, natural language data analysis — these are live features helping users move faster today. The “Tell Me” search function has been upgraded with AI so it understands what you’re looking for even when you don’t know the exact menu name.
AI · Wave 2 -> Sales Order Agent
This one’s a genuine game-changer for any team still manually processing incoming orders. The Sales Order Agent reads customer emails and attachments, extracts the relevant details, and builds a sales order — automatically. It handles multiple shipping addresses, checks inventory, and flags anything that needs human eyes before moving forward.
AI · Wave 2 -> Payables Agent
Your AP team is going to like this one. The Payables Agent captures vendor invoices directly from your Microsoft 365 email, uses OCR to pull the data, matches them against purchase orders, and prepares them for approval — with human oversight built in. It learns from your historical posting patterns and gets smarter over time. It’s not replacing your AP staff; it’s getting rid of the part of their job nobody loves.
Reporting · Now -> Improved Financial Reporting
Financial reports are getting more flexible — dynamic column naming, expanded Word layout options, richer Power BI integration with drill-down directly into transactions from visuals, and enhanced data analysis with additional related tables. The goal is to get more usable information in front of decision-makers without requiring a data analyst to build every view.
Custom AI · 2026 -> Build Your Own Agents
BC is introducing a framework that lets you design your own custom AI agents directly inside the system — using natural language to define goals, with the agent reasoning through the steps to execute them within your permission boundaries. Every action is logged, sensitive steps require human approval, and it’s all tenant-isolated. This is automation that operates under control, not instead of it.
Sustainability · Now -> ESG & Sustainability Tracking
This is newer territory for an ERP, but BC is ahead of the curve. You can now track greenhouse gas emissions, water, and waste metrics directly in the system, set goals, monitor progress, and generate reports aligned with regulatory standards like CSRD. Copilot can even estimate emissions based on your journal entries. For organizations with ESG reporting requirements, this is significant.
One thing worth knowing about the AI features: While Copilot is included with your BC license, the autonomous Agent features (like the Sales Order Agent and Payables Agent) operate on a consumption-based billing model using Copilot Credits. Microsoft is still refining the pricing model, so if you’re budgeting for these specifically, check the current licensing guide before making assumptions. The last thing anyone wants is a surprise invoice.
So Where Does That Leave You?
If you’ve read this far, you’re already doing better than most people who walk into an ERP implementation unprepared. Understanding the landscape — what’s involved, what can go wrong, and what the system is becoming — gives you a real advantage as you move through this process.
The technology is genuinely good. Business Central is a capable, increasingly intelligent platform that can transform how your organization manages its finances and operations. The implementations that go well aren’t the ones with the most sophisticated configurations — they’re the ones where the humans were prepared, engaged, and willing to learn.
That’s the whole reason this blog exists. We’re going to go deep on the how-tos, the common questions, the “I was too embarrassed to ask” moments, and the features that will actually save you time once you know they exist.
Coming Up Next
We’ll dig into the Chart of Accounts in Business Central — what it is, why it matters more than you think, and how to set it up in a way you won’t regret in six months. If you’ve ever stared at a posting setup screen and felt your soul leave your body a little, that post is for you.
Until then — ask questions. Take notes. And please stop being afraid of the system. It’s just a tool. A very large, occasionally confusing, ultimately useful tool. And we’re going to figure it out together.
— Bobbi
D365 Functional Architect | Recovering Controller & Professor
Leave a Reply