Implementing Business Central is one of the best investments a growing SMB can make — but only if you go in prepared. This guide covers what to expect from a BC implementation, how to prepare your team, and the pitfalls that derail most SMB ERP projects.
What a BC Implementation Actually Involves
Many SMBs underestimate what an ERP implementation involves. It's not just "installing software." A Business Central implementation requires:
- Business process redesign: BC's implementation is an opportunity to fix broken processes — not just digitize broken ones
- Significant internal time investment: Your key people need to be available for workshops, testing, and training
- Data preparation: Cleaning and formatting data from your current system for migration
- Change management: Getting your team ready for a new way of working
Typical BC SMB Implementation Timeline
- Weeks 1–2: Discovery workshops, requirements documentation, system design
- Weeks 3–7: Configuration, data migration preparation, basic customization
- Weeks 8–10: User acceptance testing (UAT), data validation
- Week 11: Final data migration rehearsal, cutover planning
- Week 12: Go-live weekend, hypercare begins
How to Prepare Your Organization
1. Designate a Project Champion
Every successful BC implementation has a dedicated internal project champion — typically the CFO, Controller, or COO. This person has authority to make decisions, resolve conflicts, and keep the project moving. Without executive sponsorship, implementations stall.
2. Allocate Key User Time
Your most knowledgeable business users will be needed extensively during the project. Plan for:
- Department leads: 30–40% time during workshops and UAT
- Finance team: 50%+ time during month-end close testing
- IT staff: 20–30% for system access, data extraction, integration coordination
3. Start Data Cleanup Now
The biggest hidden time sink in BC implementations is data cleanup. Start immediately:
- Customer master: Identify and resolve duplicate records, update contact info, clean address data
- Vendor master: Same as customers
- Item master: Clean up discontinued items, standardize units of measure, validate costs
- Chart of accounts: Decide which accounts to keep, merge, or restructure
4. Define Your "Go-Live Criteria"
Before the project starts, agree with your implementation partner on what "ready to go live" means. Define the minimum criteria for go-live: all critical business processes tested and signed off, open invoices migrated and reconciled, key users trained.
The Most Common BC SMB Implementation Pitfalls
- Scope creep: Adding features mid-project that weren't in the original scope. Every addition delays go-live. Use a formal change control process.
- Data migration underinvestment: Not allocating enough time for data cleanup and validation. Bad data in = bad data out.
- Training at the last minute: Users who haven't been trained resist the new system. Start training 2–3 weeks before go-live, not the day before.
- Going live at month-end or year-end: Don't go live during your busiest financial periods. Aim for the first week of a month, mid-quarter.
- Underestimating post-go-live support needs: The first month after go-live requires intensive support. Budget for it.
Questions to Ask Your BC Implementation Partner
- How many Business Central implementations have you completed in the last 12 months?
- Do your consultants hold Microsoft BC certifications (MB-800)?
- What is your methodology for data migration, and how many rehearsals do you run?
- What does your post-go-live support look like for the first 90 days?
- Can I speak with 2–3 reference clients in my industry?