No. Qwyk is a product business, not a services business, and the model is built through partners rather than direct sales. Partners register, bring their own clients, and hold the commercial relationship. Qwyk works behind the partner: we don't contact, market to or contract with your clients.

Three partner types. MSPs and Microsoft IT companies with no Business Central capability in-house. Accounting practices with clients who need more control than their current finance system can handle. Smaller Business Central consultancies and independent consultants who want to take on more clients without adding headcount.

It adds to it. The platform automates the setup and migration stage, which is the part that consumes effort before the valuable work starts. Your consultants' time goes on the parts that need people: reviewing exceptions with the client, process design, training, and anything beyond the onboarding scope, such as manufacturing, service management, integrations or industry-specific work.

It also makes smaller deals viable. Engagements that are not worth the manual setup time today become worth taking on when the foundation is automated.

Partner-led, where you run the onboarding yourself through the partner portal. Qwyk-managed, where we run the onboarding on behalf of your client while you keep the relationship. Client self-serve, where you hand your client the guided wizard and oversee them while they complete it. You can use different modes for different clients.

Only if you want it to be. The onboarding portal can carry your logo and colour scheme, and support and delivery can be provided as a white-labelled service, so the client sees you throughout. We just need your branding pack. Partners who prefer to introduce Qwyk openly can do that instead.

No. If you already transact licences, directly with Microsoft or through a distributor, keep doing so. The licence revenue and the Microsoft relationship stay with you.

Qwyk can also supply licences with a rebate for the partner. That option is designed for partners who don't have their own licensing route, and buying direct or through a distributor will usually give you a better margin. Either way, you resell to the client.

The platform has four uses for a partner.

Winning new clients. Run a prospect's real Xero or Sage data through the wizard as part of your sales process. They see their own chart of accounts, customers, vendors and balances inside Business Central before they commit. If they proceed to a full onboarding, the demo credit comes off the production fee.

Migrating clients. Connect the source system, review in sandbox, go live. Once the source system is connected, the platform-led onboarding takes hours rather than weeks.

Scaling delivery. Run multiple onboardings simultaneously through the partner portal in any combination of delivery modes, without adding headcount.

Staying connected after go-live. Support ticketing, change request management and the knowledge base keep you embedded in the client relationship long after the migration is done.

Once the client gives Microsoft Entra admin consent, the platform provisions Business Central in the client's own tenant, creates the company, installs the Qwyk connector and loads a configured template. It then takes you step by step through company information and fiscal year, chart of accounts, bank accounts, tax rates, dimensions, payment terms, customers, vendors, items, locations and fixed assets, followed by stock, fixed asset and G/L opening balances and open AR, AP and bank items.

The template is chosen at the start of the onboarding:

Standard (Finance + Stock). General businesses carrying inventory. Customers, vendors and items, stock balances and locations, bank accounts and GL mapping, open AR and AP balances, fixed assets.

Professional Services. Service businesses with no physical stock. Customers and vendors, bank accounts and GL mapping, open AR and AP balances.

Retail. As Standard, with stock held across multiple locations.

Not in scope: historical transactions (the platform migrates opening positions, and detailed data is summarised into opening balances), payroll, integrations such as the Shopify connector, and customisations. These are available as additional consultancy.

Yes. As the data comes in, the platform builds the posting groups and maps the sub-ledger accounts, using AI to suggest the mappings. You review the result in the sandbox rather than configuring it by hand.

Yes. Each company is a separate onboarding. Companies in the same localisation are deployed into the same Business Central environment. A company in a different localisation is deployed into its own environment, subject to licensing.

Yes. As well as migrating from an existing system, the platform can set up a new Business Central company from scratch.

Yes. The onboarding produces a standard Business Central environment with a clean finance and inventory foundation. Manufacturing, warehousing, service management and project accounting can be layered on afterwards in the normal way.

Yes. The Qwyk connector installs a simplified view of Business Central, with guided tours that build on Microsoft's own. A client moving from Xero or MYOB isn't dropped into the full interface on day one.

It is where you register, manage multiple client onboardings, track pipeline and client accounts, run support ticketing, access training and the knowledge base, and submit feature requests. There is also a Business Central app for partners, so if you would rather manage your clients and tickets from inside Business Central than from the portal, you can.

The configuration templates are hosted centrally by Qwyk. Clients pull the latest template data when they connect, so setup changes and new functionality can be rolled out across the client base without touching each tenant individually.

It is built on Microsoft Azure and designed so that nobody has to sit in the back end for an onboarding to complete. Scaling is a matter of resource, not headcount.

If your client is on a system not listed here, ask us. Other regional systems are on the roadmap.

Usually, yes. The portal issues a lightweight desktop agent that you install on the machine holding the data. It extracts the data and sends it to the portal. This is how on-premise Sage is handled today, with MYOB in testing and Microsoft Dynamics GP in development. Where there is no agent yet, a file export and import route is available.

