You can try Figaf in your migration projects for free. Just start a free trial and you can get started with the tool right away. Figaf covers all the needs you have for your migration projects.
Customers of SAP Integration Suite can use SAP’s free migration tool. It offers users the ability to migrate ICOs to SAP Integration Suite.
We have built our own migration tool and keep improving it. This is a paid tool that we believe simplifies your migration making it a more cost-effective solution.
Some integrations may not work in SAP but work with Figaf or vice versa. You therefore need to understand what will work best for your scenarios.
SAP’s Approach
SAP’s tool is based on templates. You can see the list of supported templates here. An ICO is migrated to one of those templates, so if its structure does not match a template, the tool cannot migrate it.
Check SAP’s documentation for how message mappings with Function Libraries are handled. How well the tool works depends on your landscape, and SAP keeps improving it, so look at the roadmap for what is coming.
Figaf’s Approach
We started out building BPMN models for the structure in the ICO or Receiver Determination. This means we can migrate all cases, though some better than others. There is still going to be some manual work to ensure your integration works smoothly.
This is a license service that you will need to pay for. The price is based on the number of migration objects, each an ICO + Operation Mapping pair. It starts at €100 per object for the first 200, and goes down to €60 per object with volume. See all prices. You can try out the free trial.
Routing based on the structure of the ICO or Receiver Determination. For each receiver and receiver interface a new local process is created. This allows more specific error handling and routing. Xpath conditions are translated. The process comes with built-in retry for failed messages.
Message Mappings are migrated and updated. The tool updates mapped parameters and constants that are not supported by the standard Cloud Integration mappings. Function Libraries can use SAP Standard FL object or our Custom Groovy conversion. You need both because they have different challenges. It is possible to reuse the objects easily.
Channel is mapped in Figaf by a custom XSLT that enables you to define how you want a special migration to happen. This will allow you to set up File to SFTP or FTPS the way you want to handle it. This simplifies the development. You will also only be able to configure the elements that you decide. There are some standard templates but it takes 5 minutes to create a custom template for the scenarios you have.
Special development we have added support for File Content Converter using the same configuration and setup as SAP’s original setup. This allows you to migrate these cases without much impact. There is also a specific B2B mode that will enable you to migrate all your existing B2B interfaces without having to rebuild the mappings.
Support for dual stack systems. Figaf supports migration of 7.11-7.5 both dual stack objects and ICO. This enables you to migrate without having to upgrade first.
Faster changes. We have been making new modifications to our tooling in one week from idea to released patch, allowing you to continue with your migration effort. It does depend on the challenge and our current backlog. Try to compare this with SAP’s timelines.
Cost and Risk reduction
We believe the Figaf migration approach will enable you to migrate your integration much faster and enable us to justify a price for the migration. The more integrations you can migrate automatically, the more time you have to focus on areas that do not make sense to migrate.
The cost of the project will be lower because less work is needed for manual work to update migrations to run. There will still be some. This also will allow you to have more junior developers on the team.
With the built-in test tool you also can test the integration once you have delivered the migration. If you perform the testing you can always fix the scenario.
Pilot project
We already recommend that you do a pilot project before you start full scale of your migration. Here you should evaluate both tools and see what enables you to migrate certain scenarios most cost-effectively. There are going to be 3 scenarios:
- Some that SAP’s tool enables you to migrate faster
- Some where Figaf is the most cost effective way
- Some you will need to redesign, because a migration is not possible.
It is better to have multiple options to perform the migration. See more on the pilot project here.
