Dynamics NAV → Business Central
Microsoft’s conversion toolkit handles most of the code, and the reports come out the other side looking fine. Then month-end lands and the totals don’t agree with what NAV used to show. We rebuild the reports that matter, prove they tie out against your real numbers, and quote it at a fixed price. NAV 2017 support ends January 11, 2027.
Free, no pitch, and no call required. Email us the list and we’ll tell you which reports convert cleanly, which need hands on them, and which will quietly hand you the wrong number.
In Dynamics NAV, Business Central, and the reports teams run.
Old NAV report and new BC report, reconciled on the same data.
Quoted in writing in one business day. No hourly meter.
If a standard BC report already does it, we point you there. Free.
A NAV-to-Business-Central move is really two jobs. Microsoft’s tooling does the first one well. The second one is on you — and it’s the one that breaks month-end.
So the honest version isn’t that your reports vanish. It’s that most of them convert, a stubborn minority don’t, and almost nobody checks whether the converted ones still tie out. That last part is where month-end goes wrong, and it’s the whole reason this page exists.
Get a free report auditThe data migration goes fine. Then the reports your team runs every day turn out to be the part nobody planned for. Here’s what people actually run into:
“We upgraded to Business Central — but the reports didn’t come with it.”
The data moved. The aging, the statements, the board pack your team ran every morning didn’t — and you found out the hard way.
“It worked in NAV. In Business Central, it doesn’t.”
Reports that ran fine for years throw errors or come back empty — and there’s no Classic Report Designer in BC to fall back on.
“Our partner won’t touch the custom reports — that’s on us.”
The migration moved the data and called it done. The reports got pushed to a “phase 2” that keeps slipping.
“Nobody here remembers why half these reports were built.”
The developer who wrote them is long gone. The logic is a black box, so no one can say how to rebuild it.
“We’re back in Excel — just in case.”
Nobody fully trusts the new reports yet, so the team rebuilds the old numbers by hand every month, just to be sure.
“Everyone assumed the reports would just come across.”
Mechanically, most of them do. What nobody budgeted for is the ones the toolkit flags for manual work, and the ones that come across clean but no longer agree with NAV. That surprise usually lands at go-live.
If any of these is your month-end, the free audit is where we start: we sort out which reports actually matter, then rebuild only those.
Get a free report auditStart with the free audit. From there, rescue one report or convert the whole estate — same fixed-price, parity-proof approach.
Send us your report list (or a NAV object export). We catalog every custom report, document in plain English what each one does and the data it depends on, and triage each: rebuild in BC, replace with a standard BC report, or retire. You leave with an inventory you can actually read and a fixed-price plan — before you commit a dollar.
You have one or two reports you cannot run the business without — the aging your collections team lives in, the statement your auditors expect. We rebuild it in Business Central, reconcile it against your real numbers, and show you old-vs-new on the same data so you can trust it. Fixed price, you own it.
Doing the whole migration? We take your entire report estate, triage it so you’re not paying to rebuild reports nobody runs, then rebuild and parity-check the ones that matter. We handle the reports your migration partner treats as a footnote — without the multi-month timeline.
Send the report you can't get built. You get a written, fixed-price quote back — no call, no sales sequence, no pressure to ever get on the phone.
Rather just talk it through? Book the free 30-min call instead.
From a list of old NAV reports to reports you trust in Business Central — no surprises.
Send your report list or a NAV object export. On a free 30-minute call we walk through what you’ve got and tell you straight what carries over, what needs rebuilding, and what to retire.
Within one business day: a documented inventory and a fixed-price plan covering only the reports worth rebuilding. You see the whole scope and price before you commit.
We rebuild each report in Business Central to the agreed scope, working from read-only access or a sample export if you’d rather validate the design first.
We run the old NAV report and the new BC report on the same data and show you they match — before you sign off. One review checkpoint, one revision round.
The finished reports with plain documentation: run them, schedule them to your inbox, change them later. You own them outright. No retainer, no lock-in.
Conversion tools still need a developer to refactor and validate. Big partners bundle reports into a project where parity is a footnote. We do one thing, and prove it.
A rebuilt report is worth nothing if you can’t trust the numbers. We run the old NAV report and the new BC report on the same data and show you they tie out. No “looks right” — proof.
We’re not selling you a migration with reports as a line item. We rebuild the reports the migration leaves behind, and we’ll tell you which ones a standard BC report already covers — at no charge.
A fixed price in writing within one business day — not an hourly meter. Most report rebuilds ship in about 14 days. Heavier work (a full RDLC redesign) is scoped on its own honest timeline.
Delivered with documentation: how to run it, schedule it to your team’s inbox, and change it later. No retainer, no per-seat fee, no lock-in.
We’ve worked in Dynamics NAV and Business Central — and the reports finance and ops teams actually run — for over 14 years. We speak both sides of this move.
Most shops are told to convert all 150 reports. Usually you need a fraction of that rebuilt, some become standard BC reports, and the rest can retire. We save you the spend on the ones that don’t matter.
60-second intro
A quick look at how we turn live Business Central data into the reports your team actually needs — the same reports you’re trying to bring across from NAV.
Yes. Microsoft’s migration tooling moves your records — customers, vendors, items, G/L, open balances, and standard setup — and maps your tables and fields to Business Central. Most of your custom report code comes across too. What the tooling can’t do is tell you whether a converted report still returns the number NAV returned. That’s the part we handle.
Business Central online doesn’t run C/AL, and there’s no Classic Report Designer. Microsoft’s conversion toolkit translates most of the code automatically — roughly 70-85%, including report definitions and RDLC layouts — and flags the rest for manual work. So it’s rarely a full rebuild of everything. The audit tells you which reports convert cleanly, which need hands on them, and which need reconciling before you trust the output.
Two things. The migration tool maps your underlying table and field data into BC. Then, for each report, we map the specific fields it reads to their new home in Business Central — because a field may have moved, been renamed, or now lives in an extension. That mapping is what lets us rebuild the report so the numbers match what you saw in NAV.
Usually fewer than you’d expect. A typical NAV install accumulates a large pile of custom reports, but many are duplicates, unused, or now covered by a standard Business Central report. The audit sorts them so you rebuild only what earns its place — and we point you to the free standard-BC option wherever one exists.
It’s a fixed one-time price per report or per scope — not a retainer and not an hourly meter. We scope this as a development engagement, the way a partner would; the difference is the fixed price, the timeline, and that you own the result. The audit is free, so nobody pays to find out where they land. From there you get a fixed price in writing within one business day. The exact number depends on the report — a straight rebuild is a very different job from a full RDLC layout redesign — but you’ll always see the whole price before any work starts.
Dynamics NAV 2016 reached end of support on April 14, 2026, so it no longer receives security updates, fixes, or assisted support — you’re running unsupported now. NAV 2017 follows on January 11, 2027, and NAV 2018 on January 11, 2028. The reports are usually the slowest part of a move, so starting the report audit early takes the pressure off the rest of the migration.
No. If you just need one report rescued — before, during, or after a migration — that’s most of what we do. No retainer required. And if you’re running the whole migration with a partner, we slot in to handle just the reports.
Free either way. Email us the list, or take a 30-minute call if you’d rather talk it through. You end up knowing what carries over, what needs rebuilding, and a fixed price in writing within one business day — or, where a standard BC report already does it, we point you there at no charge.
or book a 30-minute audit call