Dynamics ERP · BC · NAV · F&O

ERP should close the month. Not become the month.

Business Central, NAV, and Finance & Operations. Implementations that drifted, upgrades that stalled, and an operating line you would rather not staff in-house.

ODDYN

Business Central · NAV · Finance & Operations

Do not mix the products

BC is not a small F&O. NAV is not “just upgrade it.” F&O is not a Power App with a ledger.

We treat each product as what it is, then connect it cleanly to CE and Power Platform instead of inventing a third source of truth.

  • Rescue: scope that grew, a partner that left, environments that no longer match LCS or PPAC
  • An honest plan: stabilize first, then improve
  • An ERP only the original consultant understands is a risk, not an asset

Products

Three lineages. One standard.

BC

Business Central

Mid-market that outgrew Excel

Dimensions, inventory, localization, and ISVs with discipline. Bank rec should not need a hero.

NAV

NAV → Business Central

Upgrade as a controlled migration

Data, custom objects, and the processes people invented around the old forms.

F&O

Finance & Operations

When the scale is already F&O

Finance, supply chain, dual-write / virtual tables, and the surface Power Platform now expects to be on.

Rescue

Course correction

Projects already in flight

The plan the slide deck avoided: what freezes, what is rewritten, what is switched off.

Retain

Outsourced ERP line

Functional and technical on retainer

Month-end, releases, ISV updates, and the tickets that never make phase 2.

Platform

ERP + Power Platform

Extend without cloning the ledger

Flows and apps at the edge. The core is touched only when the core is the problem.

Bring the ERP as it is.

Stabilize, cut, or stop digging. hello@oddyn.com.pa

hello@oddyn.com.pa