ERP and HCM, move by move.
ERP and HCM moves touch payroll and the general ledger, so nobody gets a second try at cut-over weekend. S/4HANA, Workday and Oracle moves, planned around period close and pay runs.
Dynamics AX 2012 to Dynamics 365 Finance & Operations
Told without the client's name or anything that could identify them.
A distributor's finance and operations team still ran Dynamics AX 2012 R3, which stopped getting Microsoft fixes in January 2023, so tax and e-invoicing changes were being patched in-house. Most customizations were overlayered changes to standard objects, and integrations ran through AIF services and file drops on Windows Server and SQL Server versions security wanted gone. We ran the upgrade analysis report and the Lifecycle Services code upgrade tool first, then froze AX 2012 code and moved overlayered X++ to extensions. After data clean-up and rehearsed data upgrades in development and sandbox, a mock cut-over was timed against the downtime limit before go-live on Dynamics 365 finance and operations apps.
what the client got- Microsoft ships tax and regulatory updates againThe business runs on Dynamics 365 finance and operations apps, on Microsoft's service update cadence. Regulatory changes come from Microsoft now. Nobody writes in-house patches for them.
- Customizations are extensions in source controlOverlayered X++ now lives as extensions in source control. Service updates go on without anyone reworking standard objects by hand.
- Integrations run on data entitiesThe AIF services are gone. In their place are data entities, OData and the Data Management Framework, with Dataverse linked through dual-write or virtual entities wherever a process called for it.
All 4 in erp and hcm
Read any of them and you get the story, the before-and-after architecture, the plan phase by phase and the results.
Dynamics AX 2012 to Dynamics 365 Finance & Operations
We take AX 2012 R2 or R3 systems to Dynamics 365 finance and operations apps, and the code, data, attachments and integrations come across with them.
read the case studyOracle E-Business Suite to Fusion Cloud ERP
Leaving Oracle E-Business Suite 12.2 for Fusion Cloud ERP, deciding which customizations survive and planning conversion, integrations and quarterly updates.
read the case studyPeopleSoft HCM to Workday migration
Moving PeopleSoft HCM to Workday with effective-dated history, payroll, integrations and the identity feed rebuilt and tested.
read the case studySAP ECC to S/4HANA before 2027
Getting from SAP ECC 6.0 to S/4HANA ahead of the 2027 end of mainstream maintenance, by conversion, new build or selective data transition.
read the case studyRisks that keep coming up
One risk from each of these moves, and the case study that shows how we handled it when it hit.
-
Blocked features
Virtual companies and data partitions stop the upgrade path. If the analyzer finds them, the plan becomes a reimplementation with data migration, and that's better known early.
-
Recreating EBS in the cloud
Rebuilding every customization as an extension brings the old patching pain back. Each one needs a business owner who confirms it's still needed.
-
History scope creep
Converting every effective-dated row makes each load slower and harder to reconcile. Agree early what converts and what goes to an archive people can still query.
-
Business partner conversion failures
Bad or duplicated customer and vendor records stop the conversion. Data cleanup has to start months before the first mock run.
Platforms and services across these moves
Ordered by how often they appear in this area's case studies.
01Can Cohash support us after go-live?
Yes. We take on service update testing, extension development, integration support and Lifecycle Services administration, with onsite, nearshore or offshore engineers.
02We run Oracle EBS. How do you migrate from EBS to Fusion Cloud?
Start with the customization inventory, because it sets the size of everything after it. Then settle the ledger design, run mock conversions through FBDI and reconcile each one, and rebuild interfaces on REST APIs or Oracle Integration. Go live by ledger or business unit, and archive EBS history so auditors can still query it.
03We've signed with Workday. What part of the program would Cohash take on?
Usually data conversion, integrations, the identity feed, reporting moves and PeopleSoft decommissioning, working beside the team configuring Workday. We can also staff Workday integration developers and data analysts on contract or contract-to-hire.
04Do you also replace SAP Identity Management?
Yes. SAP IdM's maintenance ends in 2027 too, so moving provisioning to Microsoft Entra ID Governance or SailPoint goes in the same plan.
More case studies by area
The same approach, applied to other parts of the estate.
53a6fb5d - 01Book a 30-minute working sessionsenior engineer
- 02Talk to an engineer about your setupreply within 24 hours
- 03See how similar projects wentcase studies
Facing one of these moves?
Tell us what you're on now and where you need to be. We'll come back with how we'd run the move.
- The platform and the version you're on
- Where you need to get to, and by when
- What's custom: rules, plugins, integrations
- Any audit finding or deadline driving it