Skip to main content
Upgrading OwnPay between versions involves database schema changes, file updates, and cache clearing. This guide walks you through the process from preparation to verification.

Version history

Check the Changelog for the full list of changes in each release.

Pre-migration checklist

Complete every item before starting an upgrade. Skipping any of these steps risks data loss or a broken installation.

Migration process

OwnPay uses an auto-migration system that runs at boot time. You do not need to run migration commands manually.

How auto-migration works

When Kernel::boot() runs, it compares the current schema version (stored in op_system_settings) against the code version. If they differ, it executes pending migration files from database/migrations/ in order. Each migration file uses a safe pattern:
This SHOW COLUMNS / ALTER TABLE pattern means migrations are idempotent - running them multiple times is safe.

Running the upgrade


Post-migration steps

After the migration completes, verify everything is working correctly.

Rollback

If something goes wrong after an upgrade, restore from your pre-migration backups.
Rolling back after the new version has processed transactions will create a data mismatch. The restored database will not contain transactions that were completed between the upgrade and the rollback. Reconcile with your gateway dashboards.

Last modified on August 25, 2026