If your enterprise reporting and automation still depends on spreadsheets, manual extracts, and half-retired systems… you don’t really have a data strategy. You have a risk strategy.
That’s the realization one international telecommunications company came to—and it kicked off two major transformation initiatives that I had the opportunity to support using the Dynamics ecosystem.
Different regions. Different challenges. Same underlying problem: legacy complexity slowing the business down.
First challenge: Getting from Dynamics to Oracle without breaking the business
One region was preparing to move from Dynamics GP and CRM to Oracle. On paper, that sounds straightforward. In reality, it meant supporting a heavily customized GP environment where the original development team was long gone.
Add in global stakeholders, a seven hour time difference, and zero tolerance for downtime.
My role was to preserve the existing organizational structure while designing and delivering all the data extracts required by the Oracle implementation team. The key decision here was to avoid brittle, one-off extracts and instead deliver user-refreshable Dynamics data.
That shift mattered. Teams around the world could access what they needed, when they needed it—without waiting on someone else. The result was an eleven month transition that maintained business continuity the entire way through.
Second challenge: ERP sprawl
In another region, the problem wasn’t migration—it was fragmentation. Multiple ERP systems were in play, from Dynamics SL to QuickBooks, making support and visibility harder than it should have been.
The goal was consolidation: bring everything into Dynamics GP, simplify the landscape, and give the business time to think strategically about what came next.
I led data migration from multiple source systems, using tools like eOne SmartConnect and Popdock. Along the way, I built a custom Excel timesheet with approval workflows that posted directly into the WennSoft Job Cost module and generated a UKG upload file—meeting operational needs without compromising controls.
Ten months later, every company in that business unit was operating on a single ERP platform.
What this reinforced (again):
Modernization isn’t about chasing the newest platform or ripping everything out at once. It’s about making intentional architectural choices—grounded in governance, security, and scalability—so today’s fixes don’t become tomorrow’s constraints.
Done right, ERP work doesn’t just stabilize the business. It creates space to automate, integrate, and actually move forward.
If you’re dealing with legacy ERP complexity, global data challenges, or trying to modernize without disrupting operations, I’m always interested in swapping notes.
