Frequently asked questions

Your data stays with you. On SAP BTP, Docker or a local PC, it is stored in a PostgreSQL database that you operate. With Figaf Cloud, Figaf hosts the application, but not your data.

Figaf receives usage information, such as the first time you use a function, and the hashed names of the ICOs and iFlows you use with each feature. Beyond that, no data is sent to Figaf automatically.

No. Figaf does not have access to your data, so we cannot train models on your content.

Figaf is penetration tested periodically by an external company. The architecture was found robust, with no traces of data loss and no open security threats.

If a security threat is found, it is handled as a high-priority ticket and fixed with a patch right away.

Since we do not host your private data, a leak is not likely.

We check our dependencies, and if there is something major, like log4j in 2021, or a problem in our code, we inform our users and provide a workaround.

Mainstream maintenance ends December 31, 2027. Extended maintenance is available until December 31, 2030 at additional cost.

It depends on the number and complexity of interfaces. Run a pilot to measure your own per-interface time, then use the migration estimator.

With Figaf, yes: ICOs and dual-stack objects from PI 7.11 through 7.5 are supported. SAP’s own migration tool supports PI/PO 7.31, 7.4 and 7.5.

Neither handles every scenario best. Pilot both against a representative set of your own interfaces and compare.

No. Figaf is much more than migration, but migration is a really good place to start.

You can migrate an ICO in about 10 minutes and spend another 10 minutes testing it. When there are no complications, the complexity of the ICO and its components does not matter.

There are cases, though, where you run into points Figaf cannot handle, which you then need to resolve.

• Communication channels are migrated with your own templates. This means fewer externalized parameters, and once you have a channel that works, you can create a template in 5 minutes.
• UDFs and function libraries can be converted to Groovy scripts, or use the standard function library objects. This gives your mappings more options, with less manual work.
• More configuration on each iFlow.
• A faster turnaround on new features.

• We can migrate the majority of scenarios without modification.
• Groovy UDFs, together with our Groovy editor, simplify how you deal with the integration.
• Custom channel templates save configuration work.
• A host of small improvements solve the edge cases that are difficult to quantify.
• It is integrated with the tool chain: testing, transport and documentation.

The most complete overview of your SAP PI/PO system that you will ever see, and it is free. It shows all your ICOs and receiver determinations with all dependent objects and receivers. You can use tagging to run custom searches in your SAP PI objects for more information.

No. There are too many factors involved. Our view is that all integrations can be migrated, but it is up to you to decide whether they should be.

Yes. We think it provides a lot of good ways to handle asynchronous message processing with retries.

No, and it is not a focus for us.

Java mappings can be migrated, but they are wrapped in a Groovy script. This brings some limitations, so it is often best to redesign these mappings. The Groovy editor really helps here.

ABAP mappings need to be implemented in Groovy.

Yes. RFC lookups are migrated as an empty UDF, and you then fill in the lookup yourself.

The Migration Edition is our collaboration with SAP that lets you run and test your migration with Figaf.

• Manage your migration project.
• Create a detailed assessment of your SAP PI landscape.
• Record messages from SAP PI and run the tests on SAP Cloud Integration. The tests are valid for 30 days; after that, fetch new messages from your SAP PI system or get a testing license.
• 10 free migrations with the Figaf tool.
• A 2-month trial of the DevOps tool.

We recommend running Figaf on SAP BTP, because it is the easiest platform to operate. It costs roughly €300 a month to run, paid with your SAP BTP credits, and you can lower the cost for smaller installations.

We recommend deploying it on SAP BTP Cloud Foundry, where you can use SAP’s user management to simplify onboarding and sharing in your team, and run the app as a Docker image; see the deployment guide. To connect to your SAP PI/PO system you need a Cloud Connector that gives Figaf access to it.

You can also run Figaf as a standalone application on your laptop, though you cannot share your test results with your team that way. It is a good way to evaluate the tool. Or run it on any server, on-premise or at a hyperscaler, with Java 21 and PostgreSQL or MSSQL.

We have focused on making it easy to use, so everybody can get started fast. Our free online training takes you from installation to configuration and daily use.

Since it is a free edition, you do not get everything in our paid edition. Support is limited to our forum: we try to help with your challenges, but paying customers come first. Testing is limited to test cases created from your SAP PI/PO system, run on your migrated iFlows for 30 days; you can always create new test cases and use them for another 30 days. The full tool is a trial for the first 2 months, with limits on the number of objects.

A migration takes a lot of hours, and a tool that automates even 10-20% of the work pays for itself. With the full version you improve how you deliver on SAP Integration Suite after the migration, reuse your test cases for regression testing, transport with governance, and get our support.

See the pricing page for the full version.

Figaf has two license components:

• Migration is a one-time cost per migration object: an ICO, an operation mapping for B2B, or a receiver determination. It starts at €100 per object and goes down to €60 with volume. Every Figaf Migration Tool subscription includes a 2-month trial of Figaf DevOps.
• DevOps is a monthly or, in most cases, yearly cost. You pay either for a feature, like testing or transport, or for the whole suite, based on the number of license objects.

See all prices.

The DevOps license is based on the integration objects in your development system. It counts iFlows, TPM agreements, MAGs and API Management proxies.

An agent is a connection to a system, like SAP PI/PO, API Management or Integration Suite/CPI. We count real subaccounts, and API Management is a separate agent.

Figaf can save you a tenant with a virtual tenant. You can have physical development and production tenants, and QA as a virtual tenant: the iFlows are copied into a separate package on the development tenant, with a different name and endpoint, which keeps them unique.

Yes. External configuration is a crucial part of transports, and in Figaf it is part of the transport itself: when you transport an iFlow, you add all the objects that need to go with it.

No. Figaf has its own file transport management and does not rely on Cloud Transport Management, which makes the tool much more flexible.

• Easy building of Groovy scripts on your own system.
• Reuse of your test cases to run the scripts in your landscape.
• Easy updates of the iFlows or script collections once you have made changes.

Yes. Running the script on your own integration engine gives you that advantage.

Yes. Your test data and scripts are only sent to your own Integration Suite.

It depends on your scope. Cloud Integration DevOps, including testing, takes about 4 hours for users, and a bit more for super users. PI to Integration Suite migration takes about 8 hours: the key is to understand what happens to the objects and how to perform the different steps.

In a short time, you can be confident using the tool.

Yes. There are a lot of online guides and free courses to help you get started with the tool.