Where Fusion ERP projects actually slip
Configuration is rarely the reason. The slips come from data, integrations and reporting scope that were not treated as first-class work.
By AMTEX Consulting · Editorial
Ask a programme director where the last Fusion ERP implementation slipped and the answer is almost never 'the configuration was hard'. It is data conversion that took four mocks instead of two, integrations discovered in UAT, or reports the business assumed would exist.
Data conversion is engineering, not admin
FBDI templates look like spreadsheets, so conversion gets staffed like a spreadsheet task. It is a pipeline: extract, cleanse, transform, load, reconcile, repeat. Build it as one, run it weekly from the start of build, and publish a reconciliation report finance signs off each cycle.
Inventory every interface before design ends
Interfaces hide in scripts, scheduled jobs and people's laptops. A structured inventory in discovery, with owner, frequency, volume and failure mode for each, is the cheapest risk reduction available in the whole programme.
The reporting catalogue is scope
List every report the business uses today. Decide for each whether it dies, maps to a seeded report, becomes an OTBI analysis, or needs BI Publisher. Assign it a build and test cycle. The alternative is a reporting backlog that lands in hypercare and never leaves.
- fusion-erp
- programme-management
- data-conversion