SAP has set a single retirement date for two systems that most IT roadmaps still treat as separate projects. SAP ECC end of maintenance and SAP PI/PO (Process Integration/Process Orchestration) end of life land on the same day, the close of 2027, and PI/PO is the middleware that moves data between SAP and everything else a company runs. Most of the planning attention so far goes to the S/4HANA side of that migration, the modules finance and operations teams touch every day.
The integration layer gets less attention and more risk. It’s harder to staff than the finance and operations modules, harder to test end to end, and the one piece of the migration that breaks every other connected system if it goes wrong. For Hi-Tech and IT companies already running lean engineering teams, that combination turns into a hiring problem before it turns into a technical one.
This guide covers what the deadline actually changes, why integration specialists are the hardest roles to fill before it hits, what that staffing gap costs, and how a mix of nearshore staffing models closes it faster than a US-only search.
Mainstream maintenance for SAP ERP 6.0, the release most companies still call ECC (ERP Central Component), ends on December 31, 2027, with an optional extended maintenance window through the end of 2030 at a 2-point premium on the maintenance base. SAP’s maintenance strategy for SAP PI/PO 7.5 follows the same calendar: mainstream support until the end of 2027, extended support available through 2030, and customer-specific maintenance with no further releases after that. The alignment is deliberate. PI/PO runs on the same NetWeaver release as the ECC core, so SAP retires them together.
SAP’s recommended path off PI/PO is SAP Integration Suite, the cloud integration platform built on SAP Business Technology Platform (BTP), and SAP has built tooling to help move the work along. That tooling only semi-automates the migration, in SAP’s own description, assessing each integration scenario and sorting it into ready to migrate, needs adjustment, or needs evaluation. Every interface the tool flags still needs a developer who understands both the old PI/PO configuration and the new Integration Suite model to actually finish and test it. Gartner estimates that roughly 17,000 of the 35,000 companies still on ECC, nearly half, will still be running it when mainstream maintenance ends in 2027, and most of those same companies are carrying a PI/PO integration layer they haven’t touched yet.
The people who can close that gap are a narrower slice of SAP staff augmentation than most companies plan for: not generalist SAP consultants, but developers who know PI/PO’s message mapping and adapters well enough to rebuild them in Integration Suite. That role is exactly what every problem below comes back to.
A senior engineer capable of rebuilding PI/PO interfaces in Integration Suite isn’t a junior hire, and US pay reflects that. The median annual wage for a software developer in the United States is $135,980, per the Bureau of Labor Statistics’ May 2025 wage data, and integration specialists with BTP or Cloud Integration (CPI) experience typically sit above that median, not at it. Add payroll taxes, benefits, and the recruiting cost of finding someone who actually knows legacy PI/PO adapters, and a full-time hire for a project with a fixed end date gets expensive in a hurry.
That math gets harder for a company whose engineering budget already has competing claims on it. A migration with a hard date attached pulls funding away from product work that has no deadline at all, and building a full-time team around a project that’s over in eighteen months rarely pencils out on its own, a pattern that shows up across the broader tech staffing trends for 2026 as companies rethink how much permanent headcount a short, deadline-driven project actually needs.
Even once the budget is there, finding the person is its own problem. Ashby’s benchmark data, drawn from 54 million applications across 93,000 jobs, puts the median time to fill a senior technical role at 71 days, 37% longer than a junior search, and integration and middleware roles are rarely junior. Add a notice period at the candidate’s current job and a few weeks of ramp-up before they’re productive on your specific PI/PO landscape, and a search that starts today can run past the point where it still helps you hit a 2027 cutover.
SAP isn’t going to move its date. A search timeline that runs 60 to 90 days isn’t a scheduling inconvenience at that point, it’s the actual constraint on how many of these migrations get finished on time.
Compare a 60-to-90-day US search against nearshore staffing timelines with our free calculator.
Pulling your own engineers off product work to rebuild integration interfaces sounds free, right up until the roadmap they were supposed to be shipping slips instead. ASUG’s 2026 Pulse of the SAP Customer survey found that budget pressure is now the top challenge SAP customers report, cited by 61% of members, up seven points from the year before. A separate read on that same research, reported by ERP Leaders, found that systems integrators and implementation partners already absorb 37% of the typical migration budget, the single largest line item, before a company adds its own staffing costs on top.
Internal teams weren’t built with spare capacity for a once-in-a-decade platform retirement. Every engineer reassigned to PI/PO migration work is an engineer not writing the product code your roadmap already promised, and that tradeoff shows up in slipped releases long before anyone notices the integration layer is behind schedule. It’s the same pattern Fast Dolphin has seen on SAP and Oracle projects where temporary staffing keeps delivery on schedule without pulling internal engineers off their own roadmap.
SAP's December 2027 Deadline
Two systems, one clock
SAP ECC and SAP PI/PO share the same maintenance calendar, so the integration layer runs out of road exactly when the core ERP does.
Sources: SAP Support maintenance strategy · SAP Community maintenance alignment for SAP NetWeaver 7.5
Offshore staffing solves a cost problem, but a PI/PO to Integration Suite cutover is a timing problem first. Interface testing, cutover rehearsals, and the go-live window all need the integration developer and the internal systems owner working the same hours and catching the same errors in real time, not handing off a ticket across a nine-to-twelve-hour gap and waiting for the next overlap window to find out if it worked. A single overnight delay on a cutover weekend can be the difference between a clean migration and a rollback.
Async handoffs work fine for backlog items that can wait a day. They work badly for anything tied to a date SAP has already fixed, and PI/PO retirement is exactly that kind of work. Nearshore engineering teams based in Latin America work inside US business hours, which closes that gap without asking the client to run a parallel night shift on their own side, the same reason systems integrators scale nearshore teams without adding overhead instead of building a second internal team from scratch.
The talent squeeze isn’t limited to people who still remember classic PI/PO. S4 Contracts’ review of UK contract market data found that pay rates for SAP PI and integration contractors rose 22.6% over six months, the fastest growth of any SAP specialty it tracked, and that BTP, Cloud Integration, and Integration Suite postings take roughly twice as long to fill as more established SAP roles. Part of that is a market-wide effect: Gartner’s analysis, as reported in Boomi’s recap of the 2025 Magic Quadrant, put the integration platform as a service market above $9 billion in 2024 and forecast it to exceed $17 billion by 2028, which means every company adopting cloud integration tools is drawing from the same thin pool of people who know them.
A short comparison makes the gap concrete:
Classic PI/PO vs. SAP Integration Suite
Same ecosystem, different skill set
The 2027 deadline doesn't just retire a product. It shifts demand from one set of integration skills to another.
Classic PI/PO developer
Shrinking demandCore skill
Java-based mapping, adapters, ccBPM
Deployment model
On-premises middleware
SAP Integration Suite developer
Growing demandCore skill
Cloud Integration flows, API Management, BTP extensions
Deployment model
Cloud-native on SAP Business Technology Platform
Sources: S4 Contracts SAP module demand data · Gartner iPaaS market analysis via Boomi
Companies hiring for the full range, people who can read the old system and build in the new one, are drawing from the smallest slice of an already thin market, and that’s before counting the AI-adjacent roles the same companies are staffing for at the same time. The hiring pattern around SAP’s AI roadmap and Joule-ready roles looks almost identical: a short list of specific, modern skills and a long list of companies competing for them.
Fast Dolphin is a nearshore IT and Engineering staffing company that gives US and Canadian Hi-Tech and IT companies access to tens of thousands of vetted professionals across Latin America, so a scarce PI/PO or Integration Suite profile doesn’t mean starting a search from zero. The first candidate is delivered in 24 to 48 hours, cost runs significantly lower than US-based hiring (Fast Dolphin’s own analysis of its placements found a weighted average of 54% savings against the true cost of a US hire), and consultants work in your time zone, with bilingual talent available when a project calls for it.
That combination answers each problem above directly. It brings down the cost of carrying integration headcount through a project with a fixed end date, it replaces a 60-to-90-day US search with a first candidate inside 48 hours, it adds capacity without pulling your own engineers off the product roadmap, and it does all of that without the time zone and async handoffs that make offshore staffing a poor fit for a cutover this sensitive.
Contratação Temporária is built for exactly this kind of project-sized work: add a PI/PO specialist or a full migration team for as long as the cutover takes, and it can start under Contract-to-Hire when you want a built-in path to keeping the right person on permanently. Contratação Direta fits the architect who owns SAP Integration Suite after the migration is done, and every Direct Hire placement includes a 90-day replacement guarantee: if the professional leaves or is let go for documented poor performance within the first 90 days, Fast Dolphin replaces them at no cost, or refunds the fee on a pro rata basis if it can’t.
Share your SAP ECC and PI/PO migration timeline in our contact form, and we’ll get back to you with next steps.
It means SAP stops releasing standard support packages, legal change updates, and problem fixes for ECC once 2027 ends, unless you pay for extended maintenance through 2030 at a 2-point premium. Nothing stops working on January 1, 2028, but every day after that you’re running on a system SAP is actively winding down.
Yes. SAP PI/PO 7.5 runs on the same NetWeaver release as SAP ERP 6.0, so SAP aligned PI/PO’s maintenance calendar with ECC’s. Both end mainstream maintenance at the close of 2027 and both share the same optional extended maintenance window through 2030.
Partly. SAP describes its migration tooling as something that semi-automates the move, assessing each PI/PO interface and sorting it into ready to migrate, needs adjustment, or needs evaluation. A developer still has to finish, test, and sign off on every interface the tool flags, which is the step most companies underestimate.
Industry benchmark data puts the median time to fill a senior technical role at around 71 days, and that’s before onboarding and ramp-up on your specific SAP landscape. For a project with a fixed 2027 deadline, that search timeline alone can eat a meaningful share of the runway you have left.
Offshore staffing can work for backlog development, but a cutover depends on real-time collaboration between your integration developer and your internal systems owner during testing and go-live. A large time zone gap turns that into a slower, async process at exactly the point in the project where speed matters most.
It depends on how long the role lasts. Project-sized work, like rebuilding a set of PI/PO interfaces or running the cutover itself, fits Temporary Staffing, where named people join your team for the length of the project. A permanent SAP Integration Suite architect who owns the platform afterward is better hired through Direct Hire.
Yes, with the specifics set in your own contract and access controls. Fast Dolphin’s consultants work inside your systems under the same access rules you’d give any other team member, and you decide what each person can reach based on your own security and compliance requirements.