Database Migrations During Deployment
When a new feature needs the database structure to change — a new column, a new table — those changes are applied through controlled scripts called migrations.
Handling them carefully during deployment is essential, because your data is your most valuable and least replaceable asset.
How We Apply Changes Safely
- Migrations are written as versioned, reviewable scripts.
- They are tested against a copy of real data first.
- A backup is confirmed before anything runs in production.
- Changes are applied in a way that the running app can tolerate.
Backward-Compatible Changes
Wherever possible we make changes that both the old and new versions of the application can cope with. This allows zero-downtime deployments and means a rollback never leaves the database in a state the code cannot understand.
Frequently Asked Questions
Is my data at risk during a migration?
We always confirm a fresh backup first and test migrations on a copy, so there is a clear recovery path if anything is unexpected.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.