What does moving from SAP Ariba to Ivalua involve?
A move from SAP Ariba to Ivalua is a new Ivalua implementation with a data export at the start. You take your suppliers, contracts and catalogues out of Ariba, clean them and load them into Ivalua. Processes, approval rules and ERP interfaces are built again on Ivalua. Suppliers move from the SAP Business Network to Ivalua’s supplier portal.
It is not a version upgrade. An Ivalua upgrade moves your own Ivalua configuration to a newer Ivalua release; that is the subject of my Ivalua upgrade service. Here, nothing from Ariba’s configuration carries over. The phases are those of any Ivalua project, described in How does an Ivalua implementation work?
| Ivalua version upgrade | SAP Ariba to Ivalua migration | |
|---|---|---|
| What moves | Your Ivalua configuration, interfaces and data, to a newer Ivalua release | Your data only. Processes, rules and interfaces are designed and built again |
| Supplier side | Suppliers keep the same portal | Suppliers change channel: from the SAP Business Network to the Ivalua portal |
| ERP interfaces | Checked and tested again | Built again for Ivalua |
| Contract with the old vendor | Not affected | Your SAP contract decides how and until when you can export your data |
Plan a migration from Ariba as a full Ivalua implementation, plus a data exit from Ariba with its own deadline.
Is SAP Ariba being discontinued?
No. On 12 March 2026, SAP made next-gen SAP Ariba available, rebuilt on SAP Business Technology Platform. SAP says existing customers can move to it on a voluntary basis, without commercial implications, with new capabilities delivered through 2026 and into 2027. No end date for the current Ariba has been announced.
Two older SAP dates are fixed, and they often start the discussion:
- Integration Toolkit (ITK). SAP stopped supporting ITK, Ariba’s tool for file-based integration, on 31 December 2023: no fixes, no security updates. SAP points customers to SAP Integration Suite instead. If your ERP still talks to Ariba through ITK, those interfaces have to be rebuilt anyway, on Ariba or on another platform.
- SAP Business Suite 7 (on premise). SAP announced in February 2020 that standard maintenance for the core Business Suite 7 applications runs until the end of 2027, with optional extended maintenance until the end of 2030. SAP lists SAP SRM 7.0 among these core applications, so companies still on on-premise SRM fall under these dates. SRM is a different product from the Ariba cloud.
So a move to next-gen Ariba is also a change of platform, in waves until 2027. That is often the moment when a company compares Ariba with other suites. For a comparison from published facts, see Ivalua vs Coupa, which has a section on SAP Ariba, and Ivalua alternatives.
Has an organisation moved from SAP Ariba to Ivalua?
One case is documented in public sources: the Commonwealth of Virginia’s eVA procurement platform. In March 2021, Ivalua announced that Virginia’s Department of General Services had awarded a contract to CGI, which uses the Ivalua platform, to transform eVA. The switch took place in 2022.
| What changed | What the public source says | Source |
|---|---|---|
| Why they moved | An ageing user interface; “the supplier network heavily leveraged by the previous provider imposed fees, relationship barriers, and technical hurdles”; a legacy system that had become “a patchwork of different tools” | Ivalua case study, 2026 (it says “previous provider”, not Ariba) |
| Suppliers | Orders no longer go to the Ariba Network but to the supplier’s eVA account; punchout catalogues tested again | Supplier notice from a Virginia university, March 2022 |
| State IT interfaces | An amendment to the State’s IT integrator contract removed Ariba and added Ivalua: a custom integration hub was required, $76,000 plus service hours | Virginia IT agency report, April 2022 |
| Scope today | Supplier risk and performance, sourcing, contracts, eProcurement, intake, invoicing, payments and spend analysis, on more than $10.8 billion of annual spend | Ivalua case study, 2026 |
| Reported results | More than $5 million of annualised savings; average solicitation cycle down to 69 days from 121 days the previous fiscal year | Ivalua case study, 2026 (vendor statement) |
The parts that touched other people, suppliers and the State’s IT systems, are the parts with public records. Plan them first.
Ivalua’s published case studies and press releases name no other customer that left SAP Ariba. A public tender that mentions both names is not proof of a migration. The supplier side of such a switch is covered in Ivalua supplier portal.
What data can you take out of SAP Ariba?
Your SAP contract decides. SAP’s General Terms and Conditions for cloud services (the 2020 version I read) say that during the subscription you can export your data “in a standard format”, subject to “technical limitations”. Before the subscription expires, you can run a final export with SAP’s self-service tools, “as available”. At the end of the agreement, SAP deletes the data that remains.
That version gives no extra period after the contract ends. Your own order form and supplements may say something different: read them before you set the go-live date.
| Data in Ariba | What public sources say | What to check |
|---|---|---|
| Supplier master data | Virginia converted supplier accounts to the new eVA | Which system owns suppliers after the move: Ivalua or the ERP. Clean duplicates before the load |
| Active contracts and their documents | A customer on SAP Community (April 2024) wrote that ITK used to be the only way to download all contract data, and that “not all” of it is possible through the APIs. No one answered | Test a full export of a few real contracts early: header, team, documents, forms, tasks, history |
| Contract history, tasks, forms | Same post: header data, team members, documents, task details and history were the hard part | Decide what you load into Ivalua and what you only archive |
| Catalogues and punchouts | Virginia tested punchout catalogues again with suppliers | List each punchout supplier and plan a test with each one |
| Supplier network connection | Virginia’s suppliers received orders in their eVA account, not on the Ariba Network | Tell suppliers early which channel to use from which date |
| Open purchase orders | No public source found | Ask your integrator: close them in Ariba, or load them into Ivalua? |
| Sourcing events and auction history | No public source found | Ask SAP what the export contains, and decide how long you must keep it |
| ERP interfaces | Virginia needed a custom integration hub for the State’s systems | List every interface and who builds the new one |
Where there is no public source, there is no shared practice to copy: get the answer in writing from SAP and from your integrator before you plan the cutover.
Data is often where Ivalua projects run late. In Ivalua’s own survey of 31 system integrators, data migration and integration were cited at 41.3% among implementation challenges. On the BNP Paribas v182 programme, my migration work went from data quality controls and duplicate detection to the documentation of each data flow, up to sign-off.
What should you check before you start?
- Read the data clause of your SAP contract. Note the end date of the subscription and what the order form says about export. The last export must happen before that date.
- Run a test export. Take a few real suppliers and contracts, and check what comes out: fields, documents, history. Do it before you plan the project.
- Decide what to load and what to archive. Active suppliers, contracts and catalogues usually need to live in Ivalua. Closed history may only need to be kept and searchable somewhere.
- Plan the supplier switch. Each supplier changes channel. Tell them the date, the new portal and who to call. Test punchouts supplier by supplier.
- List the interfaces. ERP flows, single sign-on, payment status, and anything that ran through ITK. Ivalua ERP integration lists the usual flows.
- Design on the Ivalua standard. Do not rebuild Ariba screen by screen. Ivalua’s 2023 terms charge complex configuration added after go-live again at every upgrade.
There is no public figure for the time or cost of an Ariba to Ivalua migration. Public Ivalua implementations range from 8 weeks for a packaged procure-to-pay scope to six to ten months for a multi-module suite. The details are in Ivalua implementation cost and timeline. Add the data exit from Ariba and the supplier switch on top.
Where can I help?
On the Ivalua side: everything that lands in Ivalua. Once your data is out of Ariba, I design and configure Ivalua, build the ERP and supplier interfaces, write the SQL for controls and reports, and run the data migration into Ivalua: quality controls, duplicate detection, flow documentation and sign-off.
I am certified Ivalua L1, L2 and L3 and have worked on three full-cycle Ivalua implementations at BNP Paribas. On a migration programme, I can join your team on a senior mission, or lead an Ivalua team of certified consultants from my network. Both are at a day rate, on request.
Frequently asked questions
Short answers to the questions people ask, each one sourced above.
Is SAP Ariba end of life?
No. In March 2026 SAP made next-gen SAP Ariba available and said existing customers can move to it on a voluntary basis, without commercial implications. No end date for the current Ariba has been announced. The fixed dates concern other products: the Integration Toolkit (end of support 31 December 2023) and on-premise SAP Business Suite 7 (standard maintenance until the end of 2027).
How long does a migration from SAP Ariba to Ivalua take?
No public source gives a duration for this kind of move. It is a full Ivalua implementation, and public Ivalua projects range from 8 weeks for a packaged procure-to-pay scope to six to ten months for a multi-module suite. Add the data export from Ariba, which must finish before your SAP subscription ends, and the supplier switch.
Can suppliers keep using the SAP Business Network after the move?
Not for the orders you send from Ivalua. In Virginia’s case, orders went to the supplier’s eVA account on Ivalua instead of the Ariba Network, and punchout catalogues were tested again. A supplier who also works with other Ariba customers keeps that network for them. Tell your suppliers the new channel and the date early.
Is moving from SAP Ariba to Ivalua the same as an Ivalua upgrade?
No. An Ivalua upgrade moves your existing Ivalua configuration to a newer Ivalua release. A move from Ariba builds Ivalua from the start and only takes your data from Ariba. The upgrade has its own service and its own fixed-price assessment.
Which part of an Ariba to Ivalua move can you take on?
The Ivalua side: design and configuration, ERP and supplier interfaces, and the data migration into Ivalua. On the BNP Paribas v182 programme, I worked on the migration workstreams end to end, from data quality controls and duplicate detection to flow documentation and sign-off. The export from Ariba itself is a question for SAP and your integrator.
Project already started? Check where it stands.
The health check scores your platform and your programme in three weeks.
Seb Troz
Certified Ivalua consultant (L1–L3). Three full-cycle implementations at BNP Paribas (v156, v164, v182), programme manager at Vallourec. Led a team of 13 on Rapsody at Société Générale. Engineer, ENSIMAG. About Seb