Business Central health check and support transition

A delayed month-end close, recurring job failures or an uncertain partner handover can have several causes. A useful Business Central health check begins with the affected process, the business impact and the evidence already available. It should produce an ordered next-step list, with a named owner for each action.

Bitta Apps offers Business Central support, AL development and integration services. The initial conversation helps establish whether configuration guidance, a targeted investigation or a broader improvement project is appropriate. Bring two or three examples of the work your team cannot complete reliably, and explain what a successful outcome would look like.

We do not assign a health score from a sales conversation or promise a performance improvement before investigating the environment. Priorities depend on your actual configuration, extensions, data volumes and operating requirements.

The free BC Environment Snapshot includes one hour on a screen share with a senior Business Central consultant, followed by a written two-to-three-page environment summary within five business days. It covers version and update posture, extension inventory, integrations, data integrity signals, performance red flags, permissions, deployment discipline and support risk.

You receive five findings ranked by risk, their business impact, effort ranges and the three recommended first actions. The report is yours to use with any partner. It does not include fixes, code changes, data changes or a fixed-price migration plan. Check current Snapshot availability and the sample report.

The paid BC Health Check is a ten-business-day architecture review across configuration, extensions, integrations, performance, permissions and update risk. It includes written findings and a prioritized remediation roadmap. The published fee starts at $4,750, with larger environments quoted up to $6,500 based on tenant size, extensions and integrations. The amount is agreed in writing before work starts, and no further commitment is required. See Health Check pricing and scope.

Configuration changes, AL fixes, integration repair, data correction and ongoing support are separately agreed work. Choose the Snapshot for an initial written view of the environment and the Health Check when you need a deeper architecture assessment and remediation roadmap.

• Workflow reliability: identify the transaction, document or approval that fails, and reproduce it with representative data and permissions.
• Extension ownership: list installed apps, their publishers, source-code availability where applicable, compatibility issues and responsibility for each update.
• Integration operations: identify authentication owners, job schedules, recent failures, retries and the process for finding missing or duplicate transactions.
• Performance evidence: distinguish a slow user workflow from a background task, reporting query or external service. Microsoft documents telemetry for investigating environment activity and errors; useful analysis depends on what has been configured and retained. See Microsoft's telemetry overview.
• Update readiness: record the target version, schedule, notifications and tests for critical workflows. Microsoft describes the controls in Business Central update management.

Choose the checks that answer the business question. A narrow investigation can be more useful than a large report with no agreed action owner.

Treat a support transition as a controlled handover. Establish who administers the tenant, who supplies licenses, which providers maintain apps and who holds the operating documentation. Support services and licensing arrangements should each be understood before changing either.

Prepare an inventory of open incidents, extensions, integrations, environments, scheduled jobs and renewal obligations. Request the documentation and code access that your contracts entitle you to receive. Record unresolved items explicitly, including any dependency on the previous provider or a third-party app publisher.

Agree on a handover date, escalation contacts and responsibility during the overlap. Verify necessary access with the customer administrator, then review whether obsolete access can be removed. Keep sensitive credentials out of email and contact forms. The first working session should test an agreed workflow and the support escalation route, so the handover has observable acceptance criteria.

Business Central support covers ongoing assistance. For planned changes, explore AL development and integrations. Read the upgrade readiness checklist, or use the migration readiness guide if your current system is NAV or GP.