Send us sample export files from that system and we'll build the integration. The next client on the same system then goes through the standard flow rather than spreadsheets. Going from choosing a new integration to a working test typically takes around two weeks.

If an export from a supported system arrives in a different format, we can usually adapt to it within a couple of hours.

No. Everything lands in a fully audited Business Central sandbox first, while the client keeps working in their existing system. You and the client review it there. When the sandbox is signed off it is promoted to production: the setup carries across, so only the balances need refreshing at cutover.

Once the source system is connected, the platform-led onboarding can be completed in hours rather than weeks. The elapsed time to go-live depends mainly on how quickly data queries are resolved and on any training or process work around the migration. Most finance-led onboardings go live within days to a couple of weeks, rather than the three to six months a traditional Business Central implementation takes.

About an hour of running time for a typical SME data set: for example, 2,000 customers, 100 vendors and around 100 open invoices. Most of that is the AI review, which checks and cleans every record. For 2,000 customers it takes around 17 minutes.

Each stage shows an estimated time before it starts, based on the number of records, so you can step away while it runs. You can switch the AI review off, which brings the run down to around 15 minutes, but some of the mapping it does would then fall to you.

The platform is built to take as much of that burden off people as possible.

Automatic correction. An AI review checks every record and fixes common problems, such as a city in the wrong address line, a postcode in the country field, or a missing country inferred from the postcode, phone number or email. Each correction is explained rather than applied silently.

Exceptions with guidance. Anything needing judgement is raised in plain English, often with a one-click fix. Blocking errors must be resolved before submission; warnings and suggestions are advisory.

Excel round trip. Every data step can export a workbook listing each record with its errors and guidance. The client corrects it and imports it straight back, and it is re-validated on the way in.

Reconciliation. Before anything is posted, the trial balance must net to zero and open receivables and payables must agree to their control accounts.

Correcting the source data itself is the client's responsibility. The platform makes that work as light as possible.

Good fit: finance-led businesses with data in a supported source system, a single company (or a small number onboarded separately), opening balances rather than full history, and no immediate need for integrations or customisations. That includes finance-only implementations, professional services firms, retail businesses and not-for-profit organisations.

Less suitable: large manufacturing environments with complex integrations, businesses requiring significant customisation before go-live, or projects where the scope goes well beyond the finance and inventory foundation. Clients like these can still use the platform for the migration element of a larger project. If you are unsure about a specific client, ask us before running the onboarding.

Often, yes. Many not-for-profits are finance-led with simpler requirements, which suits a finance-first onboarding. Microsoft also offers not-for-profit pricing on Business Central licences, so eligible organisations can make the move without a traditional implementation budget.

The platform supports the UK and Australian Business Central localisations today, including VAT and GST set-up. New Zealand and North America are in build, due to be live in Q4 2026.

Where a Microsoft localisation exists, the work is roughly a week end to end. Where a partner or ISV localisation is needed, the timeline is driven by the commercial agreement with that provider and is closer to a month. Neither case is a six-month or twelve-month wait.

Yes, and it is the route we prefer. We embed their localisation into the template and agree a revenue share with them on every onboarding that uses it. If you have that relationship already, it accelerates the conversation considerably.

The framework was built with language packs in mind, in the same way Business Central handles them. Tell us which language you need and we will give you a straight answer on timing.

You choose. There are two options, and support is optional: clients can keep using Business Central without it.

Managed support. Qwyk provides support for the client's finance solution, delivered as a white-labelled service behind your brand.

Second-line backstop. Your team handles first-line support. Qwyk handles platform issues and bugs, breaking changes to customisations when Microsoft updates land, and escalations to Microsoft. You escalate tickets to us through the partner portal.

The client accesses their support portal either from inside Business Central or on the web.

Included: "How do I…?" questions, guidance on errors, escalation to Microsoft (we often resolve platform issues ourselves rather than wait for a Microsoft fix), and backup and platform recovery.

Not included, but available at our standard rates: formal training, customisations, and report and document layout design.

There is no hard cap on support hours. Our support agreement includes a fair usage policy.

7am to 9pm UK time, Monday to Friday. We are working on extending to round-the-clock support. For partners outside the UK, the second-line backstop works well: your team provides first-line support during local hours, and Qwyk works escalations outside them.

Tickets are worked by agents in the platform, with a confidence score attached to every resolution. Anything below the threshold is flagged for a person to review before it goes back to the client. The intent is that routine tickets resolve quickly and human attention goes to the ones that need it.

Errors and data issues are reported to Qwyk automatically through our support system. We usually know about a problem as soon as it happens, without waiting for you to raise it.

They raise it from the client portal as a change request. It comes through as a ticket, gets scoped and priced as consultancy, and is built and deployed through the platform's development pipeline. You stay in control of what is approved and what the client is told.

Yes. The partner portal has a feature request board, and it shows our roadmap, including what's coming and when it's due. Early partners have a disproportionate say in the roadmap, and that is deliberate. We would rather build against real partner demand than assumptions.

