Practical ERP migration lessons from real controllership work involving SAP S/4HANA, Dynamics AX, Infor M3, JD Edwards, NetSuite and HFM.
Professional examples in this article refer to Luis Alberto Rivera Tur's employment and project experience. They are not presented as Rivera Enterprise Solutions client testimonials or anonymous client case studies.
The finance side of an ERP migration begins before cutover. My experience with SAP S/4HANA at Honeywell and Dynamics AX to Infor M3 at Nefab reinforced the same principle: data integrity, accounting ownership and reconciliation have to be designed into the migration rather than checked after the system is already live.
1. Fix the balance sheet before moving it
Migrating an unexplained balance does not make it more reliable. At Nefab, the pre-cutover work included cleaning eight GL accounts, eliminating more than $270K USD of fixed-asset exposure and certifying a $0.00 variance before migration. That work was part of the migration, not a separate accounting cleanup project.
2. Treat mapping and UAT as financial controls
During the Dynamics AX to Infor M3 transformation, the finance-control framework included eight SOPs, data mapping, validation and UAT. AI-assisted ETL and automated workflows reduced manual preparation of migration-ready asset records by 65%. The goal was not simply to move records; it was to preserve their accounting meaning and traceability.
3. Acquired entities need accounting ownership during standardization
At Honeywell, four U.S. entities within an 11-entity consolidation moved from legacy systems to SAP S/4HANA. The work included GAAP continuity, tax-code mapping, activity mapping, user acceptance and post-go-live adoption. The migration reached go-live without operational downtime for those entities, but that result depended on preparation and validation rather than the software alone.
4. Training and stabilization are part of cutover
A technically correct system can still fail if users do not understand the new process. Role-based SAP S/4HANA training, video SOPs and standardized request processes helped move the organization from implementation into normal operations. Post-go-live finance support should therefore be planned as a control activity, not an optional add-on.
5. Real companies often have more than one ERP
At NOV, intercompany work spanned entities using JD Edwards and Oracle NetSuite, with consolidation through HFM. A migration or consolidation strategy has to account for the period in which old and new platforms coexist. Reconciliation across that heterogeneous environment matters as much as the final target architecture.
The Controller's cutover test
Before calling a finance migration successful, I want clear answers to five questions: Do opening balances tie? Can material master-data changes be traced? Are tax and accounting mappings validated? Can users execute the close? Can finance reproduce the supporting evidence an auditor or manager will request? If those answers are yes, the ERP is supporting controllership rather than merely replacing software.
Next step
Need help with your finance operations?
Rivera Enterprise Solutions provides fractional controllership, finance-led ERP transformation support and US GAAP financial-control services for U.S.-based companies.
Book a Consultation