The capacity ceiling in a Business Central practice is predictable, and most consultants hit it in the same order.
You win more work than you can comfortably serve. You consider hiring, which is slow, expensive, and adds fixed overhead against project revenue that is anything but fixed. You consider turning work away, which solves the scheduling problem and creates a pipeline problem. You end up doing some of both, and the practice grows in steps rather than smoothly.
What makes this frustrating is that the ceiling has little to do with expertise. A consultant who has delivered a dozen implementations knows exactly what a thirteenth needs. The ceiling is about hours, and more precisely about where those hours go.
Where the time goes
An implementation starts well before the work a client would recognise as consulting.
Before anything can be configured to fit a business, the data has to move. Chart of accounts, customers, vendors, items, outstanding invoices, opening balances, bank entries, fixed assets, and whatever history the client needs carried forward. All of it has to come out of the source system, be cleaned, be mapped onto Business Central's structure, be loaded somewhere safe for testing, and be checked before anyone signs anything off.
This stage has the worst ratio in the engagement. It absorbs senior time. It produces nothing the client can see. And it is the part clients are least willing to pay for at the rate it costs to deliver, because from the outside it looks like copying.
You will have a number in your head for what that stage costs on a typical project. Whatever it is, it is more reliable than any benchmark someone else could offer you, and the useful thing about it is this: it barely changes from one client to the next. The business is different every time. The extraction and mapping work is close to identical.
That repetition is the opening.
What changes when the migration stage is automated
Qwyk is a Business Central onboarding and support platform built for Microsoft Partners. BC consultancies use it to take the data migration stage off the project plan.
The platform connects to the client's source system, which can be Xero, QuickBooks, Sage, Dynamics GP, Dynamics NAV, or a CSV export where no API exists. On-premise systems are reached through a lightweight agent deployed from the portal onto the machine holding the data. The platform extracts, maps to Business Central with AI assistance, and runs quality checks: duplicate detection, account mapping suggestions, address and VAT format cleaning.
Everything lands in a fully audited sandbox. Nothing reaches production until you have reviewed it and pushed it live, which is a single step. A basic onboarding from a supported source runs in under 30 minutes. More involved migrations run in days rather than months.
Your role in that stage becomes review and approval rather than extraction and mapping. The platform surfaces what needs a human decision. The rest runs without you.
What that does to the practice
Removing a stage from every project is not the same as making every project slightly faster.
The same team runs more engagements in parallel, because the bottleneck that used to sit at the front of each one has gone. More of your billable hours go to configuration, process design, training and advisory work, which is both better paid and more interesting than data handling. And the cost base of each project falls, which means the margin improves whether or not you change what you charge.
What you charge is entirely your decision, incidentally. Some partners keep their existing implementation pricing and take the margin. Others price lower to win work they would otherwise lose. The platform cost to you is fixed either way.
The engagements you currently decline
There is a second effect that is easy to miss, and for some practices it matters more than the first.
Most BC consultancies carry a list of opportunities that never became proposals. The client is too small, the deal does not justify the setup time, the finance-only scope would not cover the manual work at the front. So the conversation tails off, and eventually someone else takes it or the client stays where they are.
When the foundation is automated, those engagements change shape. Work that could not carry the cost of a traditional implementation becomes viable, and it becomes viable without you lowering your standards or your rate. For practices that have been turning away the bottom of their market for years, that is a larger pool than the capacity gain.
Support, as the book grows
Implementation capacity is one constraint. The other arrives later.
Every live client adds support obligation. Tickets, questions, change requests, the small configuration jobs that are too minor to scope and too frequent to ignore. A growing book means a growing support load, and support is harder to batch than implementation work because it arrives when it arrives.
The platform includes support tooling that runs natively inside Business Central rather than alongside it. Clients raise tickets from the web portal or from inside their own BC environment, and those tickets sync both ways in real time. SLA timers and breach flagging are built in, as is satisfaction scoring, which you can see per client and across the whole book. Tickets convert to change requests in one click, and change requests carry a formal estimation, quoting and approval workflow rather than living in email.
The knowledge base is the part most practices underuse. Articles can be built from resolved tickets, which means the second client to ask a question does not generate a second ticket.
An AI agent handles tickets in the background with a confidence score on every resolution. Anything below the threshold is flagged for a person. Anything above it closes itself.
How involved you want to be
Three delivery modes, chosen per client rather than per practice.
Run the migration yourself through the partner portal. Hand it to the client to self-serve through a guided wizard. Or have Qwyk run it on your behalf, which is what most partners use when volume arrives faster than the calendar allows.
The same choice applies after go-live: your team supports the client, or Qwyk provides managed support behind your brand. In every case the client relationship is yours, and the client sees you rather than Qwyk.
What this does not remove
It would be a poor argument to suggest automation turns an implementation into a push-button exercise, and a BC consultant would see through it immediately.
Deciding how a client's chart of accounts should be structured still needs someone who understands the business. Manufacturing, service management, project accounting and industry-specific configuration still need building. Integrations to warehouse systems, EDI, payroll and reporting tools still need designing. Users still need training, and a finance team still needs a parallel run they trust before they will close a period on a new system.
None of that is going anywhere, and none of it should. It is the work that justifies your rate.
What changes is that it stops being preceded by a fortnight of data handling that nobody enjoys and nobody wants to pay full price for.
Where to start
The honest first step is not a trial. It is a look at your own numbers.
Take the last three implementations you delivered. Work out what proportion of the hours went to extraction, mapping, cleansing and reconciliation before configuration began. Then ask what the practice would look like if that proportion were close to zero.
If the answer is one more project per quarter, the maths is marginal. If the answer is three, or if it is a category of client you have been declining for years, it is worth a conversation.
The same logic applies to the legacy deadlines already in your book. Dynamics GP support ends in 2029 and NAV 2017 goes out of extended support in January, and both of those arrive as concentrated demand rather than a steady flow. Capacity planning for that is the same exercise, with a deadline attached.
Qwyk is a Business Central onboarding and support platform for Microsoft Partners. MSPs, systems accountants and BC consultants use Qwyk to migrate clients from Xero, QuickBooks, Sage, Dynamics GP and Dynamics NAV into Microsoft Dynamics 365 Business Central, automatically, in minutes. Partners choose how involved they want to be, and they always keep the client relationship.
Find out more on our page for BC consultants, our page for MSPs, our page for systems accountants, or the partner FAQ.