# Migrate sites between Ploi servers

**Project:** Sites | **Board:** Closed | **Votes:** 3
**URL:** https://roadmap.ploi.io/projects/2-site-level-requests/items/758-migrate-sites-between-ploi-servers

---

Similar to the clone feature... it would be great if sites could be migrated from one Ploi server to another, also including the database and all other settings.

---

## Comments

**Dennis** (2023-08-18T11:40:00+00:00):
Not sure I understand, what's the difference between migrating and cloning? They do the same but just different word right?

**Jure Topolak** (2023-08-18T14:13:47+00:00):
Let me clarify :)

Since it's possible to clone the site and the database... there could be a feature, to migrate / clone (call it whatever you want :) with one click, which would:
- clone the site with the same settings (which are possible)
- clone the database (if it's attached to the site) with the same database username/password
- and **optionally** remove the original if the whole process is successful. (Credits to @Arko) :P

I need to move a bunch of WP sites from one server to another and it would be nice if I could do that with only one click of the button. And after changing DNS records only issue a new SSL cert.

**Dennis** (2023-08-23T11:03:30+00:00):
Ah right, so, basically, we already have these features, their just not combined as you describe.

- You can clone a site to another server via the manage tab -> clone, this does not delete the original site, but you can do that
- You can clone a database, to another server, via the databases tab -> press the 3 dots button -> clone

You're saying it has to be in 1 action?

**Jure Topolak** (2023-08-23T11:36:16+00:00):
`When you clone the database, users will not be cloned. You can create a new user for this cloned database.`

It would be great if the new DB user would be created with the same username/password so that no additional configuration would be needed.

You could also just add a new checkbox under the "clone site" named "clone attached database" which would simplify the migration of the site with the database. But like I said, DB user should be the same.

**James** (2026-03-13T16:36:20+00:00):
I've also got a use case for this. 

Say for example we're needing to move sites from a old server to a new server say for example the server is full and we need to off-load some customers to a new server. Having a migration tool so that we can move a customer system one for server to another with on-click and then we can manage the DNS ourself.