// bitta apps · services
Business Central Implementation
Move from spreadsheets, QuickBooks, or legacy ERP to Microsoft Dynamics 365 Business Central — on a fixed-scope, fixed-price proposal, in 8 to 16 weeks.
Still closing the month in spreadsheets, or re-keying orders between QuickBooks and your warehouse? That's not a software problem you have to live with — it's a scoping problem we fix on a fixed price. Our implementation engagements cover discovery and fit-gap, data migration, configuration, integrations, role-based training, and a 30-day hypercare window after go-live. The senior team that scopes your project is the same team that delivers it — a named project manager and senior consultants, at least two of us in every meeting. We work remotely across the US and Canada under a Microsoft Cloud Solution Provider agreement.
What does a Business Central implementation include?
Discovery & fit-gap
We map your current processes to Business Central modules, surface real gaps early, and propose customization vs. standard where it matters.
Data migration
Chart of accounts, customers, vendors, items, open transactions — moved with validation and reconciliation reports you can sign off on.
Configuration & setup
Financial dimensions, posting groups, approval workflows, number series, permissions — configured the way your team works.
Integrations
Connect Business Central to Shopify, Salesforce, Azure Data Services, Power Platform, EDI, or bespoke APIs.
Training & change management
Role-based training for AP, AR, Sales, Inventory, and Finance users — recorded for onboarding future hires.
Go-live & hypercare
Scripted go-live cutover, 30-day hypercare with priority response, and a handoff plan for ongoing support.
The Bitta Apps delivery method
How long does a Business Central implementation take? Typically 8 to 16 weeks from discovery to go-live, depending on scope — and every project runs on the same method, with a written fixed-price proposal before any build work begins.
- 01
Discovery & scoping — week 0
A 30-minute structured call, then a working session on your systems, data, and integrations — enough depth to scope honestly.
- 02
Written proposal — 5 business days
A fixed-scope, fixed-price proposal with milestones, deliverables, and a committed go-live date. One number, before any work begins.
- 03
Configure & build — weeks 1–8
We configure Business Central, migrate and validate your data, and build the required integrations and extensions.
- 04
Migrate & train — weeks 6–12
Final data loads, UAT against your real workflows, and role-based training — recorded so future hires get the same onboarding.
- 05
Go-live + 30-day hypercare — weeks 8–16
Scripted cutover, 30 days of priority hypercare from the team that built it, then a clean handoff to ongoing support if you want it.
Frequently asked
How long does a Business Central implementation take?+
Typical go-live is 8 to 16 weeks. Finance-first projects with clean data land near the front of that range; multi-entity structures and integration-heavy scopes run toward the back. We commit to a firm go-live date in the written proposal and manage the project to it — the fastest way to get a real date for your situation is a 30-minute discovery call. Book a discovery call →
What does a Business Central implementation cost?+
Every engagement is fixed scope, fixed price: after discovery you receive a written proposal within five business days, with milestones, deliverables, and one number — before any work begins. We don't publish service rates because an honest price depends on your data, integrations, and entity structure; a generic figure would mislead you in one direction or the other. Microsoft licensing is separate and billed at list rates — Essentials $80, Premium $110, Team Members $8 per user/month. How our pricing works →
What does Business Central cost per user?+
As a Microsoft Cloud Solution Provider we bill licenses at Microsoft's published list rates: Business Central Essentials is $80 per user/month, Premium is $110, and Team Members — for approvals, time entry, and read-mostly users — is $8. Most businesses run a mix rather than full seats for everyone. License sizing is part of every implementation, so you go live paying for what people actually do in the system. Licensing & CSP →
Do we need Essentials or Premium?+
Premium adds manufacturing and service management on top of everything in Essentials — if you don't run production orders or service contracts, Essentials is almost always the right call. The catch is that all full users in a tenant must be on the same tier, so one Premium requirement moves everyone. We map roles to tiers during discovery rather than defaulting you upward. Essentials vs Premium vs Team Members, compared →
Can you migrate us from QuickBooks?+
Yes — moving off QuickBooks is the single most common starting point for Business Central. We migrate your chart of accounts, customers, vendors, items, and open transactions, with validation and reconciliation reports you sign off on before cutover. History you choose not to migrate stays available in read-only QuickBooks, which keeps scope and cost down. QuickBooks to Business Central migration →
How do we know it's time to leave QuickBooks?+
The pattern is consistent: month-end close stretching past a week, inventory or job costs tracked in spreadsheets next to the books, multiple entities consolidated by hand, and audit or lender requirements QuickBooks can't evidence. Any two of those usually mean you're paying more in workarounds than an ERP would cost. We've written up the decision in detail — including the cases where staying on QuickBooks is the right answer. When to switch from QuickBooks to Business Central →
Will our customizations break when Microsoft updates Business Central?+
Not if they're built correctly. Business Central customizations are AL extensions that sit alongside Microsoft's base application instead of modifying it, and we build to AppSource-grade standards even for private extensions. Microsoft ships two major release waves a year, and preview environments let you regression-test before each wave reaches production. AL extension upgrade strategies →
What happens after go-live?+
Every implementation includes 30 days of hypercare — priority response from the same team that built your system, while real transactions shake out the edge cases. After that, ongoing support is available on a monthly retainer covering break/fix, enhancements, monitoring, and advisory; staying fully self-sufficient is fine too. Either way, you're never handed off to a separate support bench. Support & managed services →
Do you fix stalled or failed implementations?+
Yes — stalled projects and inherited environments are a recovery path we know well. We start by assessing where the project actually stands — configuration, data, custom code, and what's salvageable — then propose the remaining work at a fixed price. You get a candid read, including when the previous partner's work is worth keeping. Rescue projects under AL Development →
Who actually works on our project?+
The team that scopes your project is the team that delivers it — a named project manager and senior consultants, with at least two of us in every meeting. Nothing is handed to a bench after the contract is signed. We deliver remotely across the US and Canada, with on-site visits available for key milestones like go-live. About Bitta Apps →