Back Up, Maintain, and Update SalePro Safely
Back up files and databases, verify the target release instructions, rehearse on a non-production copy, and reconcile afterward.
Before an update or migration, record the current version/commit, back up application files and every tenant/database, protect secrets, and rehearse with a copy. Follow the release-specific update path; do not overwrite protected updater behavior or run destructive module rollback migrations as an uninstall method.
Afterward, check migrations, module availability, permissions, queues/schedules, storage links, mail, payment callbacks, one purchase/sale/return, stock, dues, accounting health, and reports. Keep a rollback decision and evidence. The legacy generic “replace files and run script if applicable” wording is not sufficient release guidance.
If something is unclear, tell support which guide and section you were following.