Migrating a site from one cloudron instance to another.

[swheeler78]

No worries. I'm sure there's a way. LOL

[humptydumpty]

@swheeler78 Most definitely and I have a "clue" how, but I don't mention what I haven't done myself so I'll stay

[swheeler78]

I have some ideas but it would require manually setting up the domain and exporting users from the DB and moving mail folders over. Not my idea of a good time. Plus my kids might want to see me before 2026.

[joseph]

@swheeler78 said in Migrating a site from one cloudron instance to another.:

Also, I'm not looking at migrating to a new server nor am I trying to move any apps. I'm trying to migrate a domain and emails to an existing cloudron instance with existing domains and data.

For apps, you have to move them one by one as @humptydumpty outlined.

For email, you can move mailbox by mailbox using imapsync. See https://docs.cloudron.io/guides/import-email/ .

[humptydumpty]

@joseph said in Migrating a site from one cloudron instance to another.:

For email, you can move mailbox by mailbox using imapsync.

It's a hassle if you have a ton of mailboxes, right? It seems easier to move the apps over to the mailserver VPS and then transfer the entire Cloudron back.

[swheeler78]

Well, Except, when you have existing mailboxes and multiple domains on a single cloudron and you want to move things around. Whether it's to distribute the app / load or to migrate multiple smaller VPS's to a larger VPS.

[scooke]

@humptydumpty You didn't misread. You answered the post as written.

[scooke]

Thinking out loud:

1. Make a temp generic email address somewhere, maybe even on the destination Cloudron.

2. imapsync the existing email from the old cloudron to the destination Cloudron/temp generic email address. (this is needed first because if you move the domain to the destination Cloudron and setup the same emails and all that, you won't be able to access the old email as it won't be running.)

3. Move the domain(s) to the destination Cloudron.

4. Make the same users on the destination Cloudron (this assumes the users are dependent on the moved domain).

5. Turn on email for this moved domain and users.

6. imapsync once more from the temp generic email to this "new account" on the destination Cloudron (said accounts which should be set up to have the same email domain and passwords to make it easier for the end user to not have to change all the passwords they have in their browser, email clients, etc.)

Now, you said this was just users and emails, so please don't bring up apps now!

Be sure to read this - https://docs.cloudron.io/guides/import-email/ as it gives helpful tips in terms of mailbox creation and email activation steps.

[scooke]

@swheeler78 imapsync ftw. You can be done in under an hour.

[swheeler78]

Ok, I'll look into it. The only apps on the instance that has the users and emails is just the webmail app. So I'm not counting that.

[scooke]

There is no look-into-it. There is only do-it.