Hi,

In Odoo SH, Git manages all code in your repository, but database-level changes like installed apps, system settings, and Studio customizations are not tracked in Git. This means promoting changes across development, staging, and production requires different approaches depending on the type of change.

For database-level updates, Odoo SH allows you to create a backup of an environment and restore it into another one. This is useful for moving apps and configurations from staging to another environment. However, in production, you generally don’t overwrite the database, since it already contains live data. Instead, you replicate the same steps manually or bundle configurations into proper modules for deployment.

Studio customizations need special attention because they are stored in the database by default. The recommended practice is to export them as modules through Studio and then commit them to the Git repository. This ensures they are versioned, tested, and deployable like any other module, reducing risks of inconsistencies between environments.

A good workflow is to use development for trying new apps and customizations, staging for testing with realistic data, and production only for changes that are managed through Git and exported modules. For configurations that cannot be packaged in modules, apply them carefully in production. This approach keeps your environments consistent and makes deployments more reliable.

Hope it helps

I do it by scripting what is changed / configured in the staging database, so I can re-run the script in Production.

https://www.odoo.com/forum/help-1/easy-way-to-transfer-settings-from-one-database-to-another-can-i-export-them-can-i-programmatically-configure-a-database-184325

Odoo Studio is designed for a single User making relatively simple changes.

Odoo.sh is designed for a team of developers working as a team making complex changes.

Ideally you pick one or the other - so Odoo Studio is not install in most Odoo implemented databases hosted on Odoo.sh.

Odoo Studio changes can be exported and imported between databases - but test this first to ensure the export supports everything you need.

https://www.odoo.com/documentation/master/applications/studio/models_modules_apps.html#export-and-import-customizations

Hello Rutger,

It's great to hear you're leveraging Odoo.sh for your CRM and Helpdesk implementation! Promoting changes across environments requires careful handling of both code and database configurations.

  Apps and Modules: Standard Odoo apps are indeed installed at the database level. To promote these, you generally don't track them in Git directly. Instead, the installation status is managed within the database itself.

  Configuration and Settings: System settings and configuration updates made in staging should be exported as data files (e.g., using Odoo's data export feature). These files can then be imported into your production environment.

  Odoo Studio Customizations: Odoo Studio customizations are also stored in the database. The recommended approach is to export these customizations as a Studio patch. This patch can then be applied to your production environment. This ensures that your custom fields and adjustments are safely moved.

  Workflow: A typical workflow involves making changes in your development or staging environment, exporting the relevant data (settings, Studio customizations), and then importing this data into your production environment after testing.

  Important Note: Always back up your production database before importing any changes to prevent data loss.

For personalized assistance:
https://www.pragtech.co.in/contact-us-mql.html

Hello Rutger,

It's great to hear you're leveraging Odoo.sh for your CRM and Helpdesk implementation! Promoting changes across environments requires careful handling of both code and database elements.

Here's a breakdown of how to manage apps, settings, and Studio customizations:

  Apps and System Settings:

  Odoo apps and system settings are stored in the database. To move these changes, you'll need to update the production database with the changes from staging.

  Database Synchronization:

  The recommended approach is to create a backup of your staging database and restore it to your production environment. Be aware that this will overwrite the existing production data, so plan accordingly.

  Odoo Studio Customizations:

  Odoo Studio customizations are also stored in the database. When you transfer the staging database to production, these customizations will be included.

  Workflow:

  1. Make changes and customizations in your development or staging environment.

  2. Test thoroughly in staging.

  3. Create a backup of the staging database.

  4. Restore the staging database backup to your production environment.

  Important Considerations:

  Always test database migrations in a safe environment before applying them to production.

  Consider the impact on existing data when restoring a database backup.

For personalized assistance:
https://www.pragtech.co.in/contact-us-mql.html