// article
What a Business Central Environment Snapshot finds in one hour
by Mohammad Nour Itani·Aug 26, 2026·Reviewed Aug 26, 2026 by Mohammad Nour Itani
Most finance teams cannot answer three simple questions about their own ERP
Ask a controller at a mid-sized distributor which Business Central version they are running, what custom code is installed, and which outside systems write into the database overnight. Most cannot answer all three. That is not a criticism. Nobody was hired to track it, the last partner left no documentation, and the system keeps working well enough that the question never gets asked.
It stops being an academic question the moment an update breaks a posting routine, an EDI feed goes quiet for three days, or the one person who understands the customizations gives notice.
The BC Environment Snapshot is one hour on a screen share with a senior consultant, followed by a written summary within five business days. Below is what the hour covers and what it usually turns up. Every example is drawn from real delivery patterns, with the companies unnamed.
The eight things the hour covers
1. Version and update posture
Which version is running, how many release waves behind that puts you, how the update window is configured, and whether recent updates applied cleanly.
A common finding: a manufacturer two waves behind, with no update window set and a sandbox that had been refreshed once in eighteen months. Nobody had rehearsed an upgrade against current data. The regression risk was not in the platform. It sat in three customizations that had not been tested since the day they were written.
2. Extension and customization inventory
What is actually installed: AppSource apps, per-tenant extensions built for you, and leftover code from partners you no longer work with.
A common finding: a wholesale distributor with eleven installed extensions, four of them per-tenant, and two of those with no source code in anyone's possession. One had been published by a contractor years earlier and still ran on every sales order posting. Nothing was wrong with it that day. It was simply unowned, and unowned code is what turns a routine update into a two-week incident.
3. Integration map
What talks to Business Central, in which direction, by what method, and who owns each connection on the day it fails.
A common finding: EDI feeds to two big box retailers moving through a middleware account created under a former employee's login, writing sales orders in overnight with no failure alert anywhere. The team learned about problems when a buyer called. Drawing that map took twelve minutes of the hour. It changed the next quarter's priorities.
4. Data integrity signals
Open posting periods, unadjusted cost entries, stuck job queue entries, unposted document backlogs, and dimension and item reference hygiene.
A common finding: two companies in one tenant running an intercompany sync, with one document type failing quietly for eleven weeks. Each company balanced on its own. The two did not balance against each other. The controller had been reconciling the gap by hand every month and had assumed it was a timing difference.
5. Performance red flags
Long-running reports, page load complaints, job queue overlap, and heavy customizations sitting in the posting path.
A common finding: a manufacturer with four job queue entries all scheduled for 2:00 AM, two of them writing to the same tables. Month end ran nine hours and users were told to stay out of the system until it finished. The correction was scheduling, not hardware. Nobody had looked, because for years the complaint had only ever been recorded as a general report that the system is slow.
6. Permissions and access
Who holds SUPER, how permission sets are assigned, and whether the current arrangement was a decision or an accumulation.
A common finding: nineteen of twenty-six named users holding SUPER at a distributor whose auditor had asked about segregation of duties two years running. No grant was careless. Each one solved a real problem on a real day, and not one was ever taken back.
7. Deployment discipline
Whether a sandbox exists, whether it resembles production, what is tested before a change goes live, and who is able to publish.
A common finding: an external developer publishing straight to production on Friday afternoons, because the sandbox had drifted so far from production that testing in it proved nothing. That is not a failing in the developer. It is a missing environment refresh routine, and it is one of the least costly items on this list to correct.
8. Support and knowledge risk
Who understands the customizations, what is written down, and what happens to the monthly close if that person is unavailable for a month.
A common finding: one internal analyst who had built every operational report, set every dimension convention, and specified the logic inside two extensions, with none of it documented. Finance acts on this finding faster than any other, because it is the only item on the list that can resign.
What the written summary contains
Two to three pages, with your company name on it, delivered within five business days of the session:
- The top five findings ranked by risk, and no more than five.
- What each finding means for the business rather than for the code.
- An effort range for each item, never a single confident number.
- The three things we would do first, in order, with the reason each one comes before the next.
- What was not examined, and why.
- The questions the hour could not answer, which your team can.
A redacted sample report is published on the site. Read it before booking, and judge the offer on the deliverable rather than on the description of it.
What it deliberately leaves out
No code is written. Nothing is changed, published, or deployed during a Snapshot.
No fixes. Findings are described and ranked, not repaired.
No data changes. The session is read only.
No fixed-price plan. A migration number produced without a discovery phase is a guess, and that guess is where overruns start. Scoped plans with real figures belong to the paid BC Health Check, which reviews the full architecture over ten business days and ends in a prioritized remediation roadmap. Terms for both offers sit on the pricing page.
Keeping the two apart is deliberate. The Snapshot is the free diagnosis. The Health Check is the paid engagement. Letting them blur would turn the free hour into a sales call, which would make it worth less to you and to us.
The honest reason it costs nothing
A few readers will finish the report, recognize work they want done, and ask for a quote. Most will not. Both outcomes are acceptable, and the report reads the same either way. Every copy carries a closing line stating that it is yours to use with any partner, including the one you work with today. That line is what makes the offer genuinely free instead of a pitch in a document wrapper.
The arithmetic is straightforward. A Snapshot costs a few hours of senior time. A conversation that starts from a written, specific, prioritized document is a better conversation than one that starts from a brochure. That is the entire trade, and it is worth stating plainly rather than pretending there is no commercial interest at all.
Five spots before December 31
Five is the real capacity between now and year end, not a scarcity device. When the five are claimed, the offer returns in 2027.
If you run Business Central or NAV at a US distributor or manufacturer and cannot answer the three questions at the top of this article, one hour is a reasonable price to find out. The full terms are on the pricing page, and the session can be booked from the contact page.