HomeServicesIvalua upgrade and version migration: assessment, then the upgrade
Ivalua upgrade and version migration: assessment, then the upgrade
How hard an Ivalua upgrade is depends on two things: how much your configuration and interfaces differ from the standard, and how many versions you skip. A one to two-week assessment, from €7,500, measures both. You get the plan before the upgrade starts.
Who needs an Ivalua upgrade assessment?
Teams that are several versions behind. Teams whose upgrade is postponed again and again in the roadmap. Also teams that are not sure whether to upgrade the current solution or rebuild a simpler one on the new version. Migration from SAP Ariba to Ivalua is a different subject, covered in the guide SAP Ariba to Ivalua migration.
How often does Ivalua require an upgrade?
Ivalua’s standard terms require an upgrade at least once every two years. They recommend one every 12 to 18 months. The terms are published in a public US contract: the master agreement Ivalua signed with the State of Maine under NASPO ValuePoint in 2023.
| Rule | What the terms say |
|---|---|
| Frequency | At least one upgrade every 12 to 18 months recommended; at least one every two years required |
| Target version | Usually one of the two most recent versions released, and only a version that is generally available |
| Limit | One upgrade per 12 months, unless both parties agree |
| What is included | Ivalua’s resources to support the upgrade are included in the fees |
| What is billed | New features or modules may need extra work. Customisations, complex configurations and integrations added after go-live are billed as extra work at each upgrade |
| Freeze on changes | No new changes to the platform during the whole upgrade. A shorter freeze costs extra fees to merge the changes and test again |
| Prerequisites | Detailed test scripts written by the customer, a signed project plan, and the work charges in a statement of work |
| If you fall behind | Ivalua is not responsible for defects, security issues or a missed SLA while the customer is not in compliance |
The terms say it: the cost of an upgrade comes from your specific settings and from the versions you skip.
Source: Ivalua’s standard terms in a public US contract, master agreement MA 18P 23081100000000000020, effective August 2023. Your own contract may differ. The assessment checks it.
How hard is an Ivalua upgrade?
It can be a simple technical step or a full project. Ivalua’s terms say it can take days, weeks or months. The time depends on how complex your implementation is: customisations, complex configurations, regional variations, non-standard integrations, number of modules. It also depends on how many versions you skip, because some versions require rework or a migration. For a short upgrade, Ivalua itself recommends staying close to the standard features and upgrading regularly.
An example of a light upgrade: EPFL moved from version 170 to 178. The service stopped from a Wednesday at 16:30 to the Thursday morning, and production started on 27 June 2024. It was a technical version change: no new feature, and the functions specific to EPFL did not change (EPFL news).
What breaks when you upgrade Ivalua?
The items the standard terms list as costly are also the ones that need the most testing:
- Specific configurations and custom objects built after go-live, such as an extra approval step or a custom supplier form. Each one has to be moved to the new version and tested again.
- Non-standard integrations, above all the ERP interfaces. If a message format or a rule changes, the ERP rejects orders or invoices.
- Workflows with many exceptions, and custom alerts, queries and reports that depend on the data model.
- Skipped versions: the more versions you skip, the more rework and migration tasks add up.
- Your own changes: the freeze stops them. For example, a new approval rule that finance asks for must wait until the upgrade is live. The business has to plan for this.
How do you prepare an Ivalua upgrade?
- List the specific configurations, custom objects, integrations and reports. For each one, decide: keep, simplify or remove. Look for settings added over the years that nobody uses any more, but that must still be tested at every upgrade.
- Write or update the regression test scripts (the tests that check what worked before still works). The terms make them a prerequisite.
- Check the data that will move: supplier duplicates, statuses, records the new version will handle differently.
- List the interfaces with the ERP and other systems. Plan their end-to-end tests with the teams that run those systems.
- Agree the freeze on changes with the business and the sponsors, and sign the project plan.
- Choose the target version and the approach: upgrade the current solution, or build a new solution on the new version.
What upgrade and migration work have I done?
I did three full cycles on the same group platform at BNP Paribas. In two of them, the choice was between upgrading the existing configuration and rebuilding it:
| Version | Approach | Why, and what I did |
|---|---|---|
| v156 | Build and deploy | Built and deployed the group’s S2P platform: suppliers, sourcing, CLM, catalogue, BPM, e-procurement, with many complex specific configurations |
| v164 | Complete redesign, built from scratch | v156 carried many complex specific configurations. The rebuild started again and simplified them, and redesigned the workflows. Delivered on budget and on schedule |
| v182 | New solution built from scratch, moving from v164 | Migration work from start to end: data quality controls, duplicate detection, documentation of the data flows until sign-off. Delivered on schedule and still evolving. The old and the new version run side by side while entities and users switch over |
In two of three cycles, the choice was to rebuild rather than upgrade the old configuration.
What does the upgrade assessment deliver, and what does it cost?
- The inventory: specific configurations, custom objects, integrations and reports, each with a recommendation: keep, simplify or remove.
- The impact analysis: what the versions between yours and the target version change for your configuration and interfaces.
- The approach: upgrade the current solution or rebuild, with the reasons.
- The plan: test scripts to write, data to clean, interfaces to test again, the freeze on changes, and the order of the steps.
The assessment takes one to two weeks and costs from €7,500 excluding VAT, at a fixed price. The upgrade itself is custom and priced on the plan. I can run it as a senior mission or with an Ivalua team I lead.
Frequently asked questions
How long does an Ivalua upgrade take?
Ivalua’s standard terms say days, weeks or months. The time depends on how complex the implementation is and on how many versions you skip. A technical upgrade on a configuration close to the standard can be short. A jump of several versions with many specific configurations is a full project.
What happens if we skip upgrades?
Ivalua’s standard terms are published in a public US contract. Under them, the customer must upgrade at least once every two years. Ivalua is not responsible for defects, security issues or a missed SLA while the customer is not in compliance. Each skipped version also makes the next upgrade bigger.
Should we upgrade in place or rebuild?
Upgrade in place when the configuration still fits the business and stays close to the standard. Think about a rebuild when specific configurations have piled up over the years. At BNP Paribas, the platform was rebuilt from scratch on v164 for this reason, and v182 was again a new solution. The assessment gives the recommendation and the reasons.
What certification does Ivalua require to configure the platform?
In Ivalua’s standard terms, whoever configures the platform needs Ivalua Level 2 certification, and Level 3 for integrations. Otherwise, the third party chosen by the customer must be an Ivalua certified partner. The rule applies to every configuration, upgrades included. I am certified Ivalua L1, L2 and L3.
Does the freeze on changes stop the business?
It stops changes to the platform, not its use. During the upgrade, no new change is built, so open requests wait. The assessment plans the freeze with the business, so that urgent changes go live before it starts.
30 minutes. Your project, my honest opinion.
Tell me where your programme is today. After the call, you know the main risks and the next step, whether or not we work together.