Hi Huy,

OutSystems allows you to roll back the application code, but it does not support automatic database rollback as part of the deployment pipeline. Once new data is written in Production, the platform will not revert it when you roll back the module version.

To manage data rollback, here are the practical options used in large OutSystems projects:

1. Use your database backup strategy Before deploying to Production, make a full DB backup at the infrastructure level (SQL Server or Oracle). If something goes wrong, the only way to truly “rollback” data is to restore that backup. This is the recommended and safest approach.

2. Create data migration scripts If the deployment includes data changes, you can prepare:

• an “upgrade script” to apply new data, and

• a “rollback script” to revert the data if needed. These scripts are executed manually by the DB team when troubleshooting.

3. Avoid destructive data changes If possible, design new features so they do not override or delete existing data. This makes rollback unnecessary.

4. For small controlled datasets, export before deploy If the tables involved are small and non-critical, you can export the data before deployment and re-import it if needed, but this is only viable for specific scenarios.