The client does. Every onboarding deploys Business Central into the client's own Microsoft tenant, so they own the environment and their data from day one.

No. After onboarding the client has a standard Business Central environment running on Microsoft's cloud. It operates independently of Qwyk, and no Qwyk subscription is needed to keep using it.

A single extension, the Qwyk Onboarding Connector. It provides the migration services used during onboarding, in-Business Central support ticketing, a role centre and dashboard, a setup assistant and financial reporting services.

It can be uninstalled at any time. All accounting data lives in Business Central's standard tables and isn't affected, and there is no licence check, so nothing stops working. Only the in-Business Central support panels and dashboard preferences are removed.

The finished Business Central environment and all its data sit in the client's own Microsoft tenant.

Qwyk holds data only for onboarding: extracted source data is staged, mapped and validated, then written into Business Central. The Qwyk platform is hosted on Microsoft Azure in the UK, with the portals served from Western Europe. Where staging and support data needs to be held in a local market, we can provide that.

Yes. The data review uses Anthropic's AI service to check and correct records. Client records such as names, addresses, contact details and account descriptions are sent to it for review. This is under commercial API terms, so client data isn't used to train AI models.

Access is granted by the client through Microsoft Entra admin consent and stays in place until the client revokes it, which they can do at any time. If Qwyk isn't providing ongoing support, we recommend revoking it at go-live, and we'll guide the client through that. All onboarding activity is audit-logged.

Non-solicitation and client ownership, confidentiality and data processing, Microsoft tenant access, data protection (UK GDPR and local privacy law), professional indemnity and cyber insurance, data location and breach notification, and termination and data extraction.

You pay for the platform with Qwyk credits rather than consultant days. A credit is a unit of prepaid value: you buy credits in advance, and each service on the platform costs a set number of them, so you know what an onboarding will cost before you start. The next question explains how credits work.

Credits are bought through partner tiers to suit different volumes, from pay-as-you-go to monthly plans with credits included. The price per credit depends on your tier. Credit prices are wholesale, so you set your own client-facing price on top and present it however suits your business.

Business Central licences are separate and can be bought through your usual route or through Qwyk. Contact us for the current partner price list.

A Qwyk credit is the prepaid unit you use to pay for everything on the platform. Think of it like a top-up balance: you hold one pool of credits and draw on it as you use services, instead of signing a separate contract or receiving a separate invoice for each one.

Some examples. A partner-led onboarding, run by your own consultants through the portal, costs 5 credits. That covers provisioning Business Central, data extraction, the AI review, reconciliation, configuration and promotion to production. A demo on a prospect's real data costs 2 credits, and those come off the onboarding cost if the client goes ahead. Qwyk-managed onboardings and ongoing support are paid from the same balance.

Why credits rather than days? A traditional implementation is priced in consultant days, so the cost moves with how long the project runs. A credit price is fixed in advance for a defined scope, and no extra credits are charged within that scope. Anything genuinely outside it, such as training, integrations or customisation, is quoted separately as consultancy, so you always know where the line is.

In the partner portal. Every transaction is recorded there, and you can view and download your invoices.

No. You are buying access to the onboarding platform and its services, a toolkit for onboarding clients onto Business Central. You remain the implementation partner, and what you charge your client for the wider project, including whether to offer it at a fixed price, is your decision entirely.

For a Qwyk-managed onboarding, Qwyk runs the onboarding to the scope of the portal with no additional credits charged within that scope. Work outside it, such as training, customisation, report and document layout design and integrations, is available as consultancy at our standard rates.

Yes to both. What you charge your client is your decision, and the portal can run under your logo and colours, so Qwyk does not need to appear in front of the client at all.

No. What you pay Qwyk is a wholesale credit price. What you charge your client above that is yours to decide. Some partners charge what they would have charged for a traditional implementation. Others charge less because the platform reduces their cost base, or package a clearly defined "essentials" implementation. Qwyk has no view on what the right retail price is for your market or your clients.

You do. You run the onboarding for your prospect in a sandbox, so they see their own data in Business Central before they commit. If they go ahead and the sandbox is promoted to production, the demo cost comes off the full onboarding fee.

Yes. If you run a product demo on real client data and the client proceeds to a full onboarding, the 2-credit demo cost comes off the production onboarding fee.

Yes. There is a full end-to-end demo video covering partner registration, adding a client and running an onboarding through to go-live, plus shorter section-by-section videos if you only want to see one part of the process.

After that we run a one-to-one partner walkthrough of around two hours: an end-to-end demo migration in your market's localisation, plus the partner portal, with time for your questions. We can then give you sandbox access to run a migration of your own data before you take it to clients.

Clients onboarded, and honest feedback while the platform is still young. We are deliberately working with a select number of partners per market at this stage so that the product is shaped by real delivery.

A short introductory call to confirm your client base is a fit, then partner registration, a one-to-one partner walkthrough and sandbox access to try your own data. Your first onboarding can be one we run for you, so you see the process before you run it yourself.