CloudStick is a server control panel for developers and agencies that lets you manage cloud servers on AWS, DigitalOcean, Vultr, Linode, and Hetzner without using the command line. Plans start at $9/month — the Basic plan covers 1 server with unlimited websites; Pro at $19/month and Business at $49/month cover unlimited servers.

Will features I pay for ever get moved to a higher plan?

No. CloudStick is committed to keeping all features you currently pay for within your existing plan. New features may be added to higher tiers, but existing plan features will never be removed or require a forced upgrade.

What happens to my servers if I cancel CloudStick?

Your servers remain fully operational after cancellation. CloudStick does not host your servers — it manages them. If you cancel, you lose access to the CloudStick dashboard, but your servers continue running on your cloud provider.

Is there a free trial for CloudStick?

Yes. CloudStick offers a 7-day free trial on all paid plans with no credit card required. You can explore every feature and upgrade, downgrade, or cancel at any time during or after the trial.

WORDPRESS

July 1, 2026

How to Clone a WordPress Site for Testing

7 min read

CloudStick Team

DevOps Engineer

Share this article

How to Clone a WordPress Site for Testing

Migration Guide

When a Clone Beats Staging

A staging environment is meant to persist and stay in sync with production indefinitely. A clone is disposable — spin it up to test one specific thing (a major plugin update, a PHP version bump, a risky theme change), then delete it. If you find yourself reaching for the same clone repeatedly, that's a sign you actually need a proper staging setup instead.

Clone on the Same Server

The fastest clone lives on the same server, under a subdirectory or subdomain, sharing the same PHP-FPM pool. This is fine for quick checks but shares resource limits with production — heavy testing can slow the real site down.

# Copy files to a new document root on the same box
rsync -av /home/example/apps/example.com/ /home/example/apps/clone.example.com/
# Clone the database under a new name
mysqldump -u dbuser -p wp_example | mysql -u dbuser -p wp_example_clone
wp search-replace 'example.com' 'clone.example.com' --skip-columns=guid --all-tables \
  --path=/home/example/apps/clone.example.com

Clone to a Separate Server

For testing that involves load, server config changes, or anything you don't want anywhere near production infrastructure, clone to a fresh, cheap VPS instead. CloudStick lets you spin up a new server and one-click install WordPress in minutes, then use the same rsync/mysqldump sequence to populate it with real content for a realistic test.

Cleaning Up After Testing

A clone that outlives its purpose becomes a security liability — an unmaintained, unpatched WordPress install sitting on your server with a real copy of your data. Delete the clone (files, database, and the subdomain DNS record) the same day testing finishes.