Paami is a professional upgrade tool for enterprise software customisations. Open your project, pick a target version, and review a clean patch set. One consistent workflow across every supported ERP.
Quick start
# Detect which ERP and version your project uses
npx paami detect --path .
# Preview an upgrade plan — no tokens spent
npx paami upgrade --platform odoo --from 16.0 --to 17.0 --path . --dry-run
That is the entire setup. The CLI works with npx, yarn dlx, pnpm dlx, and bunx out of the box.
Paami supports 14 self-hosted ERP platforms. Auto-updating SaaS platforms (Workday, ServiceNow, Oracle Fusion) are intentionally excluded — the vendor manages version upgrades centrally on those, so there is no per-customer migration to perform.
| # |
Platform |
Versions |
| 1 |
Odoo |
13 → 19 |
| 2 |
SAP ABAP |
ECC 6.0 → S/4HANA 2023 |
| 3 |
Salesforce |
API v55 → v62 |
| 4 |
NetSuite |
SuiteScript 1.0 → 2.0 → 2.1 |
| 5 |
Oracle E-Business Suite |
12.1 → 12.2 → Cloud |
| 6 |
JD Edwards EnterpriseOne |
Tools 9.1 → 9.2.6 |
| 7 |
PeopleSoft |
PeopleTools 8.55 → 8.61 |
| 8 |
Dynamics 365 Business Central |
BC18 → BC26 |
| 9 |
Dynamics 365 Finance & Operations |
AX 2012 R3 → D365 F&O 10.0.42 |
| 10 |
Infor CloudSuite |
M3 13.4 → CloudSuite 2025 |
| 11 |
Acumatica |
2022R2 → 2025R1 |
| 12 |
Epicor Kinetic |
2022.1 → 2024.2 |
| 13 |
IFS Cloud |
Apps10 → Cloud 25R1 |
| 14 |
Sage X3 / 300 |
V11 → 2025R1 |
What it does
- Detects your ERP and version automatically from the source layout — no manual configuration required.
- Plans the upgrade. Reads breaking-change knowledge for the target version pair, walks your modules in dependency order, and shows you exactly what will change before any work starts.
- Generates reviewable patches. Every transformation is emitted as a unified diff and saved to disk. You inspect, accept, or refine — nothing is rewritten in place without your review.
- Snapshots and rolls back. A workspace snapshot is captured before every run; one command restores prior state.
- Validates as it goes. Lightweight platform-specific checks flag the most common version-incompatibility patterns; the post-run summary points you at the right native validator (Odoo's Docker harness, Salesforce CLI deploy validation, SAP ATC, etc.).
- Source-residency aware. Cloud or fully local execution backend — switch with a single flag for regulated environments.
Working Modes
VS Code extension
Open the Paami panel from the activity bar. The panel adapts to whatever ERP is detected in the open workspace — version dropdowns, badges, and post-run validator hints all switch automatically:
- Auto-detect the platform and current version.
- Pick a target version.
- Watch the upgrade run with live progress, file-by-file status, and a streaming log.
- Review the generated patches before applying.
Command-line interface
For scripted, headless, and CI/CD use. Same engine as the VS Code panel.
paami detect --path ./my-project
paami upgrade --platform <id> --from <version> --to <version> --path <dir>
Add --dry-run to preview the plan without spending any budget. Add --llm local to route every transformation through a local backend (recommended for source-residency-restricted environments).
Run paami help for the full platform list and option reference.
Installation
VS Code
- Install the extension from the Visual Studio Marketplace.
- Open the Paami panel from the activity bar.
- Configure your access credentials in the extension settings.
CLI
The CLI is published to npm and works with every major Node package manager. Pick whichever you prefer — no global install required for one-shot use:
# One-shot (no install)
npx paami detect --path .
yarn dlx paami detect --path .
pnpm dlx paami detect --path .
bunx paami detect --path .
# Global install
npm install -g paami
yarn global add paami
pnpm add -g paami
bun add -g paami
After installation, run paami help to see the full command reference.
Workflow
- Detect — Paami identifies the ERP platform and current version.
- Plan — Build an ordered upgrade plan from the version path and your project's dependency graph.
- Execute — Apply transformations per module, per step. Progress streams back to the UI or CLI.
- Review — Patches are written to
.paami/patches/<checkpoint-id>/ for inspection.
- Rollback (optional) — Restore the workspace from the snapshot taken before the run.
- Native validation (optional) — Run your ERP's own validator after applying patches. Paami surfaces the right command for whichever platform you upgraded.
Usage Guidelines
- Review the generated plan before authorising execution.
- Always work on a version-controlled or backed-up copy of the source.
- Inspect each patch before applying it, especially those marked for human review.
- Run the upgraded code through the platform's native validator and test suite before promoting to production.
Support
Issues and feature requests are tracked in the Resources section of this listing.
