FROM BPO BOOM TO LEGACY-SHORING

How the Philippines Can Turn the World’s Oldest Software into a New High-Value BPO Opportunity—and Prepare for the AI Economy

By Karl M. Garcia

For more than two decades, the Philippines built one of the world’s most successful business-process outsourcing industries.

It began with a relatively simple proposition:

English-speaking workforce + competitive costs + telecommunications + global demand = exportable services.

That formula transformed the Philippine economy.

BPO created millions of jobs, generated foreign exchange, supported the construction of enormous office districts, stimulated telecommunications and transport infrastructure, accelerated the growth of Cebu, Clark and other regional centers, and created a pathway for millions of Filipinos into the formal economy.

But technology is changing the nature of the opportunity.

Artificial intelligence is increasingly capable of performing routine digital work. Customer service, data processing, basic documentation, standardized back-office operations and portions of technical support can increasingly be automated or augmented.

This does not mean the Philippine BPO industry is about to disappear.

It means its next phase must be different.

And one of the most immediate opportunities may come not from the newest technology, but from some of the oldest.

THE LEGACY SOFTWARE OPPORTUNITY

The world’s economy runs on enormous quantities of software written decades ago.

Banks still operate mainframes.

Insurance companies still depend on decades-old claims and actuarial systems.

Governments maintain legacy databases and applications supporting taxation, benefits and public administration.

Airlines operate highly specialized transaction-processing systems.

Healthcare organizations retain specialized legacy platforms.

Telecommunications companies operate systems accumulated through successive technological generations.

Much of this software is old precisely because it is important.

These systems contain decades of accumulated business logic. They process financial transactions, calculate insurance payments, maintain customer records, manage inventories and execute regulatory requirements.

Replacing them is not equivalent to replacing an ordinary desktop application.

A company may technically be capable of rewriting an old system.

The business question is whether it should.

The cost can be enormous.

The operational risk can be greater.

And the consequences of introducing an error into a critical financial, healthcare, government or aviation system can be severe.

Consequently, modernization often does not mean immediate replacement.

Companies frequently choose a more pragmatic approach:

maintain the existing system + document it + secure it + integrate it with modern technology + gradually modernize components.

That creates a long-lived market for legacy expertise.

This may be one of the Philippines’ most underappreciated opportunities in the next generation of IT-BPM.

THE BUSINESS LOGIC OF NOT REPLACING SOFTWARE

There is a misconception that old technology survives because companies are technologically backward.

Often, the opposite is true.

A mature enterprise system can be extremely sophisticated.

It may have been modified thousands of times over several decades.

Its code may embody business rules that were developed long before today’s engineers joined the company.

Some of those rules may not exist anywhere except inside the software itself.

The organization may therefore have a system that is ugly, old and difficult to understand—but extraordinarily valuable.

The question becomes:

Why risk replacing something that works?

This is particularly true when the software supports mission-critical operations.

A bank does not want to discover after a migration that an obscure piece of business logic governing a particular transaction was accidentally eliminated.

An insurance company does not want a software conversion to change the calculation of a legally required benefit.

A government agency cannot simply shut down a critical benefits or tax-processing system for years while a replacement is developed.

The result is a peculiar technological reality:

the older and more deeply embedded a critical system becomes, the more expensive and risky its replacement can become.

That creates demand for maintenance.

And maintenance can last for decades.

IBM AND ACCENTURE ALREADY SHOW THE MARKET EXISTS

This is important.

The opportunity is not hypothetical.

Major global technology-services companies—including IBM and Accenture—already provide services around mainframes, legacy modernization, application maintenance and enterprise technology.

That fact changes the Philippine proposition.

The country does not have to convince the world that legacy IT is a legitimate business.

The market already exists.

The opportunity is to become a larger and more sophisticated delivery center within it.

Global technology companies need reliable pools of engineers who can maintain existing systems while newer teams build modern architectures around them.

This creates a potentially durable outsourcing model:

US client → global technology provider → Philippine legacy engineering team.

