Skip to Content
Personal Insights
Author's profile photo Thorsten Düvelmeyer

Start your SAP PO to SAP Integration Suite migration now!


SAP Process Orchestration (PO) supports custom process applications and integration scenarios for a lot of SAP customers. It evolved over many years to a very stable and feature rich integration solution. Because of changing business requirements and your IT strategy, it could be a good idea to check, if SAP Integration Suite supports your processes and integration requirements better?

If you consider moving to SAP Integration Suite, you might ask yourself what is the best time to start a project for your migration?

Benefits of SAP Integration Suite

SAP outlines some benefits why customers should migrate and transform with SAP BTP  / SAP Integration Suite:

  • SAP Integration Suite provides the flexibility and independence you need by delivering technology to move assets to the cloud, integrate the IT landscape, and configure and extend SAP and third-party applications.
  • Achieve seamless business processes: Integrate processes and data across diverse application landscapes and business networks with comprehensive integration capabilities.
    Accelerate business outcomes: Quickly integrate and connect any application or business partner with thousands of pre-built integrations using a proven methodology based on 50 years of SAP best practices.
  • Modernize integration: Enable self-service integration at scale with simpler tools, built-in AI, and modern integration capabilities. Deploy to any cloud with trust and security fully managed by SAP.

SAP Assessment and Migration Tool

It was possible to move to SAP Integration Suite in a – manual way – by migration SAP PI /PO IFlows and ICos to Integration Flows in CPI (former name of Cloud Integration) since years. By January 23 SAP released their SAP Assessment and Migration Tool to support migration projects. So is a migration from SAP PO to SAP Integration Suite now a “click of a button”? I think that is with the current version of the solution not possible, because some functionality is missing and a migration of the complete content will not be possible and sometime does not make sense. But you get a good overview on your integration content in SAP Process Orchestration with a rough estimation of your effort to move to SAP Integration Suite.

The first step will be to connect you SA PO system via Cloud Connector in the Migration Assessment tool like described in SAP Help.

After that you can start with extracting data from your system


Extract Data in SAP Assessment Tool

When the extraction job is finished, you can create a based on the data via:

Scenario Evaluation

This will show you a nice dashboard, but also the opportunity to download the results via Excel or PDF.




Download Results

The next steps will be to evaluate the results and estimation and perhaps identify some scenarios, where you will have some quick wins or easy to migrate ones. If there are special requirements from your side, you can check the rules in the settings section.

If you identified some flows, you would like to migrate, you are able to directly start with the Migration Tool. That is not designed as central tool with a central dashboard to push content to Cloud Integration but more as pulling flows from SAP PO to specific packages in Cloud Integration. So first of all, create a new package and the click on “Migrate”:


Migrate in Cloud Integration

After selecting a flow and some more clicks, you migrated your first flow from SAP PO to Cloud Integration 🙂


first migrated flow

For sure, you can do the migration manually, but at the end a tool does it in a reproducible und save way. There are some restrictions today, so that you need to do some adjustments manually. To make it more and more sures, I would suggest doing at least some testing and send feedback to SAP in case of issues or missing features. Some generic ideas and information’s can we found here.

Please keep in mind, that there is no status update for migrated flows today. So consider to mark them in PO in an appropriate way.

SAP Integration Suite vs. Cloud Integration

Integration became more complex in comparison that was there, when SAP PO was designed. So I think a migration from SAP PO to Cloud Integration is not the whole story: There are much more holistic capabilities in SAP Integration Suite and it makes sense to perhaps rethink the implemented scenarios and to migrate from SAP PO to SAP Integration Suite, e.g. to:

  • add a central API proxy as entry point for more security or a better developer experience
  • use Event Mesh for high volume interface or to implement loose coupling
  • implement a CAP service for some central logic, that could be reused.

Unit, Integration and Regression Testing

In migration projects the implementation takes time, but typically testing is a a big block where you need integration and business experts. Because business experts have a lot do what delivers more values than doing tests manually, it could be very a booster for your project to automate testing as much as possible:

  • Unit test manually via simulation and test tool
  • Integration testing via INT4 Shield with PO and Cloud Integration in one step
  • Use integration tests for regressions tests also after migration project

If you don’t have solutions in place for that, consider to use the 12 month free license of the Figaf tool or the INT4 Shield.

Migration Approaches

When thinking a bit on migration options or strategies, I find a analogy to S/4 projects very interesting:

  • Brownfield conversion: More or less try to copy/migrate as much as possible content from SAP PO to Cloud Integration without changing the logic of implemented integrations. This could be a good option in case of many standard integrations or if are not able to change thing e.g. because of keeping migration costs low.
  • Selective: Copy the mass of interface in an intelligent way and implement changes, where it brings quick wins e.g. by using more flexible functionality compared to SAP PO. One idea could be to implement a API security and load balancing layer or to document your interfaces via API Hub Business Portal (OpenAPI)
  • Greenfield: Start with ISA-M process to design your Integration landscape of the future. After that, build some interfaces based on the new guidelines, learn about the new capabilities and how to handle them in live production. With these experiences build packages of interfaces and migrate them in waves to Integration. Perhaps you can use the best of PO and Integration for a while to have a smooth migration?

Migration project steps / phases

