Week 4 of 8
What makes you different
Standard functionality is tested by the vendor before it ships. Your configuration, customizations, ISV add-ons, integrations, reports and import templates are not. Those are what break.
The vendors give you tools to find them. IFS Cloud’s Release Update Studio runs an Impact Assessment against your customizations before you take a release. Acumatica validates customization projects for compatibility when you publish them on the new version. Odoo will not upgrade a database until its custom modules are ready for the target version.
This week: inventory everything that is not vanilla
- List every customization by type: IFS solution repository changes, Epicor BPMs and Application Studio layers, Acumatica customization projects, Odoo custom modules, Sage X3 specific developments.
- Add every ISV add-on, integration, scheduled job, report, form and data import template, each with an owner.
- Map each item to the processes it touches from last week’s ranking.
- Mark each item mandatory for every release regression. Nothing on this list rides on the vendor’s testing.
Number of the week
~6 months
after a major Acumatica release is when Always Current upgrades SaaS customers, with about 90 days’ notice. That is your window to validate customizations.
Source: Acumatica Community, The Always Current Program (January 2026)Use this week
- ERP Vendor Update Test Plan →
A customization and add-on inventory plus a per-release plan that works for IFS, Epicor, Acumatica, Sage and Odoo cadences.
- Change Impact Analysis Log →
Changed objects, impacted processes and selected tests for every change.
Next week: data imports run through your business logic, and their templates change between releases. We test them like code.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.