Instead of exporting only call-center labor, the Philippines can export technical continuity.

The client is not simply buying programmers.

It is buying the assurance that critical systems will continue to operate.

THE LEGACY WORKFORCE PROBLEM

The most important scarcity may not be software itself.

It may be people.

Many legacy systems were created by engineers who are now approaching retirement.

COBOL is the most visible example, but the problem is broader.

The legacy ecosystem includes:

  • COBOL
  • PL/I
  • Assembly
  • JCL
  • CICS
  • DB2
  • IMS
  • MUMPS/M
  • TPF
  • FORTRAN
  • Visual Basic 6
  • Delphi
  • FoxPro
  • proprietary databases
  • customized enterprise applications
  • decades-old middleware

The challenge is therefore not simply learning an old programming language.

It is transferring institutional knowledge.

A young engineer can learn COBOL syntax.

Learning why a particular program exists, what systems depend upon it, which regulatory requirement produced it and what might break if it is changed is much harder.

The scarce commodity is increasingly:

context.

That is precisely where a well-developed Philippine technology workforce could become valuable.

FROM CHEAP PROGRAMMERS TO LEGACY ENGINEERS

The Philippine strategy should not be to become the world’s low-cost warehouse of COBOL programmers.

That would reproduce the old labor-arbitrage model.

The opportunity is to build a more sophisticated workforce capable of combining:

legacy programming + business knowledge + cybersecurity + testing + AI + modern integration.

The ideal engineer understands both the old and the new.

They can read COBOL.

They understand JCL and mainframe operations.

They know databases.

They understand APIs and cloud architecture.

They can use AI to analyze millions of lines of code.

And, critically, they can determine whether the AI’s recommendation is safe.

This is a much higher-value capability.

AI AS A TOOL FOR LEGACY SYSTEMS

Ironically, artificial intelligence may make legacy technology easier to maintain rather than immediately eliminate it.

Generative AI can assist engineers in:

  • analyzing old code
  • identifying dependencies
  • generating documentation
  • translating code
  • producing test cases
  • explaining unfamiliar programs
  • identifying potential vulnerabilities
  • mapping relationships between applications
  • preparing modernization plans

But AI does not automatically understand the consequences of changing a production system.

Consider a decades-old insurance application.

An AI system might identify a section of code that appears redundant.

But perhaps that section implements a regulatory requirement affecting a small class of policies.

Removing it could produce incorrect payments.

The human engineer therefore remains essential.

The emerging workflow is:

Legacy Code → AI Analysis → Human Judgment → Testing → Controlled Change → Production

This creates a new category of worker.

Call them Judgment Architects.

Their value is not simply writing code.

Their value is knowing when not to change code.

LEGACY-SHORING

This suggests a distinct evolution of Philippine BPO:

Offshoring → IT-BPM → Legacy-Shoring → AI-Augmented Capability

Legacy-shoring would specialize in keeping critical legacy environments operational while helping clients modernize them safely.

A Philippine team could provide:

application maintenance

mainframe operations

production support

batch processing

incident management

code documentation

reverse engineering

automated testing

database maintenance

security monitoring

legacy-to-modern integration

API development

data migration

modernization support

The product being exported is therefore no longer simply labor.

It is continuity, knowledge and technical capability.

BEYOND COBOL

Banking provides the most visible example, but the opportunity extends far beyond it.

Healthcare may require expertise in MUMPS/M and specialized databases.

Airlines use specialized reservation and transaction-processing environments.

Insurance companies maintain complex claims and policy systems.

Government agencies operate decades-old applications.

Manufacturing companies maintain customized production and inventory systems.

Telecommunications companies possess layers of software accumulated over generations.

Mid-sized American companies may be particularly interesting because they often possess highly customized applications without the enormous internal technology organizations of the largest corporations.

The Philippine opportunity should therefore be to build vertical specialization.

Instead of simply training “legacy programmers,” training could produce:

mainframe banking specialists

insurance systems specialists

