← Figaf Friday

Figaf Friday: why does it help the community to automate SAP PI to CPI migrations?

A rough estimate of the effort needed to move all SAP PI/PO customers to Cloud Integration, and why automating the migration helps the community.

March 3, 2022 · 2 min read

Why does it help the community to automate SAP PI to CPI migrations? If you were to change the integration platform, the best would be to implement the solution to leverage the new platform.

For that to happen, that will require you have:

  • To really want to implement the functionality again
  • A good team that can leverage the new platform
  • The business resources to help with the new integration

Support for SAP PI/PO is set to end by 2030

SAP Process Integration/Process Orchestration is a hugely successful product by SAP with over 12,000 clients. However, support for the platform ends by 2030 per announcement by SAP themselves.

Support may be extended beyond that, but it would rely on external partners to provide it.

Watch on YouTube SAP updates roadmap for SAP PI/PO and SAP CPI

The end-of-life dates for SAP PI/PO create an urgency to move to the SAP Cloud Integration (SAP Integration Suite). Have you started sizing up the cost of your migration? If not, we have created an estimator of the migration project costs. Check it out to see how much it will cost you at this point in money and time to migrate to the Cloud Integration.

Example of the cost of a Migration

This is based on an average size customer with 200 ICOs that needs to be migrated.

A migration will take roughly 500 days. That is about 2.5 person years. If there are 12,000 migrations in 8 years then that brings an average of 1,500 migrations per year.

That means 1,500 migrations per year at 2.5 person years each, which equals 3,750 person years every year just for migration.

I don’t know how many people work with SAP Integration but I would guess in the range of 20,000 people.

An extra requirement of 20% will stress the existing developers. Moreover, add new projects and more integrations to the mix then the migration is going to propose a big challenge to the community of SAP Integration developers. And if the bulk of the migrations is handled in the last few years before the deadline, it could even require 50% of the developers.

Screenshot of the Figaf Migration Estimator
Screenshot of the excel document for the migration estimator

How to automate the migration process

In the Figaf Migration Tool, we have created a number of ways to automate the migration. You can read more about what the tool does here.

If it can save 50% on the migration, then it will save almost 2,000 person years every year and reduce the migration effort to only 10%. And sure, there will be places where it is better to redesign the process because of a number of factors.

More from Figaf Weekly

Oct 16, 2026

Put your B2B migration on a real calendar

A new calculator plots your B2B migration go-live on a real calendar. Also: wildcard ICO migration, Cloud Integration chamber of horrors and SAP TechEd.

All issues →

See this working in your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.