Perhaps we can reuse SAP Activate for our migration projects?

  • Discover: The outcome of the Discover phase is to lean about the new SAP Integration Suite capabilities an do define your Integration approach. Also, a basic documentation of your landscape should be ready afterwards.
  • Prepare: The outcome of the SAP Prepare phase is to setup the Assessment tool (see above) and to run the assessment on your SAP PO system(s). You should analyse the results in detail regarding effort and what is possible to migration automatically. During the Prepare phase, SAP or enterprise architects will build a business case for migration, which outlines the benefits and reasons for migrating from SAP PO to Integration Suite.
  • Explore: A change impact analysis will be completed to understand how SAP Integration Suite will benefit the business and integration team. This outcome of the Explore phase is to enable a smooth transition to the new system.
  • Realize: SAP functional consultants and business users will work together to ensure the objects in Integration Suite are delivered within the timeline and to a high standard. Once all the deliverables are satisfied, a cutover plan is made to move the configurations.
  • Deploy: The outcome of the Deploy phase is to migrate the interfaces to SAP Integration Suite so that customers and partners can benefit from the new capabilities while continuing to receive support in case of problems or concerns.
  • Run: The main task for consultants during the Run phase is to keep up to date with the latest innovation and technologies in SAP as part of the product’s “Continued Learning” philosophy. Once the transformed integration landscape is up and running, the focus shifts to continuous improvement and risk management.

Quo Vadis – Start your SAP PO to SAP Integration Suite Migration now?

So finally, what to do? Start now? Migrate everything in one step? Or do it step by step? What is the best way to do it and what is the best target architecture?

I think it makes sense nearly for every customer to START NOW, because:

  • we now have the tools form SAP in GA
  • there are quick wins by SAP Integration Suite nearly for every scenario
  • it is a complex project, that takes time and will be become more difficult, when starting at the end of SAP PO lifetime

For sure, there are still missing capabilities in the Migration- and Assessment tool and also in SAP Integration Suite (compared to SAP PO). That’s we I would suggest starting now, to migrate what makes sense in you landscape and to use the power of SAP PO and SAP Integration perhaps for a certain time until needed features are available.

What are your ideas on migration from SAP PO to SAP Integration Suite? Do you already have first experiences? Would it be a good idea to build a community book with tips and tips or FAQs?

Also check out the SAP documentation of the new tools for more detail.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Techedge-PI Consultor
      Techedge-PI Consultor


      Thanks for the blog Thorsten.

      In my experience, lots of clients use SAP PO for G2G integration scenarios, with high message volumes, and also large messages, including file scenarios.

      In the blog you did not touched this subject and I think it´s really important if you are thinking in a migration.

      Is the Integration cell (On Prem version of Integration Suite) ready to be used? It was in beta version as far as I know, most of us have not been able to test it yet.

      Also, I could not find any info on how will the On prem runtime count the messages, license stuff. This is a very important subject for the clients when migrating,

      I think that migrating PO systems, G2G scenarios, under the actual Integration Suite license version, is simply not worth it, the cost of running those scenarios in the cloud, could be really huge (counting messages and checking sizes) .... latency could also be an issue with this architecture... I think it waiting a little bit, might be worth it, until we can deploy this scenarios in an hybrid architecture.

      I hope that the license of the the integration cell, does not charge clients based on number and size of messages, because they are using their own resources for that runtime. Once that is clear, I think it would be the proper time to migrate the whole PO to Integration Suite, having a hybrid architecture already set within the company for the I.Suite.

      For all these reasons, I would not jump onto a migration right now, at least for G2G scenarios, maybe for other integration scenarios subject to domains like C2C, G2C, C2G.

      Best regards,

      Author's profile photo Thorsten Düvelmeyer
      Thorsten Düvelmeyer
      Blog Post Author


      yes, you are right: high message volumes for system in a private data center is a challenge and Integration Cell is still on the way and currrently in BETA.

      My idea would be to start with scenarios, where it makes sense to move to Integration Suite now and to learn about the capabilities.

      Perhaps some On Premise systems will be replaced by SaaS serivces or move to IaaS, so that it could make sense to wait a bit and not to move with the complete workload today.


      Best Regards,

      Author's profile photo Bryan Pierce
      Bryan Pierce


      This was a great blog. It summarizes all the same concerns we, too, are experiencing with our efforts to move to Integration Suite. This really helps put together exactly the mindset of concerns, questions, and curiosities about the whole migration approach for us. Seeing your thoughts on how you view those same constraints and the options for solutions is helpful to reinforce our own decision making process. As we look at the options of migration approaches (brownfield, selective, and greenfield) I'm very curious to if you've used the ISA-M approach at all or know of others that have? I like the idea of slowing down the migration to spend the time with ISA-M and really set ourselves up for a strong foundation to build on but I have yet to find anyone that's taken that step. More guidance material for the ISA-M methodology and how it can provide value is needed.


      Author's profile photo Mastan Vali Meduturu
      Mastan Vali Meduturu

      Hi Thorsten,

      Is SAP Assessment and Migration Tool is free or any cost involved.




      Author's profile photo Thorsten Düvelmeyer
      Thorsten Düvelmeyer
      Blog Post Author


      it comes with SAP Integration Suite.
      For testing pupose, you can use it with the free trial option of Integration suite.

      Best Regards,

      Author's profile photo Richard Kleibl
      Richard Kleibl



      it is free if you have an integration suite license. As of now, you can also use a Free-Tier account.

      In October/November it should also be available with a trial account.


      Kind regards