healthcare legacy specialists

aviation systems specialists

government systems specialists

industrial legacy specialists

The more domain knowledge an engineer accumulates, the harder that capability becomes to commoditize.

THE PHILIPPINE ADVANTAGE

The Philippines already possesses many of the foundations required.

It has:

a large IT-BPM workforce

experience serving Western enterprises

strong English-language capability

24/7 operating models

established global technology companies

major technology centers

enterprise-service management experience

a large base of universities and technical institutions

The next step is specialization.

Instead of continuously expanding the number of workers performing standardized tasks, the industry can increase the value generated per worker.

That is the fundamental transition:

from labor arbitrage to capability arbitrage.

THE SECOND THESIS: AI WILL CHANGE BPO

Legacy systems provide an immediate opportunity.

AI provides the longer-term strategic question.

The AI revolution is still a continuing process.

It would therefore be premature to declare that AI has already eliminated the traditional BPO model.

It has not.

But the direction is clear.

AI allows companies to produce more output with fewer people in some categories of work.

That means a Philippine operation that once required 1,000 workers might eventually require 700, 500 or fewer for the same volume of routine transactions.

Those jobs may not return to the United States.

They may simply disappear through automation.

This is why AI is different from conventional offshoring.

Offshoring changed where work was performed.

AI can change whether a human needs to perform the task at all.

That is a much deeper transformation.

FROM BPO TO AI-ASSISTED BPO

But the response should not be to abandon BPO.

It should be to make each worker more productive.

A customer-service employee equipped with AI can potentially handle more complex cases.

An analyst can process more information.

A programmer can understand legacy code faster.

A finance specialist can analyze more transactions.

A healthcare information worker can process more records.

A technical-support engineer can diagnose problems faster.

The future therefore may not be:

humans OR AI.

It may be:

humans + AI.

This is particularly relevant to legacy systems.

AI becomes the force multiplier.

The human becomes the accountable decision-maker.

THE DISAPPEARING APPRENTICESHIP

There is, however, a deeper risk.

Traditional BPO created an enormous apprenticeship system.

A Filipino worker could enter the economy through a relatively routine job and gradually move upward:

customer service → senior agent → quality assurance → workforce management → team leadership → specialized operations → management.

That first job mattered.

It was a bridge into the professional economy.

If AI automates too much entry-level work, that bridge can weaken.

This is one of the most important questions raised by AI:

Where will the next generation acquire experience?

The answer cannot simply be “teach everyone AI.”

The country must create new apprenticeship pathways in:

technical operations

software

engineering

healthcare

analytics

cybersecurity

manufacturing

logistics

AI-assisted professional services

Legacy technology itself can become part of that apprenticeship system.

A young engineer can learn how large enterprises actually work by maintaining systems that process real transactions.

THE LEGACY MARKET CAN BECOME A BRIDGE TO THE AI MARKET

This is where the two theses converge.

Legacy systems are not necessarily the opposite of technological modernization.

They can be a training ground for it.

A Philippine engineer who learns to understand a large COBOL application can subsequently learn:

API integration → cloud architecture → data engineering → AI-assisted modernization.

The engineer moves from maintaining yesterday’s system to helping build tomorrow’s system.

This creates a career ladder:

Legacy Programmer → Legacy Systems Engineer → Integration Engineer → Modernization Specialist → AI-Assisted Architect

That is far more valuable than simply preserving an aging workforce.

FROM CALL CENTERS TO CAPABILITY CENTERS

The Philippine IT-BPM industry should therefore gradually transform its proposition.

The old proposition was:

“We can do the work more cheaply.”

The new proposition should become:

“We can solve the problem.”

That means moving from:

scripts → judgment

transactions → analysis

labor → capability

cost savings → business continuity

routine support → specialized expertise

BPO centers → capability centers

Legacy systems are particularly suitable for this transformation because they combine technology with business knowledge.

The engineer must understand not merely the programming language but the enterprise behind the program.

