Cloning creates a separate copy of a WordPress website. Syncing copies selected types of data from one existing website to another. Our NabWP Staging & clone tools can support these workflows where enabled, but it is essential to identify the source, destination and data scope before you continue.
IN THIS ARTICLE
01 Choose a clone or a staging copy
A full independent clone has its own website and database and is subject to the plan's website allowance. A staging copy is associated with the live website for testing. Both copies use hosting resources, so review available storage and the destination before starting. A copy operation is not a substitute for keeping an appropriate backup.
02 Review the data scope before syncing
The sync workflow can offer files only, database only, or files and database. These choices have different consequences.
| Sync scope | What to consider |
|---|---|
| Files only | Files-only deployment may suit some code changes, but changes stored in the database will not necessarily follow. |
| Database only | A database sync can replace content and settings on the destination, including records created there after the source copy was made. |
| Files and database | Both types of data are copied. Review the file changes and the consequences of replacing the destination database together. |
For a live shop, booking site or membership website, do not assume sync will merge recent orders, bookings or customer registrations. The supported database copy is not an intelligent business-record merge. Tell our team what changed on staging and what has continued changing on live so that the deployment can be planned appropriately.
03 Back up the destination and verify the result
Before syncing, create or confirm a current destination backup and review any offered restore-point option. Keep the copy direction explicit, wait for completion and test the destination afterwards. If you are unsure whether a page-builder change lives in files or the database, ask before deploying it. We can help identify a suitable release method so that the intended improvement reaches production while the current live information is accounted for.
What should I confirm before cloning or synchronising websites?
- Write down which site is the source and which site will receive the copy.
- Choose files, database or both according to where the actual change is stored.
- Confirm a current destination recovery point, carry out the supported operation and verify the destination afterward.
A page-builder edit may live in the database even when it looks like a design change. A files-only sync may omit it, while copying the whole database can overwrite newer live orders or registrations. The supported copy process does not merge business records automatically; ask for help when the two sites have both changed.