Agentic onboarding is a way of moving a business onto Microsoft Dynamics 365 Business Central in which software agents carry out the migration work: pulling data out of the old system, mapping it to Business Central, cleaning it and configuring the new environment. People review what the agents have produced and approve it before anything reaches the live system.
The term is turning up more often in conversations about Business Central, usually with little explanation attached. This piece sets out what it means in practice for a Business Central migration, and where the agents hand over to people.
How a Business Central migration usually runs
Anyone who has run a migration from Xero, Sage or QuickBooks will recognise the pattern. Data is exported from the source system into spreadsheets. Someone works through the chart of accounts and decides where each account belongs in Business Central. Customer and vendor records are de-duplicated by eye. Addresses and VAT numbers are corrected a row at a time. Business Central is configured by hand, a test import goes into a sandbox, errors come back, and the cycle repeats until the balances tie out.
For an experienced consultant this work is familiar and slow. It grows with the size and untidiness of the client's data rather than with the complexity of their business, and clients like paying for it least, because nothing visible comes out of it until the end. It is a large part of why a traditional Business Central implementation typically runs for three to six months.
What changes when the work is agentic
The same stages still happen in an agentic onboarding, with agents carrying out most of the work in each. On the Qwyk platform the process runs in four steps.
Connect the source. The platform connects to Xero, Sage, QuickBooks, Dynamics GP or a CSV file. Where the source system has an API, it uses that. Where it is an older on-premise installation with no API, a lightweight agent is installed on the machine holding the data and sends it to the platform.
Extract, map and configure. Agents extract the data and map it to Business Central. They suggest where each account belongs, flag likely duplicate customers and vendors, clean address and VAT formats, and build the Business Central environment from a ready-made template: finance only, finance with inventory for distributors, or finance with inventory for retail and eCommerce, which includes a Shopify connection.
Review in a sandbox. Everything lands in a fully audited sandbox. The partner, and the client if the partner chooses, reviews the mapping, the balances and anything the agents have flagged.
Go live. Once the partner signs off, the sandbox is pushed to production in a single step.
For a basic onboarding from a supported source system, the active time is under 30 minutes. Larger or untidier data sets take longer, mostly because of the time spent reviewing and correcting, which is where a partner's time is best spent anyway.
Where people stay in charge
"Agentic" can suggest software making decisions that nobody has checked. For a finance migration that would be a poor design, so the process is built around people approving each outcome.
The agents propose and flag, and the partner decides. Duplicates, missing fields, formatting problems and mapping gaps are returned to the partner and the client as a list. Fixing them sits with the people who know the business, in the source data, before the migration is re-run. Production is only written to once someone has reviewed the sandbox and approved it.
The sandbox also helps with timing. The client's current system keeps running while the review takes place, so go-live can be planned around month-end: the close finishes in the old system and the next period opens in Business Central.
How it differs from import tools
Business Central already has ways of bringing data in, including configuration packages and Microsoft's own cloud migration route for Dynamics GP. Those tools load data that someone has already prepared. Agentic onboarding covers the preparation as well, working out what the data means, what is wrong with it and how the new environment should be set up to receive it.
After go-live
The same approach carries into support. On the Qwyk platform, tickets raised from inside Business Central or from the client portal are worked by an agent, with a confidence score attached to each resolution. Anything below the threshold goes to a person for review. A ticket that turns out to be a customisation request converts into a change request, which the partner scopes, prices and takes to the client for approval.
What it means for partners
The benefit depends on where the partner is starting from. An MSP with no Business Central team can move a client who has outgrown Xero without referring them to another firm. An accounting practice that spotted the problem in the management accounts can lead the move itself and keep the relationship. For a Business Central consultancy, the hours that used to go on data preparation move to configuration, process design and the industry-specific work clients value most.
Partners also choose how involved they want to be on each client. They can run the onboarding themselves through the partner portal, hand the client a guided wizard to complete, or have Qwyk run it on their behalf. The full platform walkthrough covers how delivery is structured. Different clients can use different modes, and the partner keeps the client relationship in every case.
Which clients it suits
Agentic onboarding works best for businesses on Xero, Sage or QuickBooks that need a finance-first Business Central environment. That includes finance-only implementations, professional services firms, businesses carrying stock, retailers and not-for-profit organisations with dimension-based reporting. The onboarding produces a standard Business Central tenant, so manufacturing, service management or project accounting can be layered on afterwards in the normal way.
It is less suited to large manufacturing environments with complex integrations, or to projects that need significant customisation in place before go-live. In those cases the finance foundation can still be automated, with the specialist work built on top of it.
Common questions
More on how the partner model works in the Qwyk FAQs.
Does agentic onboarding mean AI runs the migration unsupervised? No. Agents extract, map, clean and configure, and flag anything they are unsure of. A person reviews the result in a sandbox and approves it before anything is written to production.
How long does an agentic onboarding take? A basic onboarding from a supported source system takes under 30 minutes of active time. Overall timing depends on data volume and how much review the client wants before go-live.
Which systems can it migrate from? In the UK, Xero, Sage (cloud and on-premise), QuickBooks, Microsoft Dynamics GP, and CSV or Excel files.
Does the client see Qwyk? Only if the partner wants them to. Onboarding and support can run under the partner's brand, so the client deals with the partner throughout.
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 and Dynamics GP into Microsoft Dynamics 365 Business Central. Partners choose how involved they want to be, and they always keep the client relationship.
Watch the full platform walkthrough, read the partner FAQs, or book a call with the team.