Bringing an existing site
A WordPress site can be copied in for you: install our small connector plugin on the live site and Site Buddy copies it across. For anything else, you create an empty site of the right type, then hand Buddy your code and data and let it set the site up.
WordPress: copy it with the connector
Section titled “WordPress: copy it with the connector”- Create a site, choose WordPress, and under Start from pick A copy of my live WordPress site.
- On the Connect step, download the Site Buddy connector (a .zip file). On your live site, go to Plugins, Add New Plugin, Upload Plugin, choose the file, then Install Now and Activate.
- On the live site, go to Tools, Site Buddy, copy the pairing code and paste it into the wizard. Treat the code like a password: anyone with it can copy your site. If you think it was seen by someone else, press Make a new code there and the old one stops working.
- The Review step shows what Site Buddy found: WordPress and PHP versions, the theme, how many plugins, and how big the database is. If the site can’t be copied (a multisite network, a very old PHP, a host with no room for the copy), the wizard tells you why before anything starts.
- Choose which tables’ records to leave out. Form entries and logs are ticked for you: they are usually the biggest part of an old site’s database and hold your visitors’ personal details. Their tables still come across, empty, so the plugins that use them keep working. Untick one to copy its records too.
- Press Create. Your live site packs up its database, themes and plugins (a minute or two on most hosts), then Site Buddy downloads and loads the copy. The site’s status pane shows how far it has got.
What is copied: the database, themes, plugins and everything else under wp-content. What isn’t: images and
other media. The copy shows them from your live site, so nothing looks missing; media you add to the copy is kept in
the copy. Your live site is not changed, and the copy is deleted from your host once Site Buddy has it.
Logging in: the copy keeps the live site’s users, so you log in to it with your usual username and password.
Made safe automatically: so the copy can’t affect real customers, Site Buddy turns off WordPress’s scheduled tasks, deactivates email-sending, firewall and caching plugins, removes the live host’s cache add-ons, and switches off the connector in the copy. The status pane lists what was changed (hover Copied from). If WooCommerce is active, check its payment gateways are in test mode before trying a checkout.
If the copy stops: the status pane says why. A host that ends long-running tasks may stop the export part-way; raising the PHP memory limit to 256M in your hosting control panel usually fixes it. Then open Site settings, Live site and press Try the copy again.
The connection: Site Buddy keeps the pairing code (encrypted) so the copy can be refreshed from the live site later. Site settings, Live site shows where the copy came from, and Disconnect makes Site Buddy forget the code. You can also deactivate or delete the connector plugin on the live site at any time; the copy is not affected.
Any other site
Section titled “Any other site”The rest of this page is for sites the connector doesn’t cover, or if you would rather bring a WordPress site in by hand.
1. Create a matching site
Section titled “1. Create a matching site”Create a site of the same type as the one you are bringing:
- WordPress, Drupal or Laravel for those platforms. Set PHP version and Database to match the live site; the database type can’t be changed afterwards.
- Shopify Theme or Netlify: give the wizard your store or Netlify credentials, and Site Buddy works against your real account from the start.
- Generic PHP for any other PHP site or static site, and Node.js for a JavaScript app.
For WordPress, fill in Live media URL with the live site’s address: images the copy doesn’t have are shown from the live site, so you don’t have to move a large uploads folder.
2. Give Buddy the code
Section titled “2. Give Buddy the code”Either:
- From GitHub: add a GitHub integration to the site with the repository’s address and a token. Buddy can clone it, and later push its changes back or open pull requests.
- As files: upload a zip of the site’s files to the Artifacts pane (up to 95 MB per file; split a bigger archive into parts). See files and uploads.
3. Give Buddy the data
Section titled “3. Give Buddy the data”For a site with a database, export it from your current host (a .sql or .sql.gz file; most hosts and database
tools have an export button) and upload it to Artifacts.
4. Ask Buddy to set it up
Section titled “4. Ask Buddy to set it up”Something like:
Set this site up from the code in the GitHub repository and the database export in Artifacts. The live address is https://www.example.com.
Buddy puts the code in place, imports the database, changes the site’s address to its preview address, and checks the result in a browser. Then take a checkpoint so you always have this starting point to come back to.
Things worth telling Buddy
Section titled “Things worth telling Buddy”- The live site’s address, so it can fix links and settings that point to it.
- Anything special about the site: a plugin that needs a licence key, a service it talks to, a page that must not change.
- Where secrets live. Don’t paste passwords or keys into the chat; connect the service as an integration instead.
Going live
Section titled “Going live”Site Buddy is where the work happens; your live site stays with your current host. Buddy can deliver its changes the way your team already ships: by pushing to GitHub, deploying through Netlify or Shopify, or connecting to your server over an SSH server or Remote WordPress integration.

