Migration Guide
Updating SigmaOrders, switching databases, or migrating from another plugin.
Version Updates
Config and database schema updates are automatic - new options get defaults, old data is preserved, no manual migration needed for most updates.
- Backup:
cp -r plugins/SigmaOrders plugins/SigmaOrders.backup - Replace the JAR and start the server - the plugin migrates automatically.
- Verify: check console for migration messages, test basic functionality, review new config options.
SQLite → MySQL
- Backup:
cp plugins/SigmaOrders/database.db database.db.backup - Set
type: MYSQLand connection details inconfig.yml(see Database Configuration). - Restart - the plugin creates MySQL tables automatically. The old SQLite file is kept untouched.
Data migration is not automatic - export/import data manually or start fresh.
From Other Plugins
- Export orders from the old plugin if it supports it.
- Install and configure SigmaOrders.
- Re-create orders via the API, or manually. Migration from specific plugins may need custom scripts - contact support.
Rollback
- Stop the server.
- Restore the plugin folder:
rm -rf plugins/SigmaOrders && cp -r plugins/SigmaOrders.backup plugins/SigmaOrders - If needed, restore the database:
cp plugins/SigmaOrders.backup/database.db plugins/SigmaOrders/ - Start the server and report the issue.
Testing Migration
Test on a dev server first: verify orders load, test order creation/delivery/collection, confirm payments work, and check statistics. Do this before and after migrating on production.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Config errors after update | Bad YAML, stale syntax | Check YAML syntax, restore from backup, check console for the specific error |
| Data missing/corrupted after migration | Failed or partial migration | Restore database backup, check migration logs in console, verify database integrity |
| Slower after migration | New config defaults not tuned, still on SQLite | Review new config options, consider MySQL, see Performance Guide |