Staging

Mohamed Azizi

• May 23, 2026 14:11

Hi Brizy team,

I currently have a Brizy Pro Freelancer license and I host my websites myself on a self-managed DirectAdmin server.

I'm working on a WooCommerce website and I want a proper development/staging workflow. My goal is to be able to make and test changes without editing the live website directly.

My first idea was to create something like:

• Live: domain.com

• Staging/Dev: dev.domain.com or staging.domain.com

However, I ran into a concern. If I clone the live site to a staging subdomain, make all changes there, and then like the result, I would still need to manually recreate the same changes again on the live site. That feels like double work.

What I am actually trying to achieve is a workflow where I can:

1. Work safely on a development version

2. Test all changes there

3. Push only the design/page/template changes to the live website

4. Avoid overwriting WooCommerce data such as orders, customers and dynamic content

So I have a few questions:

• Does a staging/dev subdomain count as a separate activated site under the Freelancer license?

• Do you have a recommended workflow for this setup?

• Is there a Brizy-specific way to move page/template/design changes from staging to production?

• How do Brizy users usually handle staging on self-hosted environments?

Thanks!

0

• 

  KC George

  • May 25, 2026 04:54
  • Edited

  Hello Mohamed,

  You can use a staging/migration plugin to create a staging site for your WooCommerce website. Migrate Guru works well with Brizy. You could consider the migration process outlined at Migrate WordPress Site to ANY Host For Free

  To retain the WooCommerce orders and other customer related data, while pushing changes back to the live site, you will need to export your orders and product data by using a separate export/import plugin on the production site and then import the data back into the staging site before you do the push. Kindly follow the process outlined at How to Prevent WooCommerce Orders and Products from Being Overwritten During Pushing. It is ideal to test the entire process (of creating staging and pushing changes back to live) on a test website, before trying it out on a live WooCommerce website.

  Let me go over to your questions.

  • Does a staging/dev subdomain count as a separate activated site under the Freelancer license? Your production and staging sites can share a single Brizy Pro license key.
  • Do you have a recommended workflow for this setup? As we have not attempted the above workflow on a WooCommerce website, we cannot guarantee results. Hence please test the process before implemnting it on a live site.
  • Is there a Brizy-specific way to move page/template/design changes from staging to production?. For regular migrations (without the need for retaining order details), using Migrate Guru works well for Brizy websites. 
  • How do Brizy users usually handle staging on self-hosted environments? Brizy users either use the staging feature provided by their hosting company or use a migration plugin to push changes to their live websites. However, both these approaches do not help retain WooCommerce customer and order data. 

  0

Please sign in to leave a comment.