THE BIGGER DEVELOPMENT QUESTION

This brings the discussion back to the larger Philippine economy.

BPO has been enormously successful.

But no country should expect one sector to carry an ever-increasing share of employment, foreign exchange and urban development.

The answer is not to shrink BPO.

It is to diversify while increasing its sophistication.

The Philippines needs multiple productivity engines:

manufacturing + agriculture + BPO + technology + healthcare + education + logistics + tourism + MICE + maritime industries + energy + creative industries.

BPO should remain a pillar.

But BPO dependence should decline even as BPO capability increases.

That distinction is critical.

FROM SERVICES TO A CAPABILITY ECONOMY

The next Philippine development model should not be defined simply by whether an activity is manufacturing or services.

The more important question is:

How much productive capability does the country retain and develop?

A sophisticated manufacturing operation requires engineers, software, logistics, finance and data.

A sophisticated BPO operation increasingly requires technology, analytics, cybersecurity and domain expertise.

An AI industry requires electricity, data centers, telecommunications, engineering and specialized human capital.

The boundaries are collapsing.

The factory and the service center are becoming parts of the same technological ecosystem.

AI WILL ALSO CREATE A PHYSICAL ECONOMY

There is an important paradox.

AI may reduce demand for some digital workers while increasing demand for physical infrastructure.

AI requires:

electricity + data centers + cooling + fiber + telecommunications + land + construction + engineering.

The BPO economy monetized human density.

The AI economy increasingly monetizes computational density.

That creates new opportunities—but also new constraints.

The Philippines cannot become a serious AI economy simply by purchasing GPUs.

It needs reliable power.

It needs telecommunications.

It needs water and cooling infrastructure.

It needs appropriate land-use planning.

It needs data centers.

It needs semiconductor and electronics ecosystems.

It needs engineers.

It needs research institutions.

AI policy is therefore also:

energy policy + industrial policy + infrastructure policy + education policy.

WHY MANUFACTURING STILL MATTERS

The rise of AI does not eliminate the need for industrialization.

It makes industrial capability more important.

Manufacturing develops:

engineering

technical skills

quality systems

supply chains

industrial management

export capability

process discipline

technological learning

The Philippines should therefore pursue manufacturing where it can build durable capabilities:

electronics + food processing + medical devices + automotive components + machinery + shipbuilding + renewable-energy equipment + chemicals + advanced logistics.

The objective should not be to recreate the labor-intensive factories of the twentieth century.

It should be to build the technologically sophisticated industrial ecosystems of the twenty-first.

THE REAL ESTATE CONSEQUENCE

The BPO boom also created a real-estate model:

more workers → more seats → more offices → more buildings.

AI weakens that relationship.

But it does not necessarily make existing business districts obsolete.

It changes what they should become.

Future districts should combine:

offices + universities + healthcare + hotels + MICE + retail + residential + logistics + research + technology infrastructure.

A district dependent almost entirely on conventional BPO employment is vulnerable.

A district combining technology, education, healthcare, manufacturing, tourism and professional services is resilient.

The future building is therefore not merely an office.

The future district is an economic platform.

THE PROVINCIAL OPPORTUNITY

This strengthens the case for a more polycentric Philippines.

Cebu, Clark, Iloilo, Davao, Bacolod and other regional centers can develop complementary economic ecosystems.

One city might specialize in:

technology + BPO + education.

Another:

manufacturing + logistics.

Another:

healthcare + education.

Another:

tourism + MICE.

Another:

maritime industries + logistics.

The objective is not for every Philippine city to become another Metro Manila.

It is to create a national network of complementary economic centers.

THE STRATEGIC OBJECTIVE

The Philippines therefore faces two different time horizons.

The immediate opportunity:

Legacy technology.

The world already has millions of lines of critical legacy code.

Companies already pay IBM, Accenture and other technology-service providers to maintain, modernize and integrate these systems.

The Philippines can capture a larger share of that existing market by developing specialized engineering teams.

The emerging opportunity:

AI-augmented services.

