// About
We only do one thing.
Chivora specialises exclusively in Microsoft Dynamics 365 data migration — moving critical business data from SAP, Oracle, Sage, NAV, BPCS, IFS and Access Dimensions into D365 F&O and CE. Not configuration. Not general IT. Not implementation project management. Data migration, and nothing else.
// The Founder
Sunday Ukwungwu — Founder & Director
I started Chivora because data migration kept being the thing that went wrong.
Across 7 years working on ERP transformation programmes — including implementations moving organisations from Microsoft Dynamics NAV and SAP into Dynamics 365 — I watched the same failure play out repeatedly. The functional design would be solid. The configuration would be done. The training would be delivered. And then, in the final weeks before go-live, the data would surface problems that should have been found in month two.
The reason was always the same: nobody had owned data migration as a discipline. It had been distributed across people with other priorities, no dedicated tooling, and no structured methodology. It was treated as something that would "just happen" alongside everything else — and it didn't.
I have been part of 6 migration projects across that period, working across General Ledger, Accounts Receivable, Accounts Payable, Inventory, Fixed Assets, Customers, and Vendors — and across source systems including SAP, Microsoft Dynamics NAV, SAGE, BPCS, IFS, and Access Dimensions. I know where the problems hide in each of those systems because I have found them, documented them, and fixed them under real delivery pressure.
Chivora exists to provide what those programmes were missing: a single, accountable specialist who owns data migration from discovery through to post-go-live sign-off, with a methodology built from real delivery experience rather than generic best practice.
"We only do data migration. Not configuration, not project management, not general IT. That focus is not a limitation — it is the reason we're better at it."
Sunday Ukwungwu, Founder & Director — Chivora
Background & Experience
- 7+ years working on ERP transformation and data migration programmes
- 6 D365 migration projects delivered across F&O and CE platforms
- Source systems: Microsoft Dynamics NAV, SAP (ECC), SAGE, BPCS, IFS, Access Dimensions
- Domains: GL, AR, AP, Inventory, Fixed Assets, Customers, Vendors — full coverage
- Tools: DIXF / Data Management Framework, KingswaySoft, SQL Server, Excel / Power Query, Power BI
How I Work
Chivora takes on a small number of engagements at a time — by design. Every client gets my direct involvement from the first discovery conversation through to post-go-live sign-off. There are no account managers, no junior handoffs, and no situations where the person who scoped the work is not the person delivering it.
I work remotely as standard, with on-site attendance for key workshops, mock migration reviews, and cutover. I am based in the UK and available for programmes across the UK and, where the engagement is primarily remote, internationally.
// Positioning
What we are. What we're not.
What we are
- A specialist data migration team, and nothing else
- Owners of the data workstream, from discovery to sign-off
- Built to work alongside your Microsoft Partner or SI, not replace them
- Obsessive about reconciliation — every balance agrees before we sign off
- Direct about pricing, timelines and what's actually achievable
What we're not
- An ERP or IT consultancy
- A general Dynamics 365 implementation partner
- A configuration or process re-engineering service
- A body-shop for generic data engineering work
- A team that guesses at go-live dates to win the work
// Why This Matters
Most D365 projects treat data migration as an afterthought.
On most implementations, data migration is handed to a functional consultant to run alongside their configuration work — squeezed into whatever time is left between workshops. It usually surfaces as a problem for the first time at the first mock migration, when balances don't reconcile and nobody on the programme owns the fix.
We exist because that pattern is predictable and avoidable. Treating data migration as its own workstream, with a dedicated team and a repeatable methodology, is the difference between a go-live that slips and one that doesn't.
Tooling