By Vanguard 360 Solutions · 23 June 2026
If the phrase “ERP implementation” makes you think of 18-month waterfall projects, blown budgets, and people quietly updating their LinkedIn profiles, you’re not alone. The industry hasn’t always covered itself in glory.
But a Business Central implementation, done well, doesn’t have to feel like that. It can be an agile, transparent process where you see working software in weeks, not months — and where go-live is the beginning of a partnership, not the end of a hostage situation.
This article walks through exactly what a Business Central implementation looks like — phase by phase — from the Vanguard 360 approach. We’ll cover timelines, what’s expected of you, what your partner handles, and the parts nobody tells you about.
First, the Honest Truth About Timelines
“How long does it take?” is usually the first question — and the most honest answer is: it depends.
| Scope | Typical Duration | Examples |
|---|---|---|
| Lightweight — finance core only, clean data, no integrations | 6–10 weeks | Company migrating from QuickBooks, single entity, simple chart of accounts |
| Standard — finance + supply chain, data migration from legacy system, some integrations | 3–5 months | Mid-size distributor with inventory, purchasing, and basic reporting needs |
| Complex — multi-entity, manufacturing, retail (LS Central), heavy integrations, custom development | 5–9 months | Manufacturer with production orders and routings, or multi-country retailer with POS — see our implementation services for examples |
These aren’t calendar-time-padded estimates. They reflect real project experience. The biggest variable isn’t the software — it’s data readiness and decision-making speed on the client side.
A critical principle: you don’t have to do everything at once. A phased rollout — finance first, then operations, then advanced modules — is often smarter than a big-bang go-live. It reduces risk, gives your team time to absorb change, and gets you value faster.
Phase by Phase: The Agile Approach
Vanguard 360 runs implementations in agile sprints. That means you see progress continuously — not at a single UAT session months after the project started. Here’s how it breaks down.
Phase 1: Project Initiation (Week 1)
The kick-off meeting sets the tone for the entire project. We bring together your executive sponsor, your project lead, key department heads, and our implementation team. The goals:
- Align on scope: what’s in, what’s out, what’s phase 2
- Define the project governance: who decides what, escalation paths
- Confirm the sprint cadence and communication rhythm (weekly stand-ups, sprint reviews)
- Set up your sandbox environment so you can see work in progress from day one
- Identify risks early — data quality, customizations, upcoming business changes
Your role: Assign a project lead — someone with authority to make decisions and time to dedicate. This person is the single most important success factor. We’ve seen projects with mediocre data and excellent project leadership succeed, and projects with perfect data and absent leadership stall.
What we handle: Environment provisioning, project plan, governance framework, initial discovery.
Phase 2: Requirements (Weeks 1–3)
This isn’t a 200-page BRD that nobody reads. We run focused workshops with each functional area — finance, sales, purchasing, warehouse, operations — to understand how your business actually works, not how it says it works in the org chart.
Key outputs:
- Process maps (current state and desired future state)
- A prioritized requirements backlog (must-have vs. nice-to-have)
- Integration inventory: what systems talk to what, and how
- Data migration scope: what comes over, what gets archived
Your role: Make the right people available for workshops. These aren’t two-hour meetings — they’re working sessions where real decisions get made. If the person who knows the purchasing workflow isn’t in the room, we’ll build the wrong thing.
What we handle: Facilitation, documentation, gap analysis, scope recommendations.
Phase 3: Solution Design (Weeks 2–5)
With requirements understood, we design the solution architecture:
- Chart of accounts structure and dimensions
- Financial posting groups and VAT setup
- Inventory and warehouse configuration (locations, bins, item templates)
- Approval workflows
- Role centers and security profiles
- Integration patterns (APIs, file-based, Power Automate)
- Customization decisions: what’s configuration, what’s an extension, what’s a “let’s see if the standard feature works first”
This phase overlaps with requirements — we don’t wait for a finished spec before we start designing. Agile means parallel tracks.
A note on customizations: Business Central’s extension model means we never touch the base code. Everything we build sits cleanly on top as AL extensions. When a client needs something that doesn’t exist yet — a compliance module, a specialized integration — we build it. Our product suite — Romanian localization, SAF-T, e-Invoice, e-Transport, and more — was born exactly this way: from real client needs, refined across implementations. This makes upgrades smooth — Microsoft can update the base system and your customizations stay intact. It’s one of the biggest improvements over the old Dynamics NAV model.
Your role: Review and sign off on design decisions, especially around financial structure (CoA, dimensions) — these are hard to change later.
What we handle: Solution architecture, configuration design, integration design, extension specification.
Phase 4: Build & Configure (Weeks 3–ongoing)
This is where the system takes shape, in 2-week sprints. Each sprint:
- We configure or develop a specific set of features from the backlog
- At the sprint review, you see working software — not screenshots, not mockups
- You give feedback; we adjust the next sprint accordingly
Typical work in this phase:
- Core setup: company, CoA, dimensions, posting groups, currencies
- Master data templates and imports
- Process configuration (sales cycle, purchasing cycle, warehouse flows)
- Extension development (if customizations are needed)
- Integration build-out
- Reporting and analytics setup (Power BI, native reports)
Your role: Attend sprint reviews. Test what’s built. Give honest feedback. The worst thing you can do is stay silent during sprints and surface concerns at UAT — by then, rework is expensive.
What we handle: All technical delivery — configuration, development, testing, demos.
Phase 5: Data Migration (Weeks 4–ongoing, intensifies pre-go-live)
Data migration is the phase that most often bites. It’s not just about export-and-import — it’s about cleaning and mapping.
The process:
- Extract data from your legacy system(s)
- Profile it — identify duplicates, inconsistencies, missing fields
- Cleanse — fix what needs fixing (often in partnership with your team)
- Map — define how each field in the old system maps to Business Central
- Transform — convert data formats, apply business rules
- Load — import into the sandbox environment
- Verify — run reconciliation reports, check balances, confirm open transactions
We typically run multiple migration dry runs before the final cutover. The final migration happens over a weekend or a defined cutover window, with verification before users log in Monday morning.
What usually needs the most love: Item master data (inconsistent descriptions, duplicate SKUs, missing units of measure), open transactions (partially shipped orders, partially paid invoices), and customer/vendor balances that don’t agree with your subledgers because of years of workarounds.
Your role: Own the data. We provide the tools, templates, and guidance — but only your team knows which vendor is still active and which is a duplicate. Budget time for data cleansing; most companies underestimate it.
What we handle: Migration tooling, mapping, transformation scripts, validation, reconciliation reports.
Phase 6: Testing & User Acceptance (Weeks 5–final)
Testing happens in layers:
- Unit testing — we test each configured feature as it’s built (ongoing during sprints)
- Integration testing — end-to-end flows across modules: quote → order → ship → invoice → payment
- User Acceptance Testing (UAT) — your team runs real-world scenarios, ideally using your actual data in the sandbox
- Performance testing — for higher-volume operations, we verify response times and batch processing
UAT isn’t a formality. It’s your team’s opportunity to confirm the system works for your business before go-live. We provide test scripts, but the best UAT comes from users trying to do their actual jobs — entering real orders, processing real invoices, running real reports.
Your role: Allocate dedicated UAT time. This isn’t something your team does between meetings. The people who will use the system every day should participate.
What we handle: Test environment, test scripts, bug tracking, fixes, retesting.
Phase 7: Training (Weeks 6–8, intensifies in final 2 weeks before go-live)
Training is layered:
- Process training — “Here’s how your sales cycle works in Business Central” — context-rich, not just button-clicking
- Role-based training — tailored sessions for finance, sales, purchasing, warehouse, etc.
- Admin training — for your internal IT/operations person who’ll handle user setup, permissions, and first-line support
- Hands-on practice — guided exercises in a training environment with your own data
We record key sessions so new hires can ramp up later. We also deliver clear, concise reference guides — not 300-page PDFs nobody will ever open.
Your role: Make training mandatory. Protect the time. If the warehouse supervisor doesn’t attend training because “it’s busy season,” the warehouse will struggle post-go-live.
What we handle: Training materials, sessions, recordings, reference guides.
Phase 8: Go-Live & Post-Go-Live Support (Week 8+)
Go-live isn’t a single button press. It’s a structured cutover:
- Final data migration from the legacy system
- Verification: open balances, inventory counts, bank reconciliations
- System switch — users log into Business Central
- Hypercare period (typically 2–4 weeks): our team is on standby for immediate support, questions, and snags
- Post-implementation review (4–6 weeks after go-live): we look at usage stats, adoption patterns, and tune what needs tuning
The hypercare period is critical. Users will have questions — even with great training. Having the implementation team available in real time (Slack, Teams, phone) makes the difference between “this is new but I’m figuring it out” and “this isn’t working and I’m going back to spreadsheets.”
Your role: Be present. Leadership visibility during go-live signals that this matters. If the CFO is on the floor asking how it’s going, adoption follows.
What we handle: Cutover execution, hypercare support, issue resolution, post-go-live review and tuning.
What Nobody Warns You About
After 50+ implementations, here’s what we’ve learned — the patterns that show up regardless of industry:
1. The hardest part isn’t the software — it’s the decisions. Configuring Business Central is straightforward. Deciding on your chart of accounts structure, your dimension strategy, your inventory costing method — those decisions require business judgment that no consultant can make for you.
2. Data migration is always bigger than you think. Every company has skeletons in its legacy data. Duplicate customers with different naming conventions. Inventory items that have never been cycle-counted. Open transactions from three years ago that were “going to be cleaned up.” Start the data conversation early.
3. Change management is the invisible project. People who have done their job a certain way for 10 years won’t embrace a new system just because it’s better. They need to understand why the change is happening, how it makes their work better, and that they’ll be supported through it. Communication from leadership is the multiplier here.
4. Post-go-live, the work isn’t over — it shifts. The first month is about stabilization. The second month is about optimization. By month three, you’ll start identifying things you want to tweak. That’s normal. Expect it, budget for it, and maintain the partnership with your implementation team.
Is Your Business Ready?
An ERP implementation is one of the biggest changes a company can make. It touches every department. It will surface process problems you’ve been working around for years. It’s uncomfortable in the middle.
But on the other side — when your finance team closes the month in two days instead of two weeks, when your warehouse knows exactly what’s in stock without a physical count, when sales can quote from real-time inventory — it’s transformative.
If you’re considering a Business Central implementation and want to talk through what it would look like for your specific business — timelines, scope, data migration, the whole picture — book a free discovery call. No obligation, no pressure. Just an honest conversation about where you are and where you want to go.
Vanguard 360 Solutions is a Microsoft Dynamics 365 Business Central partner and LS Retail Gold Partner. We’ve completed over 50 end-to-end implementations across Europe, the UK, UAE, and Saudi Arabia.