As AI continues to evolve, Philippine companies must move beyond routine labor toward workers who use AI to perform higher-value tasks.

The two are not contradictory.

They are sequential and complementary.

Legacy systems can provide today’s opportunity.

AI can become tomorrow’s productivity multiplier.

FROM LABOR ARBITRAGE TO CAPABILITY ARBITRAGE

This is ultimately the central transformation.

The Philippines’ historic advantage was that Filipinos could perform internationally tradable services at competitive cost.

The next advantage must be that Filipinos can provide specialized knowledge that companies increasingly struggle to maintain domestically.

That includes:

legacy systems engineering

cybersecurity

AI implementation

software development

financial analytics

healthcare information systems

engineering services

industrial technology

research

specialized customer experience

technical operations

The country should increasingly export not just labor, but expertise.

CONCLUSION: KEEP THE OLD RUNNING WHILE BUILDING THE NEW

The Philippines does not need to choose between BPO and AI.

Nor does it need to choose between services and manufacturing.

The more immediate task is to recognize where the market already exists.

The global economy contains an enormous installed base of legacy software.

It cannot all be replaced.

It should not all be replaced.

And many of the people who understand it are approaching retirement.

That creates a durable opportunity.

The Philippines already possesses much of the infrastructure needed to participate: an established IT-BPM industry, global technology companies, experienced enterprise-service workers, English-language capability and 24/7 operating capacity.

The country should build on that foundation.

It should develop legacy-shoring as a specialized Philippine capability—maintaining critical systems, documenting them, securing them, integrating them with modern platforms and helping clients modernize them safely.

Companies such as IBM and Accenture demonstrate that this is already a real global business.

The Philippine opportunity is to become an increasingly important delivery center within that ecosystem.

At the same time, the country must prepare for the next transition.

AI will continue changing the economics of services.

Some routine BPO jobs will disappear.

Others will become AI-assisted.

New technical and professional roles will emerge.

The challenge is to ensure that Filipino workers move upward faster than automation moves into their existing tasks.

That requires education, reskilling, apprenticeships and stronger connections between universities, industry and government.

And it requires something broader than an AI strategy.

It requires a national capability strategy.

The Philippines should continue using BPO as a foundation—but not as a permanent endpoint.

It should use today’s legacy opportunity to build tomorrow’s technical workforce.

It should use AI to make that workforce more productive.

It should simultaneously rebuild industrial capability, strengthen infrastructure, develop regional economic centers and expand exports of technology and expertise.

The development path is therefore not:

Agriculture → Manufacturing → Services → AI.

It is increasingly:

Agriculture + Manufacturing + Services + Technology + AI → Higher Productivity and Capability.

The ultimate objective is not to preserve every job.

It is to increase the productive capacity of the Filipino worker.

The BPO revolution proved that Filipinos could work for the world without leaving the Philippines.

The legacy-software opportunity can prove that Filipino engineers can keep some of the world’s most critical digital infrastructure running.

And the AI revolution can take the next step:

Filipinos should increasingly be the people who understand, manage, improve and eventually transform the systems on which the global economy depends.

The Philippines should not merely be the place where the world sends work.

It should become the place where the world sends difficult problems.

