Scipio ERP began as a fork of Apache OFBiz, so most of an OFBiz project carries over: the entity model, the services, the screens and your component descriptors. What does not carry over is small and known. This check finds it in your own code.
Paste a few files, or pick one of your component folders. The check runs in your browser and lists what must change, what to look at, and what loads as it is.
Runs in your browser. Your code is not uploaded anywhere.
What the check looks for#
- Package names. OFBiz moved to
org.apache.ofbiz.*with release 16.11. Scipio ERP keptorg.ofbiz.*, so newer OFBiz code changes its imports back. The check can rewrite them for you. - The build. Scipio ERP 4.0 builds with Gradle and no longer reads Ant
build.xmlfiles. Components inhot-deploy/oraddons/are found on their own. - The JDK. Java 11, 17 or 21. Java 8 is no longer supported.
- Replaced libraries. Jakarta ORO, iText 2.1.7, Tika 1,
groovy-alland bundled servlet API jars. - The XML-RPC handler, which is gone from the controllers.
- Themes. The old OFBiz themes are not bundled, and theme data needs a reseed.
What it cannot see: changes you made inside the OFBiz framework itself, and classes OFBiz added after 2018. For those, the OFBiz migration guide has the step-by-step notes.
Then try it on your data#
The data model is still the OFBiz data model, extended. Export your data with the entity export of your OFBiz system, import it into a Scipio ERP test server, and compare what arrives. Scipio ERP 4.0 is in preview: the code is on GitHub , the demo runs it, and the download page has the setup.
Scipio ERP 4.0 is licensed under the AGPL-3.0, with a commercial license beside it; the files that came from OFBiz keep their Apache header. The Community edition is free. Enterprise is €4,800 per production instance and year, plus VAT. The full comparison is on Scipio ERP vs Apache OFBiz .