This morning, Olin Corporation and Huntsman Corporation announced they’re merging to form OlinHuntsman; a $12.5 billion integrated North American chemicals company. The press release is polished, the strategic rationale is sound, and the synergy number is front and center: more than $400 million in total cost synergies and integration benefits, with over $300 million of that expected to be realized within 24 months of close. chemxplore.com
The financial analysts will spend today debating chlorine optionality and feedstock conversion economics. That’s their job.
Mine is to ask the question nobody in that 8 a.m. investor call addressed: who’s actually going to deliver the $300 million, and do they know what they’ve just been handed?
The Clock Starts Later Than You Think And It’s Still Brutal
The transaction is expected to close in the first half of 2027. That means the 24-month synergy clock doesn’t start ticking until mid-2027, with the bulk of $300M due by roughly mid-2029. That sounds like plenty of time until you map what actually has to happen inside those 24 months.
Despite the huge amount of work to create them, chemical company mergers don’t generate cost synergies from spreadsheets. They generate them from consolidated manufacturing networks, rationalized supply chains, unified procurement, reduced headcount through operational overlap, and, critically, IT systems that can actually see the combined business as one entity. None of that happens until the data, the applications, and the infrastructure are integrated. And in this deal, that integration starts from a complicated baseline on both sides.
Two Companies, Two Transformations, One Deadline
What the press release doesn’t cover is the operational reality sitting underneath both companies right now. Let’s take a look at what we know.
Huntsman entered this merger mid-migration to SAP S/4HANA across a global footprint spanning more than 70 facilities in 30 countries. Publicly documented master data fragmentation (inconsistent data management processes across sites, misaligned material and vendor data) prompted them to bring in a master data managed service specifically to stabilize the foundation before S/4HANA could go live. That work is ongoing.
Olin has been on its own path: active AI deployment in chlor-alkali production for energy optimization, a material master data standardization program across its global manufacturing operations, and a push to digitalize paper-based compliance and environmental records. A different ERP trajectory, a different data maturity profile, a different set of in-flight programs.
Now combine them.
You don’t have one company with a clean system of record. You have two companies, both mid-transformation, with different application stacks, different data architectures, different levels of OT connectivity, different IT governance models, and a board-level promise to deliver $300 million in documented savings within two years of close.
I’ve spent a significant amount of my career leading large-scale technology programs for global chemical companies that were products of successive mergers. Every time, without exception, the synergy number got set without asking IT what it would actually take. The IT organization finds out what it means when the ink is dry. The gap between what integration costs and what was budgeted for it is where mergers quietly bleed.
The Three Problems That Will Define Whether This Number Gets Hit
1. The ERP Decision
Someone’s SAP instance survives. Someone’s doesn’t. This is the single highest-stakes IT decision in the integration, and in a “merger of equals,” there’s no natural default. Huntsman is mid-S/4HANA migration. Does OlinHuntsman accelerate that migration and bring Olin onto the same platform? Or does Olin’s current environment become the foundation? The answer determines the integration timeline, the consulting spend, and the data migration scope. Every month this decision takes is a month the synergy clock is running.
2. The Master Data Problem- Doubled
Both companies had active master data programs before they merged. Now you have two partially-standardized data estates that need to become one. Material masters, vendor masters, customer masters, asset hierarchies; all across 100+ facilities, in multiple geographies, and across two distinct business cultures. Master data is the unglamorous work that nobody puts in the press release and everybody underestimates. It is also the work that every other integration dependency sits on top of. You cannot consolidate procurement, rationalize manufacturing, or generate reliable combined financials until the data foundation is right.
3. The OT Layer
Olin operates some of the most automation-intensive, safety-critical OT environments in the chemical industry. Chlor-alkali production runs continuous electrochemical processes where a DCS hiccup has real consequences. Huntsman operates polyurethane and advanced materials plants across 30 countries with highly variable OT maturity. Merging OT environments; historian systems, plant networks, distributed control systems, and safety instrumented systems across those geographies and process types is a massive undertaking that produces zero line items in the synergy model and absorbs enormous IT and engineering bandwidth. It will happen anyway, because a unified OT layer is required for the operational integration that drives the actual savings.
Watch the Chief Integration Officer
One detail buried in the announcement: Olin’s Todd Slater has been named Chief Integration Officer. chemxplore.com Smart move. But here’s the constraint nobody mentioned in the release. Until this deal clears regulatory review and formally closes, Olin and Huntsman are still legal competitors. Under the Hart‑Scott‑Rodino Act, gun‑jumping rules mean the two companies can’t coordinate operations, can’t share systems or sensitive data, and can’t make any joint IT or architecture decisions.
So the real integration work (ERP platform selection, master data harmonization, architecture choices, and broader IT consolidation) can’t actually start until Day 1. Don’t mistake that for a planning miss. It’s the law.
And it means the 24‑month synergy clock doesn’t start during the press conference. It starts the moment the ink is dry, with zero warm‑up laps.
The CIO role is the one to watch next. Whoever gets that seat inherits both transformation programs, both mid-flight ERP decisions, and a 24-month deadline with a nine-figure number attached to it.
The Bottom Line
The Olin-Huntsman merger makes strong strategic sense, and $400 million in identified synergies is a credible number over the right time horizon, and with the right integration execution. The 24-month target for $300M of it is where I’d push back, not on the arithmetic, but on the operational reality of what two mid-transformation chemical companies have to accomplish before that number materializes.
The deal was announced this morning, but the real work can’t start until the merger closes in Q1 2027. When it does, IT becomes the center of gravity. If nobody’s talking to them yet, they will be.
