Business Central optimization for a system already in use

What Business Central optimization targets

There are two kinds of slow. Technical slowness is a page that takes too long to open or a posting that locks other users out. Process slowness is a task with more steps, more clicks or more people than it needs. Users often describe both in the same way.

Both cost time every day, and they need different fixes. So we keep two lists. Telemetry shows the technical items. For process items, we sit with the people who do the work and watch where they leave the system. Then we rank each list by time lost.

Measuring before changing anything

Business Central can send telemetry to Azure Application Insights. It covers long-running queries, page views with load times, report runs, job queue results and lock timeouts. With that on, the slowest actions show up as a ranked list, not a complaint. We set it up as the first step.

For a single slow action, the performance profiler in the web client records what ran and how long each part took. It breaks the time down by extension. That usually points to one subscriber, one flow field or one report dataset. You can share the recording with a developer directly.

Performance fixes that last

Typical fixes are unglamorous. A list page may show calculated fields that nobody reads. We remove them. A custom routine may loop through records one by one. We rewrite it to work in sets. We move heavy reports and the cost adjustment to the job queue overnight.

Users help too. Saved filters on large lists make daily work feel quicker. So do pages without needless FactBoxes and background posting for documents. We change one thing, compare the telemetry and keep a log. Your system owner then gets the before and after figures in writing.

Business Central optimization of everyday processes

Process work starts with the spreadsheets people keep beside the system. Each one marks a gap. It might be an allocation done by hand, a reorder list built from an export or an approval tracked in a mail folder. Most have a standard feature waiting to replace them. We list them all before we choose.

Recurring journals and allocation accounts handle repeated entries. Approval workflows and Power Automate move requests without email. Reordering policies and the planning worksheet replace the manual reorder list. We set each one up and test it with the owner. Then we retire the spreadsheet. We count each change in steps saved.

Keeping the system lean

Systems slow down as they fill up. Old job queue logs, change log entries, archived document versions and integration records pile up quietly. Business Central has built-in policies that delete such records after a period you set. It also has date compression for old ledger entries. We set these up with your approval.

We also tidy what users see. Unused extensions come out. Role centers shrink to what each role needs. New features from recent release waves go on where they replace a custom workaround. A lean system is quicker to learn and easier to support.

Business Central optimization questions

Why has our Business Central become slow?

Common causes are extensions that add work to every page or posting, lists with many calculated fields, heavy jobs running in working time and tables that have grown large. Telemetry shows which one applies to you. So the fix targets the cause and not a guess. We then repeat the measure after each change, and you see the result.

Is Business Central optimization different from a health check?

A health check inspects and reports. Optimization acts on the findings and measures the result. Many companies do them in that order. If you already know what hurts, we can skip straight to measuring that area and fixing it. Either way, you get a written record of what changed and what it achieved.

Can Business Central online performance be improved, given Microsoft runs it?

Yes. Microsoft manages the servers. Even so, most slowness comes from configuration, extensions, data volume and how people use pages. All of those are in your control. Those are the areas we work on, and the platform's telemetry shows the effect. So Business Central optimization pays off even when the cloud is not the cause.

Will optimization changes disrupt daily work?

They should not. We try changes in a sandbox copy first. Then we apply them to production in small steps outside busy periods. We move job schedules to the evening. We tell users in advance when a page layout or a process step is going to change. So your team keeps working while the system gets faster.

Do we need new licenses or add-ons to optimize?

Usually not. Most gains come from features already included, such as workflows, recurring journals and the job queue. Telemetry needs an Azure Application Insights resource. Azure bills that by data volume. We mention an add-on only when it clearly fits. And we explain the reason, so you can say yes or no with confidence.

Pages related to optimization

Optimization often begins with an inspection and continues inside a support plan. These pages cover both, along with the automation and best-practice topics that come up most during the work. Read them next if your Business Central optimization plan needs a health check first, or if you want ongoing care after the changes land. For the product detail, see Performance overview for Business Central.