SEATTLE — In the high-stakes theater of commercial aviation, mergers are notoriously difficult choreographies. While business executives often focus on fleet optimization, route networks, and regulatory approvals, the true crucible of any airline acquisition lies hidden deep within the server racks and software suites that keep the operation moving.
When Alaska Airlines finalized its $1.9 billion acquisition of Hawaiian Airlines in September 2024, it inherited not just a fleet of aircraft and a proud island heritage, but a massive technological challenge: merging two disparate, mission-critical Passenger Service Systems (PSS) into a single, unified operating platform.
For Charu Jain, Alaska Airlines’ Chief Information Officer and Senior Vice President of Merchandising and Innovation, this undertaking was a career-defining moment. An aviation industry veteran with over three decades of technology leadership under her belt, Jain is no stranger to the turbulence of digital integration. By her own count, she has navigated four major airline merger IT projects throughout her career. Yet, leading the comprehensive overhaul of Alaska and Hawaiian’s core reservation and ticketing architecture stands out as her most complex and satisfying achievement to date.
"This is one of the biggest milestones in any merger work done between airlines," Jain says, speaking from the carrier’s corporate headquarters in Seattle just two months after the final cutover.
The successful transition, completed in April following an intense 18-month development and deployment cycle, marks a watershed moment in airline technology. By migrating millions of bookings and aligning two nearly 200-year combined corporate histories onto a single software platform—engineered by travel technology titan Sabre—Alaska Airlines has charted a new blueprint for how legacy carriers can merge without alienating their passengers or overwhelming their workforce.
Executive Overview: The Architecture of an Aviation Merger
To understand the magnitude of Alaska Airlines’ achievement, one must first grasp the sheer ubiquity of a Passenger Service System. In modern commercial aviation, a PSS is the central nervous system of an airline. It is an all-encompassing software suite that records and manages every facet of a passenger’s journey.
From the moment a traveler searches for a fare, books a ticket, and selects a seat, to the seconds they check their bags at a kiosk, pass through security, board the aircraft, and select an in-flight meal, the PSS is orchestrating the experience behind the scenes.
"A PSS touches almost every function of an airline from employees to guests," Jain explains.
When Alaska and Hawaiian joined forces, each airline operated on its own distinct, entrenched PSS. Maintaining two separate systems indefinitely was financially untenable and operationally counterproductive. Furthermore, it would have created a fractured experience for travelers attempting to book multi-leg journeys spanning both carriers.
The mandate was clear: two brands, one system. However, achieving this unification required solving an unprecedented industry puzzle. The leadership teams at both airlines made a foundational commitment early in the process: despite sharing a unified backend infrastructure, Alaska and Hawaiian would fiercely retain their distinct, historically rich consumer brands.
This decision set the stage for a technological feat that had never been attempted before at this scale: building the operational and digital capabilities necessary to run two distinct, market-facing airline brands on a single underlying platform.
Detailed Chronology: The 18-Month Road to Unification
The timeline to transition both airlines onto a shared PSS was aggressively compressed, spanning roughly 18 months from the initial inkling of the deal to the final, flawless cutover in April.
Phase 1: Strategy and the "Selling Cutover"
Historically, airline IT mergers have relied on massive, high-stress data migrations. These legacy approaches typically involve freezing reservation systems over a weekend and attempting to shift millions of historical records, active bookings, and frequent flyer profiles from one database to another in a matter of hours. The risks of data corruption, lost bookings, and cascading operational delays during such wholesale migrations are legendary in the tech industry.
Jain and her engineering teams opted for a far more sophisticated, risk-optimized approach: the "selling cutover."
Beginning in October, roughly six months before the official system-wide transition date, Alaska implemented a phased deployment strategy. All new ticket sales for both airlines were funneled directly into the new Sabre-backed PSS platform. Because the average booking curve in the commercial airline industry sits right around six months, this tactical move allowed the legacy systems to naturally "drain" of active bookings over time.
"There was no migration of millions of records and bookings," Jain notes. By letting natural booking cycles empty the old databases while routing all future sales into the new platform, Alaska bypassed the perilous midnight data-dump of traditional mergers. "This meant when our customers checked in on the first day [of the PSS], it was as if the booking had been made on the native system."
Phase 2: Dress Rehearsals and Mock Flights
Even with a risk-optimized booking strategy, executing a cutover on this scale in a live operational environment leaves zero room for error. An airline cannot afford a system crash when thousands of flights are airborne.
To pressure-test the infrastructure, Alaska’s IT and operations teams executed a series of exhaustive live simulations in the months leading up to the final cutover. These were not mere desktop exercises; they were full-scale operational dress rehearsals conducted at major airports, designed to test the system across both domestic and international scenarios—particularly crucial as Alaska prepared to launch several new non-stop services to Europe.
During these simulations, real volunteers acted as passengers, arriving at airport terminals, interacting with check-in kiosks, dropping off luggage, clearing security checkpoints, and boarding aircraft. The trials deliberately incorporated edge cases and complex travel scenarios:
- Passengers traveling with household pets.
- Wheelchair-dependent travelers requiring special assistance.
- Baggage collection and transfer logistics.
- Onboard hospitality management, stopping just short of serving actual hot meals.
In total, Alaska conducted five comprehensive mock rehearsals. The iterative process allowed engineers to catch microscopic bugs, interface latency issues, and UI friction points before they could affect paying customers.
"The fifth one was when everything worked without any medium or high issues, and gave us the confidence we were ready," Jain recalls.
Concurrently, the airline established dedicated command centers in strategic hubs, including Seattle and Honolulu, empowering cross-functional teams to monitor system health and resolve unforeseen anomalies in real time on cutover day.
Supporting Context & Metrics: Navigating Turbulence and Unifying the Digital Front End
No major digital transformation occurs in a vacuum, and Alaska’s journey was no exception. In the months leading up to the PSS completion, the broader corporate entity faced external headwinds, including sizeable IT outages that briefly grounded flights and impacted tens of thousands of passengers. While these incidents drew public scrutiny, Jain confirms they were isolated infrastructure events that did not compromise the PSS integration roadmap or deter the dedicated engineering teams.
Furthermore, the technological overhaul extended far beyond back-end ticket inventories and airport kiosks. It fundamentally transformed the customer-facing digital experience.
Following the successful PSS go-live, Alaska retired the separate, legacy mobile applications belonging to Alaska and Hawaiian. In their place, the company launched a newly redesigned, unified mobile app. The application was engineered with a dynamic user interface that adapts to the traveler’s preferred brand identity.
Whether a customer habitually flies Alaska or identifies more closely with the island hospitality of Hawaiian, the app delivers a personalized experience reflecting their preferred airline, complete with integrated mileage plans, seamless booking management, and intuitive navigation.
"It’s a much more seamless experience now that there’s no confusion knowing which app to go on, or why they have two booking numbers," Jain explains. The feedback from frontline employees—gate agents, flight attendants, and customer service representatives who now rely on a streamlined, unified internal toolset—has been equally positive.
Official Statements and Industry Implications
The successful execution of this merger’s technology integration has sent ripples of validation across the global aviation sector. Industry observers have frequently cited airline IT mergers as financial black holes prone to schedule disruptions, lost luggage, and burned-out employees. Alaska Airlines has proven that meticulous planning, phased deployment architectures, and a relentless focus on collaboration can turn a potential operational disaster into a masterclass in change management.
At the heart of this success was cross-departmental alignment. A Passenger Service System does not live solely within the IT department; it is the connective tissue linking the commercial divisions—pricing, merchandising, loyalty programs—with the operational frontline—pilots, flight attendants, dispatchers, and baggage handlers.
"This was about people coming together from two companies to make this one big thing happen," Jain emphasizes.
When Alaska initiated its selling cutover strategy in the fall, the company simultaneously launched a massive internal training campaign. Thousands of employees across disparate geographies and corporate cultures were trained on the new system interface. This dual-track approach—simultaneously draining legacy ticket inventory and upskilling the workforce—ensured that when the transition date arrived, staff members were fluent in the new technology.
Future Outlook: Ready for Global Expansion and Peak Travel Seasons
Timing the final PSS transition for April was a deliberate strategic choice. By completing the cutover ahead of the high-demand summer travel season, Alaska Airlines ensured that its newly fortified technical infrastructure would be tested under peak passenger loads, rather than playing catch-up during the industry’s busiest months.
With the technological heavy lifting behind them, Alaska Airlines and Hawaiian Airlines are now positioned to capture the operational synergies envisioned when the merger was first announced. The unified PSS platform provides a flexible, scalable foundation for future growth, enabling the combined carrier to manage code-shares, alliance partnerships, and international route expansions with unprecedented agility.
As airlines worldwide grapple with legacy debt, fragmented software architectures, and rising passenger expectations for digital-first experiences, Alaska Airlines’ playbook offers a compelling lesson. Through visionary leadership, rigorous risk management, and an unwavering commitment to operational readiness, Charu Jain and her team have proven that blending two corporate histories into a single digital future is not only possible—it can be executed to perfection.