Comments
4 Responses to “FROM BPO BOOM TO LEGACY-SHORING”
  1. Joey Nguyen's avatar Joey Nguyen says:

    I’m not sure if this article is based on our earlier discussion on archaic programming languages and legacy systems, but I think the article’s premise and conclusion is the wrong take. Perhaps a misunderstanding of the core points I laid out previously.

    In order to do something it takes effort. That is the main reason why legacy apps based on archaic programming languages and legacy systems like mainframes are not upgraded, mostly because it “still works.” Changing things would introduce massive, unacceptable risk to the organization. Risk costs money. A lot of money. If the risk ends up blowing up the capability to conduct business, heads will roll, executives will resign, the organization will face economic repercussions and possible organizational destruction if it gets bad enough. No competent manager thus would sign off on stuff like this unless they absolutely had no other choice.

    The market for programmers versed in archaic languages and technicians knowledgeable in maintaining legacy systems is also shrinking at a steady rate that I expect would only accelerate in the near future when the legacy hardware that runs the apps built with archaic programming languages reach the end of the hardware’s useful life.

    Organizations are well aware of all this. That’s why they continue using the legacy platforms and apps while in parallel building the replacement one more modern platforms. That’s what happened during the so-called Y2K Problem. The Y2K “Bug” wasn’t even a bug because the limitation was absolutely known in the 1950s when 2-digit year encoding started being used (due to memory limitations). Something purposefully implemented is not a bug. Before the popularization of “Y2K,” it was known as Century Date Change (CDC) since the 1950s and no one freaked out about it — it was a known and acknowledged limitation that might become a risk 50 years into the future. There were already numerous US and EU task forces dedicated to a coordinated industry response by the early-to-mid 1990s. The largest industry coordination effort was launched until Bill Clinton. No media organization wrote about it except the niche Computerworld in one article in 1993. I still have that old magazine in a banker’s box somewhere. The general public wasn’t even aware that there was a “problem” until Newsweek published the article entitled “The Day the World Shuts Down” in late 1997. I have that old magazine as well. Mass hysteria hit by 1999 with predictions that the world was going to literally end as we knew it. It was the basis of the Heaven’s Gate UFO religion’s mass suicide in 1997. Yet at the turn of the second hand at Midnight, January 1st 2000, everything was fine. Because every major organization had already switched to 4-, 6-, 8-digit year encoding years prior. The government task forces were mostly for smaller businesses that did not have the technical capability or budgets to start earlier. It is true that the early Indian IT industry had a lot of outsourced work in Y2K mitigation. It was mostly low-level, tedious work that will now be replaced by Generative AI which is already capable of doing such tedious work.

    So my question is, given that effort and time is limited, why should the Philippines dedicate a lot of time learning, training, and putting eggs into a rapidly shrinking basket? I think there are many more productive areas to pursue than this.

    • Karl Garcia's avatar Karl Garcia says:

      I tried it my way Joey but that did not mean I did not take to heart your suggestions just keep it coming. Some times I am like an old dog who can’t be taught any trick. But not that older than you so still can learn new tricks.

      • Joey Nguyen's avatar Joey Nguyen says:

        No worries Karl. What I said is not meant as a criticism but as a nudge in perhaps more productive areas. My belief is that while a nation can walk and chew gum at the same time thus do more than one thing at once, as they say time is the most precious commodity and effort should reflect that. To that end, while highly technical jobs should not be discarded as there is still a (small) middle class that needs those jobs, the greater effect would be to find ways to uplift the great majority of DEs which are 90% (~93% by some estimates). There are just not enough high end jobs to go around in the world. But potentially, there are a lot of good salaried industrial jobs that require much less educational and technical training suitable for DEs at their current level. Btw, India’s IT outsourcing sector could have not flourished if there wasn’t already a growing industrial base under it.

  2. JoeAm's avatar JoeAm says:

    The AI evolution is more dramatic than anything since Osborn made computers and I migrated our bank’s market research from paper to machine, quadrupling output and accelerating my climb up the corporate ladder. There will be lots of threads in the AI fabric, which is being knitted with billion dollar investments. Legacy code will be absorbed like trees into a swollen Nepal river, still there, but not where they used to be. The BPO industry is run by professionals who will solve their training issues because they have to. A year ago we were weeping about the likely demise of the BPO industry. Today we admire its transformative resilience. The Philippines has the critical mass to manage the transformation, I would imagine. Computers should have put people out of work but did not. They upped profitability and created the need for new skills. Which, lo and behold, appeared. My bank is still there, I would note, sold to the British, then the Japanese, then the French, and now, Canadians. The market research team is into AI, I’d imagine, and it would not surprise me if the bank’s call center, which I formed last century, is now in Cebu.

Leave a comment